m17hr1l/psyc
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

stage-28: make the proxy docker network name configurable per environment

Browse Source 
On AnD0R the reverse-proxy lives on the 'backend' docker network; on
cloud.neuronetz.ai it's 'neuronetz_default'. With a hardcoded name the
cockpit ended up on a network the prod proxy couldn't see and routing
silently dropped. Network is now overridable via PSYC_PROXY_NETWORK in
.env (default 'backend' keeps dev working).

On prod, set PSYC_PROXY_NETWORK=neuronetz_default in .env before the
next compose up.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
m17hr1l
2026-05-25 16:45:47 +02:00
parent 92f754e012
commit fad7ad0d49
2 changed files with 12 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
.env.example
View File

@@ -20,6 +20,13 @@ NVD_API_KEY=
# without a reachable acme-companion + public DNS + :443).
# LETSENCRYPT_EMAIL=admin@neuronetz.ai
# --- Production-only: the docker network the reverse-proxy is on ---
# Cockpit must share this network with nginx-proxy + acme-companion so the
# proxy can route to it. Default 'backend' matches AnD0R dev; on cloud
# production this is typically 'neuronetz_default' (whatever the proxy stack
# declares — check with `docker network ls`).
# PSYC_PROXY_NETWORK=neuronetz_default
# --- Internal service URLs — overridden in docker compose; defaults for venv CLI ---
# PSYC_MOCK_CERT_URL=http://127.0.0.1:8770
# PSYC_INFERENCE_URL=http://127.0.0.1:8771