From 5b3abd4d104ea58e2e9bc07c3505317fd367cd5b Mon Sep 17 00:00:00 2001 From: minottic Date: Thu, 4 Jul 2024 20:38:52 +0200 Subject: [PATCH] Add additional extra line --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index 66462155..26251d4e 100644 --- a/README.md +++ b/README.md @@ -212,6 +212,7 @@ To add a new service, with advanced configuration (see the [backend](./services/ 3. create a symlink from [.empty.yaml](./services/.empty.yaml) to each `.compose..yaml`, e.g. [here](./services/backend/services/v4/.compose.elastic.yaml). This is used whenever the `ENV` is unset, as described in the next step 4. use `compose.yaml` to merge the `compose*.yaml` files together, making sure to default to `.compose..yaml` whenever the `ENV` is not set. See an example [here](./services/backend/services/v4/compose.yaml) 5. if the service is another version of an existing one, e.g. v3 and v4 versions of the `backend` service, add the selective include in the parent compose.yaml, e.g. [here](./services/backend/compose.yaml) + 4. eventually, add entrypoints for init logics, as described [here](#if-the-service-does-not-support-entrypoints-yet-one-needs-to), e.g. like [here](./services/backend/services/v4/compose.base.yaml)