From 0ac46ecadb14fe37f69e1c4cf26bd3fd449b59f2 Mon Sep 17 00:00:00 2001 From: Julien Calixte Date: Mon, 1 Jun 2026 21:27:19 +0200 Subject: [PATCH] docs: explain hardcoded host and Coolify network UUID Coolify does not interpolate ${...} inside the labels: block, so the two strings tying this template to its specific Coolify resource cannot currently be variables. Document where they appear and how to swap them when redeploying as a new resource. --- README.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/README.md b/README.md index 45da022..9b4edfa 100644 --- a/README.md +++ b/README.md @@ -32,6 +32,17 @@ If the init logs show CORS errors, you can re-trigger only that step by redeploy Wildcard origin (`*`) with `credentials = false` — the only browser-spec-legal combination with a wildcard. For credentialed auth from the browser, edit the `put_config cors origins`/`credentials` lines in `docker-compose.yml`. +## Hardcoded values (cloning to another Coolify resource) + +Two strings in `docker-compose.yml` are pinned to this specific Coolify deployment and must be updated if you redeploy as a new resource: + +- The host in `traefik.http.routers.coolcouch.rule=Host(`couch.apoena.dev`)` +- The per-resource Coolify network name, appearing twice: `traefik.docker.network=lvw8efvnvsxduodrkg68zul3` and `networks.coolify.name: lvw8efvnvsxduodrkg68zul3` + +They're hardcoded because Coolify does not interpolate `${...}` inside the `labels:` block (it does inside `environment:` and `networks..name:`). The network UUID matches `COOLIFY_RESOURCE_UUID` for the resource — find it in Coolify's UI or in `docker network ls` after first deploy. + +A `sed` swap before push, or a Coolify "Custom Build Command" running `sed -i` over the file, is the simplest way to keep this template portable. + ## Files - `docker-compose.yml` — services, volume, Traefik labels, init sidecar