Running the App

The recommended way to run this app is with docker. You can install docker here. If you are not familiar with docker you can read more about it on their website.

Running the app with docker for production

If you are looking to run this in production, there is no need to clone the repo.

First, create two files: - docker-prod.yml - This file can be found in the in the root directory of the repo. - env_prod.list - The settings file sample_env_file_for_docker.list can be used as an example.

The docker-prod.yml contains the list of images and commands to run the app. It comes with an nginx reverse proxy that by default will run on port 80. You will most likely want to change the port that nginx runs on as well as use a fix tag for the image. By default, all are set to latest.

Configure the environment file

Most of the settings in your env_prod.list can stay the same as env_stg.list that is in this repo. There are a few config settings that need to be changed for most configurations. See Setting_up_env_file.md for a complete description of the environment variables.

• DATABASE_PASSWORD
• DJANGO_SECRET_KEY
• ALLOWED_HOST
• NODE_API_URL

Once the files have been created run:

docker-compose -f docker-prod.yml up -d

Running the app with docker for development

git clone https://github.com/RyanNoelk/OpenEats.git
cd OpenEats
git checkout dev
docker-compose build
docker-compose up -d

First Time Setup

Regardless of if your running the app in production or development, you need to seed the database.

To create a super user:

docker-compose -f docker-prod.yml run --rm --entrypoint 'python manage.py createsuperuser' api

Follow the prompts given to create your user. You can do this as many times as you like.

If you are an english user, it is highly recommended to add course and cuisine data. Run docker-compose run --rm api bash to open a bash shell to the API. Then:

./manage.py loaddata course_data.json
./manage.py loaddata cuisine_data.json

If you want to add some test data you can load a few recipes and some news data. This data isn't really needed unless you just wanna see how the app looks and if its working.

./manage.py loaddata news_data.json
./manage.py loaddata recipe_data.json
./manage.py loaddata ing_data.json