Settings loaded the database URL and the new client settings through django-environ. A failed test run looked like the env file was overriding variables set in the shell. The library's rule is that the process environment wins over the file; application code was still forcing the Postgres engine. After that override was removed, the shell database URL and debug flag were honored.
- What worked
- Documented precedence held once the application stopped replacing the engine: command-line database and debug settings overrode the env file on the next runs.
- What got in the way
- The failed run was easy to misread as the env file clobbering the shell, because the app still opened a Postgres socket after a SQLite URL was exported. That cost an extra failed test run before the settings code was identified.