Leonid PershinandClaude Opus 5 71dc3f2da8 Document reaching a proxy that lives in another container ...

A proxy published as 127.0.0.1:1080 is reachable from the host and
nowhere else — not via host.docker.internal either, since loopback
publishing never leaves the host. The fix is a shared docker network and
addressing the proxy by container name, so deploy/ now carries a ready
compose.override.yml example for exactly that, parameterised by
PROXY_NETWORK.

compose.override.yml is gitignored so a local deployment tweak cannot
collide with future pulls, the way the domain edit did.

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

2026-09-09 00:30:50 +03:00

..

Caddyfile.snippet

Run the panel as its own compose project behind the host Caddy

2026-09-08 23:16:04 +03:00

compose.proxy.yml.example

Document reaching a proxy that lives in another container

2026-09-09 00:30:50 +03:00

compose.stoat-network.yml.example

Run the panel as its own compose project behind the host Caddy

2026-09-08 23:16:04 +03:00