Every fv-ml1 link on the Homepage dashboard was broken. Measured against the
live dashboard API before the fix: 16 entries pointing at the dead 10.250.50.54
and zero at the live 10.251.50.54, covering gen, M.O.G.-SEC, Scriberr, Embed,
Rerank, Reward, Coder, Dockge and six dormant seats.
The miss was structural, not careless. fv-ml1-rename-sweep.sh works from an
allowlist assembled from files that mention the HOST, and a homepage.href label
mentions only an IP -- so every stack whose sole stale reference was a label
fell outside it. The allowlist now covers those 24 files, and records how to
derive the list next time (grep the old address, subtract history) rather than
enumerating from memory.
History is still untouched, and the exclusions are now written down with the
reason each one keeps the old address: recorded benchmark results, whose
base_url is part of a measurement's provenance; the one LiteLLM comment
preserving a retired hand-test endpoint; and the cutover runbooks, where the old
address is the subject matter.
Two bugs found while applying it, both fixed here:
- deploy-stack.sh rejected any stack name containing a dot, so qwen3.5-122b,
qwopus3.5-122b and mistral-medium-3.5 could not be deployed by the script at
all. The check exists to stop path traversal, which means rejecting ".." and
"/" -- not every dot. Traversal is now rejected explicitly and tested.
- stacks/scriberr/.env.example allowed CORS only from the dead IP and from
scriberr.ana.internal, which no longer resolves; the box is at the fv site
and DNS already carries scriberr.fv.internal. The live .env had both stale
origins, i.e. an allowlist with nothing reachable in it.
Host side, applied separately: canonical pushed for the 16 stacks whose only
difference from the host was this renumber, and an in-place address-only fix for
the nine whose host copy has genuinely drifted or has no canonical copy, so that
drift survives for a deliberate reconciliation instead of being clobbered. Every
compose.yaml on fv-ml1 now reads 10.251.50.54. The labels themselves only take
effect at container creation, so the running containers still need recreating.
51 lines
1.6 KiB
Bash
51 lines
1.6 KiB
Bash
# dozzle stack tunables. Copy to `.env` on each server before deploying.
|
|
#
|
|
# cp .env.example .env
|
|
# # edit for this host
|
|
# docker compose up -d
|
|
#
|
|
# Same compose.yaml on both servers — COMPOSE_PROFILES picks the role.
|
|
|
|
# Image version — pin for reproducibility (`latest` for edge)
|
|
DOZZLE_VERSION=latest
|
|
|
|
# ------------------------------------------------------------------------
|
|
# On ana-docker (hub):
|
|
# COMPOSE_PROFILES=hub
|
|
# DOZZLE_HOSTNAME=ana-docker
|
|
# DOZZLE_REMOTE_AGENT=10.251.50.54:7007
|
|
#
|
|
# On fv-ml1 (agent):
|
|
# COMPOSE_PROFILES=agent
|
|
# DOZZLE_HOSTNAME=fv-ml1
|
|
# ------------------------------------------------------------------------
|
|
|
|
COMPOSE_PROFILES=hub
|
|
|
|
# Display name for this host in the UI (shown as a tab / section header).
|
|
DOZZLE_HOSTNAME=ana-docker
|
|
|
|
# ---- Hub-only -----------------------------------------------------------
|
|
|
|
# Host port for the web UI (container listens on 8080 internally).
|
|
DOZZLE_PORT=8088
|
|
|
|
# Comma-separated list of remote agents the hub should connect to.
|
|
# Leave blank if this host only views its own containers.
|
|
DOZZLE_REMOTE_AGENT=10.251.50.54:7007,10.100.50.40:7007
|
|
|
|
# Auth — `none` is fine behind the LAN / a reverse proxy with auth.
|
|
# Switch to `simple` and set USERNAME/PASSWORD to gate the UI itself.
|
|
DOZZLE_AUTH_PROVIDER=none
|
|
DOZZLE_USERNAME=
|
|
DOZZLE_PASSWORD=
|
|
|
|
# ---- Agent-only ---------------------------------------------------------
|
|
|
|
# Host port the agent listens on (container listens on 7007 internally).
|
|
DOZZLE_AGENT_PORT=7007
|
|
|
|
# Bind address — restrict to the LAN interface if you want belt-and-braces
|
|
# beyond what the firewall already enforces. Default 0.0.0.0 exposes on all.
|
|
DOZZLE_AGENT_BIND=0.0.0.0
|