An environment-level setting changes between deployment environments such as development, testing, and production. Keep it separate from release-level settings, which remain fixed for a release, and feature-level settings, which control behavior between releases. section 18.1
A practical configuration hierarchy starts with defaults packaged in the image, adds override files from a mounted filesystem, and allows environment variables to replace specific values. This lets identical images run with different environment settings. section 18.1
Run one image in two environments
Run the default container on port 8080, then mount config/dev at /app/config-override and run another copy on port 8081. Query both /config endpoints: the first reports UNKNOWN for the environment name, while the second applies the development override. Add -e APP_METRICS_ENABLED=true to change one setting without changing the file. section 18.1
