Configuration Profiles Per Environment #44
Description
Why
Prevent unsafe defaults in production and noisy settings in development.
Definition of Done
- Separate profiles exist for development, test, and production.
- Each profile sets ports, logging levels, timeouts, limits, and paths.
- Environment variables override documented defaults.
- Missing or invalid configuration fails fast with a clear message.
Tasks
- Define a configuration structure with layered sources.
- Provide sample files for each profile.
- Validate configuration on startup and exit on error.
- Document all keys and defaults.