rdash-env-var-naming-drift-breaks-prod-boot
docker-compose.prod.yml and k8s manifests used env var names the app never reads (e.g. RDASH_SESSION_SECRET, DATABASE_URL, REDIS_URL) while the app reads RDASH_JWT_SECRET, RDASH_DATABASE_URL, RDASH_REDIS_URL via RDASH_ prefix. Without fixing, the app boots in production with all dev defaults silently — no error, no warning. Always audit env var names end-to-end from app Settings class to compose/k8s injection before any deploy.
Related
- docker
- subagents-blocked-writing-to-root-claude-skills
- openclaw
- inotify-max-user-instances-exhausted-by-docker-shims
- alembic-ini-hardcoded-url-triggers-secret-scanner
- module-level-env-reads-with-dev-fallback-bypass-runtime-conf
- pydantic-prod-safety-validator-rejects-dev-defaults-at-boot
- makefile-awk-help-regex-must-include-digit-character-class
- env-var-naming-drift-causes-silent-prod-boot-with-dev-defaul
- module-level-env-reads-bypass-runtime-env-in-python
- pydantic-model-validator-prod-safety-gate-pattern
- makefile-awk-help-extractor-excludes-digit-containing-target
- env-var-naming-drift-causes-silent-dev-defaults
- pydantic-settings-prod-safety-validator-pattern
- env-var-naming-drift-compose-vs-app-code
- makefile-awk-help-target-regex-excludes-digits
- prod-env-var-naming-drift-boots-with-dev-defaults