The Config That Swallowed Prod

A deploy to production succeeds. Traffic still hits the laptop-friendly defaults. ENVIRONMENT is set to 'production', but the resolver only recognizes the short token 'prod', so every host silently inherits DEVELOPMENT.

Initial failing signalproduction env still resolves dev DBExpected behavior: Production resolves to postgres://prod-db/app. · actual behavior: Production resolves to the development database postgres://localhost:5432/app_dev.

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Build an environ with ENVIRONMENT=production.
Call resolve_settings.
Check database_url is the production profile value.

Focus Mode

Start

src/settings.py
src/loader.py

Likely area

src/settings.py
src/loader.py
src/profiles.py

Challenge Coach

Hints reveal broad direction first, then narrow toward the suspect path without showing hidden tests or exact solution code.

TopicConfig & Environment

DifficultyMedium

Est. time15 min

Workspacepreparing

Explorer

Loading files

Evidence Map

Failing signal loaded from challenge API
Workspace files loaded from workspace API
Results rendered only after API run/submit

Autosaved

workspace

Outputread-onlyready$ prepare workspace

Preparing workspace