Compare commits

..

2 Commits

Author SHA1 Message Date
Jeff Emmett 8dc1c11227 Merge branch 'dev'
CI/CD / deploy (push) Successful in 2m16s Details
2026-04-16 18:42:51 -04:00
Jeff Emmett 7ada95b46a 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) <noreply@anthropic.com>
2026-04-16 18:42:44 -04:00
1 changed files with 13 additions and 10 deletions

View File

@ -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: {}