I have a question regarding the config files: In “...
# docker
s
I have a question regarding the config files: In “normal” environments, the order is “config_default -> config_default-environment -> config_default-store -> config_default_environment-store -> config_local”, but in docker, config_default-docker-store requires config_default-docker, overwriting settings in the config_default-store. This makes it a bit difficult to keep it “in sync” with the config structure for other environments. What is the reasoning for this and are there plans to return to the standard order of config files again?
q
well, yes. there is a lot in config_default-docker that is not specific for docker and thus it overrides too much
someone was a little bit too eager here
you could probably check against config_default what did not change and can be removed from config_default-docker
s
and then remove the require from config_default-docker-store?
will start my new week with that. thx
q
sounds like a fun week 😄 👍
h
Removing require from config_default-docker-store would broke the docker setup. It can be done but carefull. Look for configuration keys in config-default-docker to be NOT overridden by config-default-store.