Sometimes it might be useful to define multiple configurations (e.g. for deploying to different environments). To support this case, DevSpace CLI allows you to create the file
.devspace/configs.yaml where you can define multiple configurations.
Using multiple configs is an advanced feature. To define a different behavior for
devspace dev, you should consider overriding the entrypoints of your images and make sure you consider the best practices for development with DevSpace.
Defining multiple configurations
Multiple configurations can be defined in
.devspace/configs.yaml (note the
config1: config: path: .devspace/config.yaml config2: config: data: version: v1alpha2 dev: ... deployments: ... images: ...
A config can either be loaded from a
path or it can be defined directly inside
.devspace/configs.yaml using the
The above example defines two configurations. The first one is called
config1 and will be loaded from the path
.devspace/config.yaml. The second one is called
config2 and is directly defined within the
data section in this
Instead of creating multiple completely different configuration files, it is often much better to use config overrides which allow you to have multiple slightly different configurations on top of a single configuration file.
Switching between multiple configs
To switch between different configs, you can run:
devspace use config [CONFIG_NAME]
After adding a newly created
.devspace/configs.yamlto your project, you will need to run
devspace use config [CONFIG_NAME]to tell DevSpace CLI which configuration to use.
List all configs
To get a list of defined config, you can run:
devspace list configs