docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

ENGDOCS-2257 (#21115) 

* ENGDOCS-2257

* clarify methods

* Update content/manuals/compose/how-tos/environment-variables/envvars.md
This commit is contained in:
Allie Sadler 2024-10-15 15:17:28 +01:00 committed by GitHub
parent f90323e7c2
commit 8c3965bd0d
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 2 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
content/manuals/compose/how-tos/environment-variables/envvars.md
View File

@ -31,8 +31,7 @@ This page contains information on how you can set or change the following pre-de
## Methods to override ## Methods to override
You can set or change the pre-defined environment variables: You can set or change the pre-defined environment variables:
- Within your Compose file using the [`environment` attribute](set-environment-variables.md#use-the-environment-attribute) - With an [`.env` file located in your working director](/manuals/compose/how-tos/environment-variables/variable-interpolation.md)
- With the `env-file` attribute and an [environment file](set-environment-variables.md#use-the-env_file-attribute)
- From the command line - From the command line
- From your [shell](variable-interpolation.md#substitute-from-the-shell) - From your [shell](variable-interpolation.md#substitute-from-the-shell)

3
content/manuals/compose/how-tos/environment-variables/set-environment-variables.md
View File

@ -68,7 +68,7 @@ services:
env_file: "webapp.env" env_file: "webapp.env"
``` ```
Using an `.env` file lets you to use the same file for use by a plain `docker run --env-file ...` command, or to share the same `.env` file within multiple services without the need to duplicate a long `environment` YAML block. Using an `.env` file lets you use the same file for use by a plain `docker run --env-file ...` command, or to share the same `.env` file within multiple services without the need to duplicate a long `environment` YAML block.
It can also help you keep your environment variables separate from your main configuration file, providing a more organized and secure way to manage sensitive information, as you do not need to place your `.env` file in the root of your project's directory. It can also help you keep your environment variables separate from your main configuration file, providing a more organized and secure way to manage sensitive information, as you do not need to place your `.env` file in the root of your project's directory.
@ -85,7 +85,6 @@ The paths to your `.env` file, specified in the `env_file` attribute, are relati
### Additional information ### Additional information
- If multiple files are specified, they are evaluated in order and can override values set in previous files. - If multiple files are specified, they are evaluated in order and can override values set in previous files.
- In addition, as the `.env` file supports [interpolation](variable-interpolation.md), it is possible to combine those with values set by `environment`.
- As of Docker Compose version 2.24.0, you can set your `.env` file, defined by the `env_file` attribute, to be optional by using the `required` field. When `required` is set to `false` and the `.env` file is missing, Compose silently ignores the entry. - As of Docker Compose version 2.24.0, you can set your `.env` file, defined by the `env_file` attribute, to be optional by using the `required` field. When `required` is set to `false` and the `.env` file is missing, Compose silently ignores the entry.
```yaml ```yaml
env_file: env_file: