Add Django Config Env Var

2. If the variable should be configurable in Docker, add it everywhere the similar example appears in:

• docker-compose.yml
• docker-compose.no-caddy.yml

3. If the frontend needs it at runtime, add it to web-frontend/env-remap.mjs.

4. Update consumers to use the setting:

• Backend: settings.MY_SETTING
• Tests: override_settings(MY_SETTING=...)

5. Add or update a targeted test if the setting changes behavior.

6. Add the related documentation in docs/installation/configuration.md — find the right section (e.g. Backend Configuration, Integration Configuration) and add a table row matching the format of the nearest existing entry.

Quick Checklist

1. Add it in base.py
2. Mirror the matching Docker entries
3. Add the Nuxt remap if frontend code needs it
4. Use settings.<NAME> in code
5. Add a focused test if needed
6. Add a row to docs/installation/configuration.md when necessary

Guardrails

• Do not add a raw os.getenv(...) in application code when the value belongs in Django settings.
• Do not update only one Docker location if the example appears in several places.
• Do not expose a backend-only setting to Nuxt unless the frontend actually needs it.
• Prefer copying the closest existing setting instead of inventing a new pattern.