fix(traefik): route stalwart portal via canonical service name #2

Merged

ivoryghst merged 1 commit from fix/stalwart-canonical-name into trunk

2026-06-14 13:49:29 +01:00

ivoryghst commented

2026-06-14 13:40:33 +01:00

Owner

Same fix as ivoryghst/r2-d2#7, applied to optimus's traefik dynamic config.
Routes the apex/portal Stalwart routers at the canonical Swarm name
stalwart_stalwart:443 instead of the lost short alias / brittle VIP.

Safe to merge: optimus's deploy SKIPs the traefik stack and only re-syncs
stack/traefik/dynamic/ for the file watcher — no service recreate. Already
verified live (portal /admin/ -> 200 via optimus public edge).

🤖 Generated with Claude Code

Same fix as ivoryghst/r2-d2#7, applied to optimus's traefik dynamic config. Routes the apex/portal Stalwart routers at the canonical Swarm name `stalwart_stalwart:443` instead of the lost short alias / brittle VIP. Safe to merge: optimus's deploy SKIPs the traefik stack and only re-syncs `stack/traefik/dynamic/` for the file watcher — no service recreate. Already verified live (portal /admin/ -> 200 via optimus public edge). 🤖 Generated with Claude Code

ivoryghst added 1 commit

2026-06-14 13:40:33 +01:00

fix(traefik): route stalwart portal via canonical service name ef760f86ce

The `stalwart` short alias stopped resolving on stalwart_net after the
2026-06 swarm re-init (service endpoint aliases=[]); only the canonical
Swarm name `stalwart_stalwart` resolves. Point the apex/portal routers at
it instead of the interim hardcoded VIP — durable across recreation.

Verified live: portal.opmail.io/admin/ -> 200 via optimus public edge.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>