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/
Miniflux
Minimal self-hosted RSS reader (miniflux.app, Apache 2.0, ~30 MB Go single-binary). One unified inbox for tech blogs, Hacker News, Lobste.rs, and selected subreddits.
Why this stack
The fleet doesn't have a feed reader yet. Reddit subreddits expose
clean RSS feeds at https://reddit.com/r/<sub>/.rss, so subscribing
to your relevant subs alongside HN / blogs gives you a single place
to scan recent activity — no Reddit account needed, no polling
multiple sites by hand.
Self-hosted on ana-docker (10.250.50.70). Postgres bundled in the
stack rather than sharing pfi-postgres — keeps the dependency graph
flat and the DB is tiny (single-user).
Deploy
scripts/elway ana-docker --playbook playbooks/deploy-miniflux.yaml
Cold deploy budget: ~250 MB image pull (postgres:16 + miniflux), ~10 s startup, ~1 s warmup.
After deploy, the .env on ana-docker still has placeholder passwords — edit those before first start succeeds:
ssh ana-docker '
cd /opt/docker/compose/miniflux
sed -i "s|^MINIFLUX_DB_PASSWORD=.*|MINIFLUX_DB_PASSWORD=$(openssl rand -base64 24)|" .env
sed -i "s|^MINIFLUX_ADMIN_PASSWORD=.*|MINIFLUX_ADMIN_PASSWORD=$(openssl rand -base64 18)|" .env
grep ^MINIFLUX_ADMIN_PASSWORD .env # one-time copy this for first login
docker compose up -d
'
Then login at http://10.250.50.70:8080 with the username from .env
(lkraven by default) and the printed admin password.
Initial feed setup — OPML import
A starter OPML at stacks/miniflux/starter-feeds.opml covers:
- Hacker News + Lobste.rs
- r/selfhosted, r/homelab, r/LocalLLaMA
- r/nba (with spoiler caveat — see below)
Import via Miniflux UI: Settings → Import → Choose File → select the OPML → Submit. All feeds appear in their categories; first refresh fetches the most recent posts within seconds.
r/nba spoiler block-list
Subreddit-RSS titles for game-day threads include final scores
(e.g. Lakers 108 - Warriors 102 [Final]). Miniflux supports
per-feed regex block rules to skip these.
After importing the OPML:
-
Go to Feeds → click r/nba → Edit Feed
-
In the Block Filter field, paste:
\b\d{2,3}\s*[-–]\s*\d{2,3}\b|\[Final|Final Score|Game Thread.*\d{2,3} -
Save. Past matching entries stay (they were already fetched); future fetches skip score-bearing headlines. Discussion threads, highlights, and meta-content still come through.
If a real post slips through with a score in the title, refine the regex.
Adding subreddits later
Reddit RSS URL patterns:
| URL | Returns |
|---|---|
https://reddit.com/r/<sub>/.rss |
Newest posts (firehose) |
https://reddit.com/r/<sub>/top/.rss?t=day |
Top-of-day (less spam) |
https://reddit.com/r/<sub>/top/.rss?t=week |
Top-of-week |
https://reddit.com/r/<sub>/hot/.rss |
Currently hot |
top/.rss?t=day is the lowest-noise option for high-volume subs
where you want highlights only.
In Miniflux: Feeds → New Feed → URL, paste, pick a category.
Backup
Miniflux state lives in the named volume miniflux-db-data. To
include in restic, add a pre-backup.sh step on ana-docker that
dumps the DB to a stage path:
docker exec miniflux-db pg_dump -U miniflux miniflux \
> /var/lib/restic/stage/miniflux.sql
Then restic's regular sweep picks up the SQL file. Subscriptions and read-state are tiny (~MB even with months of history); the dump is fast.
Updating
ssh ana-docker '
cd /opt/docker/compose/miniflux
sed -i "s|^MINIFLUX_VERSION=.*|MINIFLUX_VERSION=<new>|" .env
docker compose pull miniflux
docker compose up -d
'
Migrations run automatically on container start (RUN_MIGRATIONS=1
in compose.yaml).