docs/compose/compose-file
Edgars Baduns 7b6f2d918a
Clarify the source name of secrets and configs
The current wording of "name of the config as it exists in Docker" suggests that the real generated name is used, instead the "key" of `configs` object in the docker-compose file is used.

```yml
version: "3.5"

services:
  app:
    image: alpine
    configs:
      # documentation currently suggests this (the "name as in Docker")
      # this causes an error- undefined config "name-as-in-docker"
      - source: name-as-in-docker
        target: /config-with-name-as-in-docker.json

      # the correct source to use is the name (key) from this docker-compose file
      - source: name-as-in-file
        target: /config-with-name-as-in-file.json

configs:
  name-as-in-file:
    name: name-as-in-docker
    file: ./cfg.json
```
2021-04-13 19:28:07 +03:00
..
compose-file-v2.md Fix comment from Chris and update a note format 2021-03-16 13:41:11 +00:00
compose-file-v3.md Clarify the source name of secrets and configs 2021-04-13 19:28:07 +03:00
compose-versioning.md Fix comment from Chris and update a note format 2021-03-16 13:41:11 +00:00
index.md Remove Compose file v1 ref docs 2021-03-15 19:15:17 +00:00