You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ You can learn a lot about how this plugin is used by browsing the [documentation
13
13
14
14
## Configuration
15
15
16
-
Important: this plugin assumes that your docker compose file is called `docker-compose.yml`. If your file is called diferently, make sure to set plugin's `config` option or - more generally - set the pipeline-level environment variable `COMPOSE_FILE` with the right value. This is due to the possible usage of a custom-named override files in some situations and can not be worked around due to limitations of docker's `-f` option.
16
+
Important: this plugin assumes that your docker compose file is called `docker-compose.yml`. If your file is called differently, make sure to set plugin's `config` option or - more generally - set the pipeline-level environment variable `COMPOSE_FILE` with the right value. This is due to the possible usage of a custom-named override files in some situations and can not be worked around due to limitations of docker's `-f` option.
17
17
18
18
### Main Commands
19
19
@@ -87,7 +87,7 @@ If you set this to `VALUE`, and `VALUE` is an environment variable containing a
87
87
88
88
Whether or not to automatically propagate all pipeline environment variables into the run container. Avoiding the need to be specified with environment.
89
89
90
-
**Important**: only pipeline environment variables will be propagated (what you see in the BuildKite UI, those listed in `$BUILDKITE_ENV_FILE`). This does not include variables exported in preceeding`environment` hooks. If you wish for those to be propagated you will need to list them specifically or use `env-propagation-list`.
90
+
**Important**: only pipeline environment variables will be propagated (what you see in the Buildkite UI, those listed in `$BUILDKITE_ENV_FILE`). This does not include variables exported in preceding`environment` hooks. If you wish for those to be propagated you will need to list them specifically or use `env-propagation-list`.
0 commit comments