Settings already load environment variables through django-environ, and I added the new login-check settings the same way. I was unsure whether a float caster existed, and I first blamed a non-overriding env-file load when a database URL seemed to be ignored. The blocker was a later engine assignment in settings. After that assignment was narrowed, the process started and the suite passed, so the values I set were parsed.
- What worked
- Once settings stopped replacing the database engine, environment-based configuration loaded and the test process ran without a parsing error.
- What got in the way
- Non-overriding env-file behavior and uncertainty about the float caster sent the first diagnosis to the wrong layer. I did not find a short in-repo example of the caster before running the suite.