trails-cool/trails
1
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix(infra): IPv6 belongs on trails-shared, not a staging default network

Browse source 
Follow-up to #466: staging and preview services attach only to the
externally-named trails-shared network (created by the production
compose project) — they have no per-project default network, so the
enable_ipv6 added to the staging file was dead config. Move the flag
to trails-shared where it takes effect.

Rollout requires recreating trails-shared on the flagship: detach
staging, previews, and production postgres, remove the network, re-up.
Production journal/planner are unaffected (they use the default
network).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Ullrich Schäfer 2026-06-06 23:21:25 +02:00
parent fc8d35d7d4
commit 2d8046b9a6
2 changed files with 7 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

9
infrastructure/docker-compose.staging.yml
View file

@ -109,12 +109,9 @@ services:
memory: 256M
networks:
# IPv6 egress for staging/preview journals, matching production — see
# the production compose file for details. Preview networks are created
# fresh per PR; the persistent staging network needs a one-time
# down/up to pick this up.
default:
enable_ipv6: true
# Staging/preview services attach only to trails-shared — created (and
# IPv6-enabled) by the production compose project. There is no per-project
# default network here, so v6 egress comes from trails-shared itself.
trails-shared:
external: true
name: trails-shared