Skip to content

Fix typos in the "Pre-defined environment variables in Compose" manual #22492

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ Compose can set the project name in different ways. The level of precedence (fro

1. The `-p` command line flag
2. `COMPOSE_PROJECT_NAME`
3. The top level `name:` variable from the config file (or the last `name:` from
3. The top-level `name:` variable from the config file (or the last `name:` from
a series of config files specified using `-f`)
4. The `basename` of the project directory containing the config file (or
containing the first config file specified using `-f`)
Expand Down Expand Up @@ -78,26 +78,26 @@ Specifies the path to a Compose file. Specifying multiple Compose files is suppo
```
The path separator can also be customized using [`COMPOSE_PATH_SEPARATOR`](#compose_path_separator).

See also the [command-line options overview](/reference/cli/docker/compose/_index.md#command-options-overview-and-help) and [using `-f` to specify name and path of one or more Compose files](/reference/cli/docker/compose/_index.md#use--f-to-specify-name-and-path-of-one-or-more-compose-files).
See also the [command-line options overview](/reference/cli/docker/compose/_index.md#command-options-overview-and-help) and [using `-f` to specify name and path of one or more Compose files](/reference/cli/docker/compose/_index.md#use--f-to-specify-the-name-and-path-of-one-or-more-compose-files).

### COMPOSE\_PROFILES

Specifies one or more profiles to be enabled when `docker compose up` is run.

Services with matching profiles are started as well as any services for which no profile has been defined.

For example, calling `docker compose up`with `COMPOSE_PROFILES=frontend` selects services with the
For example, calling `docker compose up` with `COMPOSE_PROFILES=frontend` selects services with the
`frontend` profile as well as any services without a profile specified.

If specifying multiple profiles, use a comma as a separator.

This following example enables all services matching both the `frontend` and `debug` profiles and services without a profile.
The following example enables all services matching both the `frontend` and `debug` profiles and services without a profile.

```console
COMPOSE_PROFILES=frontend,debug
```

See also [Using profiles with Compose](../profiles.md) and the [`--profile` command-line option](/reference/cli/docker/compose/_index.md#use---profile-to-specify-one-or-more-active-profiles).
See also [Using profiles with Compose](../profiles.md) and the [`--profile` command-line option](/reference/cli/docker/compose/_index.md#use-profiles-to-enable-optional-services).

### COMPOSE\_CONVERT\_WINDOWS\_PATHS

Expand Down Expand Up @@ -179,7 +179,7 @@ When enabled, Compose displays a navigation menu where you can choose to open th
- Supported values:
- `true` or `1`, to enable
- `false` or `0`, to disable
- Defaults to: `1` if you obtained Docker Compose through Docker Desktop, otherwise default is `0`
- Defaults to: `1` if you obtained Docker Compose through Docker Desktop, otherwise the default is `0`

### COMPOSE\_EXPERIMENTAL

Expand Down