kevinveenbirkenbachandClaude Opus 4.8 0b57337032 fix(proxy): reach node-local force_bridge apps via the host gateway under swarm ...

A force_bridge app (matrix's MDAD flavor) deploys as a node-local compose stack and publishes its local port on its host, while openresty runs as an overlay task whose 127.0.0.1 is its own loopback; the readiness probe died on 502. The proxy_pass lookup now resolves networks.local.force_bridge (trust-tagged for the 2.19 templar, hard-failing on an unrendered template instead of silently falling back to loopback) and keys the decision on the real DEPLOYMENT_MODE, since such apps rewrite the effective mode to compose via compose_mode_force. The upstream becomes host.docker.internal:<local_port> rendered as a literal directive, because the request-time resolver cannot see /etc/hosts entries, and the swarm openresty service maps host.docker.internal to the host gateway like prometheus already does. Non-force_bridge renders stay byte-identical.

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

2026-07-18 01:11:48 +02:00

..

__init__.py

refactor(networks): replace Jinja includes with compose_networks/container_networks lookup plugins

2026-06-16 18:42:04 +02:00

proxy.py

fix(proxy): reach node-local force_bridge apps via the host gateway under swarm

2026-07-18 01:11:48 +02:00

render.py

fix(svc-runner): make the runner role swarm-compatible

2026-07-08 02:37:26 +02:00