Add environment variables¶
Environment variables are name/value pairs that are dynamically loaded into your containers at runtime. They are often used to pass configuration details to your application. Using environment variables instead of hard-coded values lets you keep environment-specific details out of your source code.
You will add secrets in one of two ways, depending on which CI solution you choose:
If you're using an external CI provider, such as GitHub Actions, GitLab CI, or CircleCI, environment variables should be stored via your provider's interface and referenced in your Docker Compose template using the
Docker Compose element
env_file is not currently support for external CI providers.
If you're using Uffizzi CI, you have two options for adding environment variables in your Uffizzi Compose file:
environmentif you have a small number of environment variables to add. You can list your variables in an
environmentblock within the service definition. For example, the following
docker-compose.uffizzi.ymlsnippet adds two environment variables,
BAR, to the
env_fileif you have a large number of enviroment variables that would otherwise clutter up your compose file. You can store your variables in a file within your repository and use the
env_filecomponent to specify the path to this file. For example, the following
docker-compose.uffizzi.ymlsnippet tells Uffizzi to read the contents of
envs/myconfigs.envand add them to the container