Fix SECRET_KEY sentinel mismatch in .env.example (W-01)

The .env.example value didn't match the sentinel checked in config.py,
so copying .env.example verbatim to production would bypass the fatal
safety exit. Aligned to use the same default string.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Kyle 2026-03-02 17:21:32 +08:00
parent fee454fc33
commit ccfc5e151a

View File

@ -10,7 +10,7 @@ DATABASE_URL=postgresql+asyncpg://umbra:changeme_in_production@db:5432/umbra
# Application # Application
# ────────────────────────────────────── # ──────────────────────────────────────
# Generate with: python3 -c "import secrets; print(secrets.token_hex(32))" # Generate with: python3 -c "import secrets; print(secrets.token_hex(32))"
SECRET_KEY=change-this-to-a-random-secret-key-in-production SECRET_KEY=your-secret-key-change-in-production
# development | production — controls Swagger/ReDoc visibility and cookie defaults # development | production — controls Swagger/ReDoc visibility and cookie defaults
ENVIRONMENT=development ENVIRONMENT=development