# Manual installation instructions These intructions are inspired from a standard django/gunicorn/postgresql instructions ([for example](https://www.digitalocean.com/community/tutorials/how-to-set-up-django-with-postgres-nginx-and-gunicorn-on-ubuntu-16-04)) !!! warning Be sure to use pyton3.8 and pip related to python 3.8. Depending on your distribution calling `python` or `pip` will use python2 instead of pyton 3.8. ## Prerequisites *Optional*: create a virtual env and activate it Get the last version from the repository: `git clone https://github.com/vabene1111/recipes.git -b master` Install postgresql requirements: `sudo apt install libpq-dev postgresql` Install project requirements: `pip3.8 install -r requirements.txt` ## Setup postgresql Run `sudo -u postgres psql` In the psql console: ```sql CREATE DATABASE djangodb; CREATE USER djangouser WITH PASSWORD 'password'; GRANT ALL PRIVILEGES ON DATABASE djangodb TO djangouser; ALTER DATABASE djangodb OWNER TO djangouser; --Maybe not necessary, but should be faster: ALTER ROLE djangouser SET client_encoding TO 'utf8'; ALTER ROLE djangouser SET default_transaction_isolation TO 'read committed'; ALTER ROLE djangouser SET timezone TO 'UTC'; --Grant superuser right to your new user, it will be removed later ALTER USER djangouser WITH SUPERUSER; ``` Download the `.env` configuration file and **edit it accordingly**. ```shell wget https://raw.githubusercontent.com/vabene1111/recipes/develop/.env.template -O .env ``` ## Initialize the application Execute `export $(cat .env |grep "^[^#]" | xargs)` to load variables from `.env` Execute `/python3.8 manage.py migrate` and revert superuser from postgres: `sudo -u postgres psql` and `ALTER USER djangouser WITH NOSUPERUSER;` Generate static files: `python3.8 manage.py collectstatic` and remember the folder where files have been copied. ## Setup web services ### gunicorn Create a service that will start gunicorn at boot: `sudo nano /etc/systemd/system/gunicorn_recipes.service` And enter these lines: ```service [Unit] Description=gunicorn daemon for recipes After=network.target [Service] Type=simple Restart=always RestartSec=3 Group=www-data WorkingDirectory=/media/data/recipes EnvironmentFile=/media/data/recipes/.env ExecStart=/opt/.pyenv/versions/3.8.5/bin/gunicorn --error-logfile /tmp/gunicorn_err.log --log-level debug --capture-output --bind unix:/media/data/recipes/recipes.sock recipes.wsgi:application [Install] WantedBy=multi-user.target ``` *Note*: `-error-logfile /tmp/gunicorn_err.log --log-level debug --capture-output` are usefull for debugging and can be removed later *Note2*: Fix the path in the `ExecStart` line to where you gunicorn and recipes are Finally, run `sudo systemctl enable gunicorn_recipes.service` and `sudo systemctl start gunicorn_recipes.service`. You can check that the service is correctly started with `systemctl status gunicorn_recipes.service` ### nginx Now we tell nginx to listen to a new port and forward that to gunicorn. `sudo nano /etc/nginx/sites-available/recipes.conf` And enter these lines: ```nginx server { listen 8002; #access_log /var/log/nginx/access.log; #error_log /var/log/nginx/error.log; # serve media files location /static { alias /media/data/recipes/staticfiles; } location /media { alias /media/data/recipes/mediafiles; } location / { proxy_pass http://unix:/media/data/recipes/recipes.sock; } } ``` *Note*: Enter the correct path in static and proxy_pass lines. Enable the website `sudo ln -s /etc/nginx/sites-available/recipes.conf /etc/nginx/sites-enabled` and restart nginx : `sudo systemctl restart nginx.service`