In ASP.NET Core world, we have appsettings.{environment}.json
, do we have similar thing in docker's world?
My scenario is, I have a docker-compose.yml
file that starts a couple of container services. But during the integration tests, I want to start an additional container service just for integration tests. I know I can't use .env
file to specify environment to be used in the docker-compose.yml
file. But I don't want the specified container service to be created and started in non-integration environment, which means I don't want to start the container and overwrite the setting based on passing environemnt from .env
file, I want docker-compose.yml
completed ignores the container service for non-integration environments.
so is it something like docker-compose-{environment}.yml
like appsettings.{environment}.json
that can be merged?