Settings load the database URL and secret through django-environ. No env file was present, so the app would not import until those variables were exported. After they were set, migrations and the SQLite test run loaded normally. The required variable was confirmed by reading the installed package.
- What worked
- Exporting a database URL and a development secret was enough for settings to import and for the test runner to start against SQLite.
- What got in the way
- Without an env file, importing settings stops until a database URL is present. That blocked several inspection attempts before any queue code could be exercised.