Docker commonly passes settings via environment variables.
It could be useful if when resolving settings for production configuration this could also evaluate environment variables instead of deployed static values.
Thus the container drives the behavior of the production.
When productions are packaged and deployed the environment variable names are transprted with the export as with static values for production settings.
A suggestion from community is for System Default Settings to:
1) First try using the named environment variable if defined
2) Otherwise fallback to a given "Settings Value"
In first case, the REPORT on what settings are in effect should be expanded to indicate is from Operating System Environment Variable. See attached.
Thank you for submitting the idea. The status has been changed to "Needs review".