Skip to content

Commit 3c3bd8f

Browse files
authored
Fix example usage of COMPOSE_ENV_FILES (#23253)
## Description The example results in the second file being a command to be executed and not part of the environment variable's value. Quoting the value would address it as well, but thought it far more likely the space was an accident rather than trying to show an example of files containing spaces.
1 parent e3f57f0 commit 3c3bd8f

File tree

1 file changed

+1
-1
lines changed
  • content/manuals/compose/how-tos/environment-variables

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -119,7 +119,7 @@ Specifies which environment files Compose should use if `--env-file` isn't used.
119119
When using multiple environment files, use a comma as a separator. For example:
120120

121121
```console
122-
COMPOSE_ENV_FILES=.env.envfile1, .env.envfile2
122+
COMPOSE_ENV_FILES=.env.envfile1,.env.envfile2
123123
```
124124

125125
If `COMPOSE_ENV_FILES` is not set, and you don't provide `--env-file` in the CLI, Docker Compose uses the default behavior, which is to look for an `.env` file in the project directory.

0 commit comments

Comments
 (0)