OpenEats Installation Directions


OpenEats has the following requirements in order to run properly.  Please make sure you meet them prior to the install.

To check your PHP version and to see if you have the proper extensions compiled in, create a file called info.php and type

"<?php phpinfo()?>" minus the quotes.  Then save this file on your web server and point your browser to it.  The installer on OpenEats will also check these items to see if your server is compatible with OpenEats.

Installation Types:

OpenEats can be installed a few different ways its up to you wish one you choice.  Option one or two are the recommended install methods.

  1. As a Virtual Host with a second level subdomain or its own domain.  See your web servers documentation on how to do this.
  2. Under your document root.  Usually this is your htdocs directory.  Do run OpenEats in this fashion you will want to change the configuration of your web sever to use the /web directory of OpenEats as the document root directory, then restart your web server.
  3. Under a subdirectory under your document root directory.   This may be the most common install method because it is best suited for new comers that do not have a lot of experience with setting up the first two methods.  This would be as simple as unzipping OpenEats under the web servers root directory and pointing your browser to http://yourhost/openeats.  This method may have small quirks depending on how your web server is set-up for OpenEats was orginally designed to run as the first two options, and had to be modfied to run as this option.  Most of the testing of OpenEats is done as the first two options.

Installation Methods:

OpenEats ships with two installtion methods, a manual install and a semi-automated web based install.  For both methods you need to follow the initial steps below first.

Web Based Installer:

The web based installer is in alpha-version and has only been tested on Mac OS X and Linux. It should however work on Windows.

  1. Accessing the Web-based installer will depend on which method you used to install OpenEats.  If you picked one of the first two methods (sub domain, virtual host) point your browser to http://yourhost/setup/install.php  If you chose to run it out of a sub-directory point your browser to http://yourhost/yoursubdir/web/setup/install.php
  2. OpenEats installer will then run through a compatibility check to see if your web server is ready to run the software
  3. The next page will have you type in the database information you created
  4. If all goes well the final page should give you a link to your site and you are ready to go

Manual Installer:

  1. Under the main OpenEats directory.  Edit the config/databases.sample.yml file and  type in your database server information in the provided stanzas in this file and save this file as databases.yml (remove the sample)
  2. Under the main OpenEats directory.  Rename the file apps/OpenEats/config/app.sample.yml to app.yml
  3. Load the oe_schema.sql sql file into your newly created database. This file is located under the OpenEats Directory /data/sql/oe_schema.sql . You are now complete if you chose one of the first two install methods above.  If you chose the third, to install under a subdirectory please contiune on.
  4. Edit the .htaccess.sample file found under the OpenEats Directory. Change this line “RewriteRule ^(.*)$ /oe/web/index.php/$1” to
    RewriteRule ^(.*)$ /oedirectory/web/index.php/$1 with oedirectory being the directory you installed OpenEants under. Save this file as .htaccess
  5. Edit the config.sample.php file found under the OpenEats Direcotory /apps/OpenEats/config Change this line ‘sf_base_url_dir’ => “”, to ‘sf_base_url_dir’ => “/oedirectory/web”,  Save this as config.php
  6. You should now be able to point to your newly installed OpenEats.


The following should help with most issues you face when installing OpenEat.  The first thing you should do if you have a issue is place OpenEats in “debug” mode.  To do this copy the debug.php file found under where you installed OpenEats, to the web/ directory found under where you installed OpenEats.  Then point your browser to this file http://localhost/openeats/web/debug.php or http://localhost/debug.php. This will give a more verbose ouput when issues occur

If a issue has been resloved you will need to delete the cahce directory found under where you installed OpenEats. The cache is used to speed up pages, however after if you fix a error you don’t want the ‘cached’ version of the error so removing this directory will force the cache to be re-created.

Feel free to post in the OpenEats forums and I will help you out with any issues.



  1. […] upgrade We are getting closer and closer the 1.1 release. I have just updated the install instructions and created a new upgrade document.  Stay tuned we hope to release this next great version of […]

  2. elearndev said

    I am about to start pulling my hair out!

    I didn’t quit understand the instructions and ended up with some weird results. You can see the results on

    Please help, I am lost.

    • openeats said

      Please post in the forums with the info, such as php version, version of OpenEats you tried to install and as many details to the issues you are having as you can.

  3. elearndev said

    I got a question; can Open Eats be installed as a wordpress blog page?

    I have a blog at Can I install Open Eats in and have a page added for that. For example, at the top of the webpage there will be links to About, Our Meals, Contact…?

    Mod, Please feel free to merge my comments. Thank you.

  4. elbiem said


    please have a look at this issue..


RSS feed for comments on this post · TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: