Development and production environments #2

New Issue

binaryDiv · 2019-09-24T01:12:36+02:00

binaryDiv commented

2019-09-24 01:12:36 +02:00

Write .env files for development and for production, use environment variables in settings.py.

For production: Replace SECRET_KEY, set DEBUG to False, set database credentials.

Also: Don't commit the production .env file to the repo! (We could encrypt it of course, but let's rather manage production secrets outside the repo.)

Write .env files for development and for production, use environment variables in settings.py. For production: Replace SECRET_KEY, set DEBUG to False, set database credentials. Also: Don't commit the production .env file to the repo! (We could encrypt it of course, but let's rather manage production secrets outside the repo.)

binaryDiv added the

deployment

label 2019-09-24 01:12:36 +02:00

binaryDiv commented

2019-10-21 02:39:52 +02:00

Done with production .env in repository, for now. The whole deployment process needs to be improved and more automated. For now it works.

Also done the nginx static file serving thing.

Done with production .env in repository, for now. The whole deployment process needs to be improved and more automated. For now it works. Also done the nginx static file serving thing.

binaryDiv closed this issue

2019-10-21 02:39:52 +02:00

binaryDiv commented

2019-10-21 02:41:37 +02:00

Used this guide btw: https://testdriven.io/blog/dockerizing-django-with-postgres-gunicorn-and-nginx/

Sign in to join this conversation.