chore(env): rename KOBO_SUPPORT_EMAIL to CONSTANCE_SUPPORT_EMAIL DEV-1976

[platreth]

🔗 Related PRs

Part of a 3-repo Constance env-var standardization:

• refactor(settings): standardize Constance env overrides to CONSTANCE_ prefix DEV-1976 kpi#7230 — the app-side rename (reads CONSTANCE_SUPPORT_EMAIL)
• chore(env): rename KOBO_SUPPORT_EMAIL to CONSTANCE_SUPPORT_EMAIL DEV-1976 kobo-install#279 — same rename in the kobo-install env template

kpi keeps backward compatibility (old names still read, with a DeprecationWarning), so this can land independently — it simply migrates the default env file to the new name.

Description

Renames KOBO_SUPPORT_EMAIL → CONSTANCE_SUPPORT_EMAIL in the default django env file. Only the var name changes; the value is unchanged.

[greptile-apps]

Greptile Summary

This PR renames the KOBO_SUPPORT_EMAIL environment variable to CONSTANCE_SUPPORT_EMAIL in env/envfiles/django.txt as part of a coordinated Constance env-var standardization across three repositories. The value is unchanged; only the key name is updated.

• Single-line env rename: KOBO_SUPPORT_EMAIL → CONSTANCE_SUPPORT_EMAIL in env/envfiles/django.txt; no other occurrences of the old name remain in this repo.
• Coordinated merge required: The PR description clearly notes that kpi#7230 (app-side read) and kobo-install#279 (install template) must be released together to avoid silently reverting to the default support email.

Confidence Score: 5/5

Safe to merge once the companion PRs (kpi#7230 and kobo-install#279) are ready to release together.

The change is a single env-var key rename with the value left untouched. No old references to KOBO_SUPPORT_EMAIL remain anywhere in this repo, so there is no risk of stale lookups within kobo-docker itself. The only coordination risk is the cross-repo dependency explicitly documented in the PR description.

No files require special attention.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["kobo-docker env/envfiles/django.txt\n(this PR)"] -->|"CONSTANCE_SUPPORT_EMAIL\n(renamed from KOBO_SUPPORT_EMAIL)"| B["kpi app\n(kpi#7230 — reads CONSTANCE_SUPPORT_EMAIL)"]
    C["kobo-install env template\n(kobo-install#279)"] -->|"sets CONSTANCE_SUPPORT_EMAIL"| A
    B --> D["Support email surfaced to users"]

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A["kobo-docker env/envfiles/django.txt\n(this PR)"] -->|"CONSTANCE_SUPPORT_EMAIL\n(renamed from KOBO_SUPPORT_EMAIL)"| B["kpi app\n(kpi#7230 — reads CONSTANCE_SUPPORT_EMAIL)"]
    C["kobo-install env template\n(kobo-install#279)"] -->|"sets CONSTANCE_SUPPORT_EMAIL"| A
    B --> D["Support email surfaced to users"]

Loading

_{Reviews (1): Last reviewed commit: "chore(env): rename KOBO_SUPPORT_EMAIL to..." | Re-trigger Greptile}

[noliveleger]

LGTM but do not merge it.
We will to merge it when KPI changes are going to be released.