From f9e4c8c22437d577055fa701ab263d6d39329c27 Mon Sep 17 00:00:00 2001 From: Roberto Villarreal Date: Fri, 15 Aug 2025 16:26:02 -0600 Subject: [PATCH] Fix example usage of `COMPOSE_ENV_FILES` --- .../manuals/compose/how-tos/environment-variables/envvars.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/manuals/compose/how-tos/environment-variables/envvars.md b/content/manuals/compose/how-tos/environment-variables/envvars.md index 25ed517d2182..11ac8b64aeda 100644 --- a/content/manuals/compose/how-tos/environment-variables/envvars.md +++ b/content/manuals/compose/how-tos/environment-variables/envvars.md @@ -119,7 +119,7 @@ Specifies which environment files Compose should use if `--env-file` isn't used. When using multiple environment files, use a comma as a separator. For example: ```console -COMPOSE_ENV_FILES=.env.envfile1, .env.envfile2 +COMPOSE_ENV_FILES=.env.envfile1,.env.envfile2 ``` 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.