You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It could be nice to have a feature to manage multiple compose environment.
As the environment settings is commonly done, the main compose config would be the default base and possible additional environment would inherit from it and override necessary var.
Still need to find how to manage it well from compose manifest in YAML file, how everything could adopt this feature and if it is not wrong idea that could lead to messy things.
The text was updated successfully, but these errors were encountered:
Where the target environment would be dev. Composer should first get the base sections then look ahead for the targetted environment in section and overrides the base variable with the extra ones from environment.
From composer cli, the target environment would be defined with argument --env dev . The API may need some additional non positionnal argument to target environment in code.
It could be nice to have a feature to manage multiple compose environment.
As the environment settings is commonly done, the main compose config would be the default base and possible additional environment would inherit from it and override necessary var.
Still need to find how to manage it well from compose manifest in YAML file, how everything could adopt this feature and if it is not wrong idea that could lead to messy things.
The text was updated successfully, but these errors were encountered: