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/
65 lines
2.4 KiB
YAML
65 lines
2.4 KiB
YAML
# rest-server (Anaheim) — restic backup target for the fleet.
|
|
#
|
|
# Deploys to ana-docker. Data dir is the NFS mount at
|
|
# /mnt/backup/restic/repo/ana, backed by the Debian 12 NFS/SMB file
|
|
# server at 10.250.50.50. (Historically a TrueNAS SCALE appliance; since
|
|
# reprovisioned as vanilla Debian.)
|
|
#
|
|
# Mirrors stacks/rest-server-nh3/ in every meaningful way — same auth
|
|
# model, same on-disk layout, same operational semantics — so each client
|
|
# host uses an identical URL shape against either endpoint:
|
|
#
|
|
# rest:http://<user>:<pw>@10.100.50.50:8000/<user>/ (NH3 Synology)
|
|
# rest:http://<user>:<pw>@10.250.50.70:8000/<user>/ (this stack)
|
|
#
|
|
# Auth model:
|
|
# --private-repos : URL path must start with /<user>/ and the HTTP
|
|
# basic-auth user must match. Per-host repos are
|
|
# strictly isolated.
|
|
# --append-only : on-disk data can be added but not removed or
|
|
# rewritten; a compromised host can't wipe its own
|
|
# history. Prune requires disabling this (see README).
|
|
#
|
|
# Credentials come from /data/.htpasswd — see README for populating it.
|
|
#
|
|
# All tunables live in .env — edit that, not this file.
|
|
|
|
services:
|
|
rest-server:
|
|
image: restic/rest-server:${REST_SERVER_VERSION}
|
|
container_name: rest-server
|
|
restart: unless-stopped
|
|
# Run as the UID that owns the NFS-backed data dir, so file I/O
|
|
# is not subject to NFS root_squash. On ana-docker this is lkraven (1000).
|
|
user: "${REST_UID:-1000}:${REST_GID:-1000}"
|
|
ports:
|
|
- "${REST_PORT}:8000"
|
|
volumes:
|
|
- ${DATA_DIR}:/data
|
|
environment:
|
|
- OPTIONS=--private-repos --append-only --prometheus ${EXTRA_OPTIONS:-}
|
|
- TZ=${TZ:-America/Los_Angeles}
|
|
healthcheck:
|
|
# TCP port probe — busybox nc ships in the restic/rest-server Alpine
|
|
# image. HTTP-level checks fight with --private-repos returning 401
|
|
# (busybox wget exit 8, gnu wget exit 6 — version-dependent and hard
|
|
# to branch on cleanly in POSIX sh).
|
|
test: ["CMD", "nc", "-z", "localhost", "8000"]
|
|
interval: 30s
|
|
timeout: 10s
|
|
retries: 3
|
|
start_period: 15s
|
|
networks:
|
|
- tnet
|
|
labels:
|
|
- homepage.group=Agents (no UI)
|
|
- homepage.name=Restic (rest-server)
|
|
- homepage.icon=mdi-cloud-upload
|
|
- homepage.description=Anaheim restic endpoint (data on NFS)
|
|
- homepage.href=http://10.250.50.70:${REST_PORT}
|
|
|
|
networks:
|
|
tnet:
|
|
name: traefik-net
|
|
external: true
|