vh
39da1d4a97
The board mixed tools with endpoints. A vLLM seat whose href is a /docs page
sat in the same band as ComfyUI; the MQTT broker and the RustDesk relay, which
have no page at all, sat in Apps; and `Service Networking` was thirteen members
spanning three AdGuards, five Dockges, two Traefiks and four headless agents.
Every group is now one of two kinds and they never mix. TOOLS are expanded and
sit at the top of their tab. ENDPOINTS — an API, a broker, a background agent,
an href that is /docs or /ping or nothing — carry `initiallyCollapsed: true`
and sit at the bottom. Collapsed is not hidden: the eyebrow and its rule still
render, so the tab still says the thing exists and one click expands it.
A second rule fell out of the same pass and now shapes the group boundaries: a
group's members should all carry a widget or none should. A stat strip makes a
card ~50px taller, so one widget card in a row of plain ones opens a void under
the plain ones. That is why AdGuard and Traefik get their own groups rather
than sharing one with Dockge, and it is most of why the old Service Networking
band looked broken. AdGuard (ANA) was the last short card in its row and now
carries the same query/blocked/latency strip as its two siblings — one
infra-ops AdGuard login authenticates against all three instances, verified
against each; it lives in that stack's .env on the host and is vaulted.
The sixteen GPU-backed model seats were deliberately NOT relabelled.
`homepage.group` is read at container creation, so clearer names for
`AI - Inference` and friends would have cost a recreate on six vLLM seats, four
eval seats and four TTS engines — multi-minute model reloads on endpoints peers
reach through the gateway. Order plus `initiallyCollapsed` buys the same
separation for nothing, so those names stay as they are on purpose.
28 containers that ARE cheap to bounce were relabelled, across five hosts, via
rerunnable elway playbooks. Their label steps are gated on the old value still
being present, so a second run reports skipped rather than churning. Two verify
steps were wrong on first contact and are fixed with the reason recorded: the
traefik check raced its own recreate, and asserting a model seat is "running"
cannot answer "did I bounce it" when a seat may be legitimately stopped —
container age can, and now does.
The canonical stacks/ tree was synced to the deployed labels afterwards, so
intent and reality agree again on all fourteen tracked stacks.
Also documents the real nature of the post-recreate blank dashboard, which cost
~25 minutes here and an hour on 2026-08-19. `initialSettings":{}` in the served
HTML is the catch branch of the page's data loader, not a warm-up and not a
cache — and the error can vanish entirely, because the logger is assigned inside
the same try and the catch only logs if the logger exists. Ruled out by
measurement this time: all four API routes return 200 with correct content while
the page serves {}, and the previous known-good settings.yaml reproduces it
identically. The README now carries the one-command test and the next lead.
Before/after, all four tabs: http://10.100.10.50:8090/b/homepage-relayout/
71 lines
3.0 KiB
YAML
71 lines
3.0 KiB
YAML
# adguard-ana — the Anaheim colo's resolver.
|
|
#
|
|
# Stood up 2026-08-19 to close the gap found while designing the .internal
|
|
# naming scheme: ESH and NH3 each had an AdGuard, but colo hosts were
|
|
# resolving straight against 1.1.1.1, so the colo had no way to answer for
|
|
# internal names at all.
|
|
#
|
|
# ⚠️ PORTS DIFFER FROM THE OTHER TWO SITES. ana-docker is a busy host: :8080
|
|
# and :3000 are already taken (langfuse and friends), so AdGuard's web UI and
|
|
# API live on :8053 here, not :8080. Anything that talks to this API — notably
|
|
# scripts/dns-sync.py — reads the port from dns/internal.yaml rather than
|
|
# assuming the ESH/NH3 value.
|
|
#
|
|
# ⚠️ THIS IS NOT YET THE COLO'S RESOLVER-OF-RECORD. Standing the service up and
|
|
# repointing a whole site's DNS are two different changes with two different
|
|
# blast radii. Colo hosts still use 1.1.1.1; the cutover is a separate,
|
|
# operator-approved step. Until then this answers only what asks it directly.
|
|
#
|
|
# ESH and NH3 run their own, older, unmanaged compose files. They were left
|
|
# alone deliberately — adopting three live resolvers into this repo while also
|
|
# introducing a new naming system is two risky changes at once. Worth doing
|
|
# later, as its own piece of work.
|
|
|
|
name: adguard-ana
|
|
|
|
services:
|
|
adguardhome:
|
|
image: adguard/adguardhome:latest
|
|
container_name: ${AG_CONTAINER:-adguardhome}
|
|
restart: unless-stopped
|
|
ports:
|
|
- "${AG_DNS_PORT:-53}:53/tcp"
|
|
- "${AG_DNS_PORT:-53}:53/udp"
|
|
# Web UI + REST API. 8053, not 8080 — see the note above.
|
|
- "${AG_WEB_PORT:-8053}:80/tcp"
|
|
volumes:
|
|
- adguard_work:/opt/adguardhome/work
|
|
- adguard_conf:/opt/adguardhome/conf
|
|
networks:
|
|
- tnet
|
|
labels:
|
|
- homepage.group=DNS & Filtering
|
|
- homepage.name=AdGuard (ANA)
|
|
# si-adguard, matching the ESH and NH3 instances. This carried mdi-dns
|
|
# and was the only one of the three wearing a different mark.
|
|
- homepage.icon=si-adguard
|
|
- homepage.description=DNS resolver + .internal zone (colo)
|
|
- homepage.href=http://10.250.50.70:${AG_WEB_PORT:-8053}
|
|
- homepage.siteMonitor=http://10.250.50.70:${AG_WEB_PORT:-8053}
|
|
# Query/blocked/latency strip, same as ESH and NH3. Added 2026-08-24:
|
|
# without it this was a short card sitting beside two tall ones, which
|
|
# is the whole reason the DNS group exists as its own band — a group's
|
|
# members should all carry a widget or none of them should.
|
|
# Credential is the fleet AdGuard `infra-ops` login, which authenticates
|
|
# against all three instances; it lives in this stack's .env on the host
|
|
# (never in git) and is vaulted at
|
|
# `secret get nh3-dev/adguard-infra-ops-password`.
|
|
- homepage.widget.type=adguard
|
|
- homepage.widget.url=http://10.250.50.70:${AG_WEB_PORT:-8053}
|
|
- homepage.widget.username=infra-ops
|
|
- homepage.widget.password=${ADGUARD_WIDGET_PASSWORD}
|
|
|
|
volumes:
|
|
adguard_work: {}
|
|
adguard_conf: {}
|
|
|
|
networks:
|
|
tnet:
|
|
name: traefik-net
|
|
external: true
|