go-env | A Go library for populating a struct | Configuration Management library

As you may have guessed judging by your edit, Heroku doesn't support pushing .env files. This is because it uses an ephemeral filesystem.

Each dyno gets its own ephemeral filesystem, with a fresh copy of the most recently deployed code. [...] any files written will be discarded the moment the dyno is stopped or restarted. For example, this occurs any time a dyno is replaced due to application deployment and approximately once a day as part of normal dyno management.

You'd be better off using Heroku's built-in config var support. Here are some examples:

I fixed this problem by adding more @extend_schema to other extra endpoints, if did not that you get an error like that I take

I don't know why, but the way I restarted my server during deploy doesn't refresh env.ini, and the server remembers the old settings. If I restart my server with sudo reboot, with the same settings, then CACHES is equal to {'default': {'BACKEND': 'django.core.cache.backends.memcached.PyMemcacheCache', 'LOCATION': '127.0.0.1:11211'}} and the site works properly. And I confirmed that if I put dummy values in env.ini then the site doesn't work at all. But only if I restart my server with sudo reboot.

The most pressing problem here is that you're doing a database call at import time by trying to load a session via

This is apparently caused by two things:

• In settings.py, the secret content is loaded into environment variables with env.read_env(io.StringIO(payload)), as mentioned in the question. That read_env() function apparently does the following:

welcome to Docker! It can be quite the thing to wrap one's head around, especially when beginning, but you're asking really valid questions that are all pertinent

A great place to start is Docker's own Dockerfile best practices page:

https://docs.docker.com/develop/develop-images/dockerfile_best-practices/

They explain neatly how your each directve (COPY, RUN, ENV, etc) all create additional layers, increasing your containers size. Importantly, they show how to reduce your image size by minimising the different directives. They key to alot of minimisation is chaining commands in RUN statements with the use of &&.

Something else I note in your Dockerfile is one specific line:

First check that you have installed django-environ and maybe you have a typing mistake in your requirements.txt it should be django-environ=0.4.5 instead of django-environ=0.4.5=py_1 you can pass the path of your .env inside read_env(env_file="relative_path_of_your_env_file")

it read a .env file into os.environ.

If not given a path to a dotenv path, does filthy magic stack backtracking to find manage.py and then find the dotenv.

go through this code https://github.com/joke2k/django-environ/blob/master/environ/environ.py#L614

Answering my own question as I have FINALLY found the cause of all my troubles ...

I had created an __init__.py file at the root of my project to define a project version as a constant..

After reading here and there about Django modules and namespaces, I removed the __init__.py from my root directory and that solved the problem.

**edited my question above to show the file in question

In general, uwsgi_params is already shipped with your Nginx, so all you need is include uwsgi_params (so it refers to /etc/nginx/uwsgi_params or similar).

If that is not the case, you will likely also need to give Nginx enough permissions to read the directory structure that file is in, not just the file itself.