log warning if DATABASES cannot be defined #2346

stveit · 2022-02-15T08:42:47Z

logs a warning if something goes wrong while defining DATABASES.

Struggled a bit as the warning never showed up in the log when refreshing the site. I think my PHP experiences
have infected my brain, as I guess I assumed all code would be rerun for each refresh.

But the warning shows up when starting up (with docker-compose up) or after making changes to the code.

This is shown in the log during docker-compose up when I cause an error to happen.

Is this something along the lines of what is wanted?

codecov · 2022-02-15T08:58:16Z

Codecov Report

Merging #2346 (672e8bf) into master (43a8657) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

❗ Current head 672e8bf differs from pull request most recent head b9b44e5. Consider uploading reports for the commit b9b44e5 to get more accurate results

@@            Coverage Diff             @@
##           master    #2346      +/-   ##
==========================================
- Coverage   58.07%   58.07%   -0.01%     
==========================================
  Files         552      552              
  Lines       40206    40207       +1     
==========================================
- Hits        23351    23350       -1     
- Misses      16855    16857       +2

Impacted Files	Coverage Δ
python/nav/django/settings.py	`97.59% <100.00%> (+0.02%)`	⬆️
python/nav/web/maintenance/views.py	`43.06% <0.00%> (-1.00%)`	⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 43a8657...b9b44e5. Read the comment docs.