From 7fb2be86ee1d907cecfbd83c93deba7b8118836d Mon Sep 17 00:00:00 2001 From: hygienic-books Date: Sun, 11 Jun 2023 23:05:23 +0200 Subject: [PATCH] docs(meta): Better distiguish component_list entry examples --- docker-compose/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docker-compose/README.md b/docker-compose/README.md index 2869ead..1b2bd2c 100644 --- a/docker-compose/README.md +++ b/docker-compose/README.md @@ -66,7 +66,7 @@ Your four answers translate as follows into rendered files. └── grafana ... └── env - └── fully.qualified.domain.name.example <--- + └── fqdn_context.env.example <--- ``` Which then looks like: @@ -132,7 +132,7 @@ Consider Cookiecutter's project directory and rendered files a starting point. I Imagine if you will a service that consists of [Infinispan](https://infinispan.org/) among other things. In Docker Hub's content-addressable image store Infinispan's location is at `infinispan/server` so you obviously want that exact string with a forward slash to show up in your `docker-compose.yml` as the `image:` key's value, same with your `Dockerfile`. The `image:` key's value comes from what you enter in Cookiecutter's `component_list` prompt. Component strings are then used to also pre-fill the `volumes:` key. -This will cause obvious issues (but the `image:` key is kinda correct): +_**This**_ will cause obvious issues (but the `image:` key is kinda correct): ``` services: infinispan/server: @@ -140,7 +140,7 @@ services: container_name: "cacheman-infinispan/server-${CONTEXT}" ``` -This won't cause issues (but you'll have to then go in and manually change the `image:` key to use `infinispan/server`): +_**This**_ won't cause issues (but you'll have to then go in and manually change the `image:` key to use `infinispan/server`): ``` services: infinispan: