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>

This commit is contained in:

Leonid Pershin

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

co-authored by

Claude Opus 5

parent 380f7bcf31

commit 71dc3f2da8

3 changed files with 41 additions and 0 deletions

.gitignore

View File

@@ -6,3 +6,4 @@ web/node_modules/
 *.log
 data/
 *.tsbuildinfo
 compose.override.yml