From 7ada95b46a9dc511f68a92997772b722f3f70350 Mon Sep 17 00:00:00 2001 From: Jeff Emmett Date: Thu, 16 Apr 2026 18:42:44 -0400 Subject: [PATCH] fix(infra): sablier-support must be no-op until traefik wiring is ready Copying the sablier-encryptid.yml labels would immediately apply traefik.enable=false to the live encryptid container, breaking auth before Sablier has a middleware route in place. Reduced to empty services:{} with a comment explaining what's needed to activate. Co-Authored-By: Claude Opus 4.7 (1M context) --- docker-compose.sablier-support.yml | 23 +++++++++++++---------- 1 file changed, 13 insertions(+), 10 deletions(-) diff --git a/docker-compose.sablier-support.yml b/docker-compose.sablier-support.yml index 0bc0e74e..151c447b 100644 --- a/docker-compose.sablier-support.yml +++ b/docker-compose.sablier-support.yml @@ -1,10 +1,13 @@ -services: - encryptid: - labels: - - "sablier.enable=true" - - "sablier.group=encryptid" - - "traefik.enable=false" - encryptid-db: - labels: - - "sablier.enable=true" - - "sablier.group=encryptid" +# Sablier override — referenced by COMPOSE_FILE on Netcup. +# +# Currently a NO-OP placeholder so `docker compose` commands don't fail when +# COMPOSE_FILE includes this path. Real Sablier activation is deferred until +# Traefik middleware wiring is ready — see docker-compose.sablier-encryptid.yml +# for the encryptid label pattern, which cannot be applied in place because +# `traefik.enable=false` on the encryptid container would immediately break +# auth traffic without a Sablier-backed route in front of it. +# +# To activate: add sablier labels here AND configure Traefik dynamic config +# to route encryptid's hostname through the Sablier middleware. + +services: {}