CODEWITHSUNDEEP
djangoenvironment-variablessupervisord
Anuj TBE
Anuj TBE

Reputation: 9790

.env not working with Django with supervisor

I have a Django 2.2 project and all secrets are in .env file.

I'm using a library dotenv to load .env to the Django application in the manage.py file

import dotenv

def main():

    # Read from .env file
    env_file = os.path.join(os.path.dirname(os.path.realpath(__file__)), '.env')
    dotenv.read_dotenv(env_file)
    ....

The environment file is working and is loaded well when running locally.

On the server, I'm using the supervisor to run the application with the following configuration.

[supervisord]
[program:myapp]
command=/var/www/html/app/start_gunicorn.sh
directory=/var/www/html/app/
autostart=true
autorestart=true
stopasgroup=true
stopsignal=QUIT
logfile=/home/ubuntu/log/supervisor/supervisor.log
logfile_maxbytes=5MB
logfile_backups=10
loglevel = info
stderr_logfile=/home/ubuntu/log/supervisor/qcg-backend.err.log
stdout_logfile_maxbytes=5MB
stdout_logfile_backups=10
stdout_logfile=/home/ubuntu/log/supervisor/qcg-backend.out.log
stderr_logfile_maxbytes=5MB
stderr_logfile_backups=10

But the environment variables are not loaded and not working in Django.

Running following command from SSH console is working.

python manage.py shell
import os
os.environ.get('DEBUG')
> True

But running the application, environment variables are not accessible and not applied in the application.

Upvotes: 1

Views: 1479

Answers (2)

Vu Viet Hung
Vu Viet Hung

Reputation: 330

I think putting it on settings.py is more convenient. No need to add it to both manage.py and wsgi.py

Upvotes: 0

jimijimjim
jimijimjim

Reputation: 625

manage.py is not invoked when running Django in production. From the dotenv docs, it says that you should add the loader code to the top of wsgi.py as well.

Upvotes: 2

Related Questions