From ab9a461090442a1b73a24abc66d64530ca6fa7e2 Mon Sep 17 00:00:00 2001 From: cellarspoon Date: Thu, 27 Jan 2022 11:08:36 +0100 Subject: [PATCH] add note on limits of domain sharing --- docs/operators/handbook.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/operators/handbook.md b/docs/operators/handbook.md index 548be9d5..bb99dc63 100644 --- a/docs/operators/handbook.md +++ b/docs/operators/handbook.md @@ -244,3 +244,7 @@ To deal with this, we make an additional "internal" network for each app which i ### Avoiding service namespace conflicts When referencing an `app` service in a config file, you should prefix with the `STACK_NAME` to avoid namespace conflicts (because all these containers sit on the traefik overlay network). You might want to do something like this `{{ env "STACK_NAME" }}_app` (using the often obscure dark magic of the Golang templating language). You can find examples of this approach used in the [Peertube recipe](https://git.coopcloud.tech/coop-cloud/peertube/src/commit/d1b297c5a6a23a06bf97bb954104ddfd7f736568/nginx.conf.tmpl#L9). + +## Domain sharing for apps + +At time of writing (Jan 2022), we think there is a limitation in our design which doesn't support multiple apps sharing the same domain (e.g. `example.com/app1/` & `example.com/app2/`). This may be possible to overcome if someone really needs it, we encourage people to investigate. We've found that often, there are limitations in the actual software which don't support this anyway and several of the current operators simply use a new domain per app.