Files
containers/images/vibe-kanban-remote/vibe-kanban.network
rob thijssen 3619470d79
Some checks failed
images / hermes (push) Failing after 17m32s
images / vibe-kanban-remote (push) Successful in 21m35s
docs(vibe-kanban-remote): commit the deployed quadlets
Mirrors the hermes convention of keeping the consuming quadlet alongside the
image definition. Four units: a private network, postgres 16 with
wal_level=logical, remote-server, and electric.

Records why the start order matters -- remote-server's migrations create the
electric_sync role, its grants and the publication that electric then connects
with, so electric cannot come up first -- and why electric has its own env
file, which is to avoid depending on systemd expanding one Environment= value
into another inside a quadlet.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TsmUEtbyTkgQ18tCFYXo1h
2026-07-20 18:26:25 +03:00

9 lines
304 B
SYSTEMD

# Private bridge for the vibe-kanban stack (postgres + electric + remote-server).
# Only remote-server publishes a host port (27180); postgres and electric are
# reachable only by container name on this network, never from the LAN.
[Network]
NetworkName=vibe-kanban
[Install]
WantedBy=multi-user.target