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/
235 lines
9.0 KiB
YAML
235 lines
9.0 KiB
YAML
---
|
||
# https://gethomepage.dev/latest/configs/services
|
||
#
|
||
# Groups are ordered by settings.yaml `layout`. This file holds the manual
|
||
# entries — infrastructure, BMCs, off-Docker endpoints, and a handful of
|
||
# well-known internal service URLs. Docker-labeled stacks auto-populate
|
||
# their own groups through the providers in docker.yaml, so most app
|
||
# entries don't need to appear here.
|
||
|
||
# The Monitoring group is fully Docker-auto-discovered — Beszel, Dozzle,
|
||
# Backrest and Uptime Kuma all carry homepage.group=Monitoring on their
|
||
# compose files. There is deliberately no manual block here.
|
||
#
|
||
# Uptime Kuma used to be listed manually here AND labelled
|
||
# homepage.group=Apps on its container, so it rendered twice — once in
|
||
# Monitoring without its widget, once in Apps with it. Fixed 2026-08-18 by
|
||
# deleting the manual entry and moving the container's label to Monitoring
|
||
# (stacks/uptimekuma/). This is the exact failure the warning below
|
||
# describes; it survived the 2026-08-17 audit because a duplicate reads as
|
||
# two plausible cards rather than as an error.
|
||
|
||
- Apps:
|
||
# Manual entry — the Booth is a user-level systemd service on nh3-dev
|
||
# (not a Docker-labeled stack), so it can't auto-discover; list it here.
|
||
- The Booth:
|
||
href: http://10.100.10.50:8090/
|
||
icon: mdi-filmstrip
|
||
siteMonitor: http://10.100.10.50:8090/healthz
|
||
description: Media drop + upload-for-pickup + the standing agent link board — nh3-dev, 24h TTL except kept boards
|
||
- The Henge:
|
||
href: http://park.phasefinal.com:8420/
|
||
icon: mdi-clipboard-check
|
||
siteMonitor: http://park.phasefinal.com:8420/healthz
|
||
description: Durable needs-attention / idea parking (stonehenge-park) — ana-docker
|
||
# Was its own one-card `Games` group, which burned a full 4-wide row on a
|
||
# single panel. It is an app you open; this is where apps you open live.
|
||
- Pterodactyl:
|
||
href: http://10.250.50.55/
|
||
icon: mdi-gamepad-square
|
||
siteMonitor: http://10.250.50.55
|
||
description: Game server panel
|
||
|
||
# The AI tab is otherwise fully Docker-auto-discovered. Each service carries a
|
||
# homepage.group=AI - <role> label on its compose file (AI - Gateways & Chat,
|
||
# AI - Studios, AI - Inference, AI - Eval & Retrieval, AI - Speech (TTS),
|
||
# AI - Audio Tools, AI - Dormant). Tab assignment, group order, columns and
|
||
# collapse state live in settings.yaml. Do not add a labelled container here as
|
||
# well or it renders twice. To move a service between AI groups, change the
|
||
# label on its compose file and recreate the container — labels are read at
|
||
# creation, so `restart` will not do it.
|
||
- AI - Studios:
|
||
# Manual entry — Voice Design Studio is a user-level systemd service on
|
||
# irv-ml1, not a Docker-labeled stack, so it cannot auto-discover. It sits
|
||
# with the other studios rather than in Apps: it is a workspace you open and
|
||
# produce something in, which is exactly what that group is for.
|
||
- Voice Design Studio:
|
||
href: http://10.100.79.3:8216/
|
||
icon: mdi-microphone
|
||
siteMonitor: http://10.100.79.3:8216/health
|
||
description: Mint, audition and keeper-mark synthetic fleet voices — irv-ml1, CPU-only
|
||
|
||
- Media:
|
||
- Plex:
|
||
href: http://10.0.50.56:32400
|
||
icon: si-plex
|
||
siteMonitor: http://10.0.50.56:32400
|
||
description: Media Server (esh-nas-pve 10.0.50.56)
|
||
widget:
|
||
type: plex
|
||
url: http://10.0.50.56:32400
|
||
key: '{{HOMEPAGE_VAR_PLEX_KEY}}'
|
||
- Jellyfin:
|
||
href: http://10.0.50.57:8096
|
||
icon: si-jellyfin
|
||
siteMonitor: http://10.0.50.57:8096
|
||
description: Media Server (esh-nas-pve 10.0.50.57)
|
||
widget:
|
||
type: jellyfin
|
||
url: http://10.0.50.57:8096
|
||
key: '{{HOMEPAGE_VAR_JELLYFIN_KEY}}'
|
||
enableBlocks: true
|
||
|
||
- Infra - ANA:
|
||
- ANA-Firewall:
|
||
href: https://10.250.250.1
|
||
icon: mdi-wall-fire
|
||
siteMonitor: https://10.250.250.1
|
||
description: ana-gw FortiGate-80F, FortiOS 7.2.10 (ana-fw.phasefinal.com)
|
||
- PFI-r750xs-iDRAC:
|
||
href: https://10.250.250.30/
|
||
siteMonitor: https://10.250.250.30/
|
||
icon: si-dell
|
||
description: iDRAC (Dell R750xs) — OOB for pfi-pve @ 10.250.250.31
|
||
- PFI-PVE:
|
||
href: https://10.250.250.31:8006/
|
||
siteMonitor: https://10.250.250.31:8006/
|
||
icon: si-proxmox
|
||
description: Proxmox hypervisor (pfi-pve)
|
||
- ANA-NAS:
|
||
href: https://10.250.50.50:9090/
|
||
siteMonitor: https://10.250.50.50:9090/
|
||
icon: mdi-nas
|
||
description: Debian NAS (Cockpit)
|
||
- ANA-FileBot:
|
||
ping: 10.250.50.53
|
||
icon: mdi-sync-circle
|
||
description: File-task VM
|
||
- PFI-VM-Docker:
|
||
href: http://10.250.50.70:5001
|
||
icon: si-docker
|
||
siteMonitor: http://10.250.50.70:5001
|
||
description: Docker VM (ana-docker, Dockge at :5001)
|
||
- PFI-ANA-ML2:
|
||
ping: 10.250.50.54
|
||
icon: mdi-brain
|
||
description: GPU host (bare-metal)
|
||
- PFI-ANA-ML2 BMC:
|
||
href: https://10.250.250.50
|
||
icon: mdi-brain
|
||
siteMonitor: https://10.250.250.50
|
||
description: BMC (ana-ml2)
|
||
- SFsrv-ANA:
|
||
href: https://10.250.250.115:8006
|
||
icon: si-proxmox
|
||
siteMonitor: https://10.250.250.115:8006
|
||
description: Proxmox (SureFire tenant hypervisor at PFI colo)
|
||
- SF-R630-iDRAC:
|
||
href: https://10.250.250.110/
|
||
icon: si-dell
|
||
ping: 10.250.250.110
|
||
description: Dell R630 iDRAC (SureFire tenant hardware)
|
||
- PBS-ANA:
|
||
href: https://10.250.50.90:8007/
|
||
icon: mdi-backup-restore
|
||
siteMonitor: https://10.250.50.90:8007/
|
||
description: Proxmox Backup Server — primary (fleet vzdump target)
|
||
|
||
- Infra - NH3:
|
||
# NH3-Firewall (Fortigate 101F at 10.100.250.1) retired 2026-04-21,
|
||
# replaced by PFI-UDMSE (UniFi UDM Pro SE at 10.100.0.1, below).
|
||
# NH3-SW1 (Mikrotik CRS328-24P-4S+ at 10.100.250.2) retired from
|
||
# homepage 2026-04-22.
|
||
- PFI-UDMSE:
|
||
href: https://10.100.0.1
|
||
icon: si-ubiquiti
|
||
siteMonitor: https://10.100.0.1
|
||
description: UniFi Dream Machine Pro SE — gateway + controller (NH3 edge)
|
||
- NH3-NAS:
|
||
href: https://10.100.50.50:5001
|
||
icon: mdi-nas
|
||
siteMonitor: https://10.100.50.50:5001
|
||
description: Synology RS2418+ DSM (restic target + VM storage)
|
||
- NH3-PVE:
|
||
href: https://10.100.250.60:8006/
|
||
siteMonitor: https://10.100.250.60:8006/
|
||
icon: si-proxmox
|
||
description: Proxmox hypervisor (nh3-pve)
|
||
- NH3-VM-Docker:
|
||
href: http://10.100.50.40:5001
|
||
icon: si-docker
|
||
siteMonitor: http://10.100.50.40:5001
|
||
description: Docker VM (nh3-docker, Dockge at :5001)
|
||
- NH3-ExtDev:
|
||
ping: 10.100.50.42
|
||
icon: mdi-laptop
|
||
description: Manager / external-dev box (nh3-extdev, Debian 13) — successor to the retired nh3-ansible
|
||
- PBS-NH3:
|
||
href: https://10.100.50.90:8007/
|
||
icon: mdi-backup-restore
|
||
siteMonitor: https://10.100.50.90:8007/
|
||
description: Proxmox Backup Server — DR mirror (pulls from PBS-ANA)
|
||
|
||
- Infra - IRV:
|
||
# Irvine site — reachable only via WireGuard tunnel from NH3.
|
||
# The 10.100.79.0/24 subnet is the WG tunnel IP space; these cards
|
||
# only light up when the WG link is healthy.
|
||
- IRV-ML1:
|
||
ping: 10.100.79.3
|
||
icon: mdi-brain
|
||
description: GPU host (bare-metal, RTX 3090 + RTX A6000, native AI stacks)
|
||
- IRV-ML1-Dockge:
|
||
href: http://10.100.79.3:5001
|
||
icon: si-docker
|
||
siteMonitor: http://10.100.79.3:5001
|
||
description: Docker management (irv-ml1)
|
||
|
||
- Infra - ESH:
|
||
- ESH-UDMPM:
|
||
href: https://10.0.0.1
|
||
icon: si-ubiquiti
|
||
siteMonitor: https://10.0.0.1
|
||
description: UniFi Dream Machine Pro Max — gateway + controller (ESH)
|
||
- ESH-Firewall:
|
||
href: https://10.0.250.1
|
||
icon: mdi-wall-fire
|
||
siteMonitor: https://10.0.250.1
|
||
description: esh-gw
|
||
- Brother Printer:
|
||
href: http://10.0.90.125/
|
||
icon: mdi-printer
|
||
siteMonitor: http://10.0.90.125/
|
||
description: Brother (ESH)
|
||
- ESH-NAS:
|
||
href: https://10.0.50.50:9090
|
||
icon: mdi-nas
|
||
siteMonitor: https://10.0.50.50:9090
|
||
description: NAS share manager (Cockpit)
|
||
- ESH-PVE:
|
||
href: https://10.0.250.35:8006
|
||
siteMonitor: https://10.0.250.35:8006
|
||
icon: si-proxmox
|
||
description: Proxmox hypervisor (esh-pve)
|
||
- ESH-PVE-NAS:
|
||
href: https://10.0.50.55:8006
|
||
siteMonitor: https://10.0.50.55:8006
|
||
icon: si-proxmox
|
||
description: Proxmox hypervisor (esh-pve-nas, storage/media)
|
||
- ESH-FileBot:
|
||
ping: 10.0.50.70
|
||
icon: mdi-sync-circle
|
||
description: Restic / file-sync VM (esh-nas-pve) — role TBC
|
||
- ESH-VM-Docker:
|
||
href: http://10.0.50.45:5001
|
||
icon: si-docker
|
||
siteMonitor: http://10.0.50.45:5001
|
||
description: Docker VM (esh-docker-vm, Dockge at :5001)
|
||
|
||
# Service Networking group is now fully Docker-auto-discovered (Traefik ×2,
|
||
# AdGuard ×2, Dockge ×5, rest-server-ana, mailrise, etc. all carry
|
||
# homepage.group=Service Networking on their compose files). Position and
|
||
# layout live in settings.yaml. Do not add entries here or they'll double up.
|
||
#
|
||
# Mosquitto (ESH) note: still labeled Apps on its compose; once moved to
|
||
# Service Networking via a label change on esh-docker-vm, it auto-populates.
|