Multiple environment ?

[sveetch]

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.

[sveetch]

This could be done with extra section for environment like:

[tool.project_composer.dev]
collection = [
    "debug_toolbar",
    "admin-tools",
]
syspaths = [
    ".",
    "./mystuff/",
]

[tool.project_composer.requirements.dev]
template = "requirements/base_dev_template.txt"

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.

[sveetch]

The job would to be implemented almost in Manifest.load() with a new keyword argument env which, when defined, will load the base configuration from manifest, then overwrite configuration with existing value in the section related to the env. Since we have multiple format with different structures we will need to perform this on each format.