Skip to content

Commit a5ca186

Browse files
committed
Revert _data/compose-cli/docker_compose.yaml
This reverts part of commit 9ce29a8. As @glours noted in the review of #16915, this content comes from the upstream docker/compose repo. He's opened docker/compose#10390 to apply the update there instead. Signed-off-by: Mike Bland <[email protected]>
1 parent 9ce29a8 commit a5ca186

File tree

1 file changed

+3
-15
lines changed

1 file changed

+3
-15
lines changed

_data/compose-cli/docker_compose.yaml

Lines changed: 3 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -63,21 +63,9 @@ long: |-
6363
6464
### Use `-p` to specify a project name
6565
66-
Each configuration has a project name. Compose sets the project name using
67-
the following mechanisms, in order of precedence:
68-
69-
- The `-p` command line flag
70-
- The `COMPOSE_PROJECT_NAME` environment variable
71-
- The top level `name:` variable from the config file (or the last `name:`
72-
from a series of config files specified using `-f`)
73-
- The `basename` of the project directory containing the config file (or
74-
containing the first config file specified using `-f`)
75-
- The `basename` of the current directory if no config file is specified
76-
77-
Project names must contain only lowercase letters, decimal digits, dashes,
78-
and underscores, and must begin with a lowercase letter or decimal digit. If
79-
the `basename` of the project directory or current directory violates this
80-
constraint, you must use one of the other mechanisms.
66+
Each configuration has a project name. If you supply a `-p` flag, you can specify a project name. If you don’t
67+
specify the flag, Compose uses the current directory name.
68+
Project name can also be set by `COMPOSE_PROJECT_NAME` environment variable.
8169
8270
Many Compose subcommands can be run without a Compose file by passing
8371
the project name.

0 commit comments

Comments
 (0)