Quico/py-cookiecutter-templates
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

docs(docker-compose): Align pointers

Browse Source
This commit is contained in:
hygienic-books 2022-06-06 04:42:40 +02:00
parent 4c88acc64b
commit d36e30638c
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docker-compose/README.md
View File

@ -24,7 +24,7 @@ Your four answers translate as follows into rendered files.
1. The `project_slug` is used only as directory name. A container named `vault` may be fine but the project directory name `hashicorpvault` might be more descriptive.
```
.
└── hashicorpvault <--- Here
└── hashicorpvault <--- Here
├── build-context
│   ├── docker-data
│   │   └── .gitkeep
@ -50,13 +50,13 @@ Your four answers translate as follows into rendered files.
3. Treat `component_list` as the list of Docker images that make up your service. Each `docker-compose` project forms a *__service__* - see above - that consists of either a single or multiple *__components__*. They're your `services:`, your container, volume, variable names etc.:
```
services:
grafana: <---
image: "grafana:${GRAFANA_VERSION}" <---
container_name: "grafana-grafana-${CONTEXT}" <---
grafana: <---
image: "grafana:${GRAFANA_VERSION}" <---
container_name: "grafana-grafana-${CONTEXT}" <---
...
environment:
# GRAFANA_USER: ${GRAFANA_USER} <---
# GRAFANA_PASSWORD: ${GRAFANA_PASSWORD} <---
# GRAFANA_USER: ${GRAFANA_USER} <---
# GRAFANA_PASSWORD: ${GRAFANA_PASSWORD} <---
...
```
@ -66,7 +66,7 @@ Your four answers translate as follows into rendered files.
└── grafana
...
└── env
└── fully.qualified.domain.name.example <---
└── fully.qualified.domain.name.example <---
```
Which then looks like: