Julien Calixte e05a86fad8 fix: put Traefik labels back, scoped to coolcouch, pinned to UUID net ...

The previous diagnostic showed Coolify does not auto-inject Traefik
labels just because SERVICE_FQDN_<NAME>_<PORT> is set — the container
had zero traefik.* labels after deploy, which is why the host returned
503. Adding explicit router+service labels and binding the docker
provider to the per-resource UUID network gives Traefik a definite
backend. Router/service names use the coolcouch prefix so they cannot
clash with any Coolify-managed couchdb router on the same install.

2026-06-01 21:07:30 +02:00

2.2 KiB

Raw Blame History

View Raw