dtoro
610b096840
A record -> 192.168.8.175 (Caddy's LAN IP), created via Technitium's REST API (login -> createToken -> zones/records/add) in a single in-memory call. Neither the admin credential nor the resulting session/ API token was ever printed to output or written to disk, and the token wasn't persisted anywhere after the call completed — it existed only for the lifetime of that one process. Verified: dig @192.168.8.2 +short oikos.hubris.network -> 192.168.8.175. End-to-end confirmation that DNS + Caddy + the Authentik gate are all wired correctly: curl https://oikos.hubris.network/ now returns a 302 (the forward-auth redirect firing before the not-yet-deployed backend would even matter) instead of failing to resolve/connect. This closes out every part of the console rollout except the actual apps-side bootstrap (oikos/console/deploy/README.md "One-time setup"), which remains pending direct operator execution. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Homelab Wiki — hubris
Living documentation for the hubris Proxmox homelab. Every node, every cross-cutting system, and every meaningful incident is its own page; pages are linked so you can start anywhere and walk the graph.
Last refreshed against live state: 2026-07-06.
Quick navigation
- Proxmox hosts — hubris (primary) + strong (cluster member)
- VMs — ZimaOS, Home Assistant
- LXC containers — service fleet (17 containers)
- Cross-cutting infrastructure — DNS, ingress, mesh, storage, auth
- Investigations — incident timelines
- Operations — cheatsheet, enrollment, runbooks
- Glossary — term definitions
- Conventions — wiki style, changelog hygiene, same-session update rule
Map
Proxmox hosts
hubris— PVE node, GMKtec NucBox M6 Ultra,192.168.8.77— primary host, runs 8 LXCs + 2 VMsstrong— PVE node (cluster hostnamestrong),192.168.178.181— 2nd member ofHomelabcluster. Hosts 7 LXCs migrated from hubris (Phase 1+2, 2026-07-05)
VMs
- 100 —
zimaos— ZimaOS 1.6.1, NAS frontend (evaluation) - 108 —
haos-16.3— Home Assistant OS - See vms/index.md for the full table
LXC containers
See the full table with IPs, hosts, mounts, and status in
containers/index.md. Quick summary:
- hubris (10 active): 102 nfs-export, 103 paperless, 104 gitea, 105 apps, 114 nextcloud, 119 sophia, 120 mule-images, 121 caddy, 124 authentik (outpost), 128 trmnl, 132 rclone
- strong (7 active): 101 jellyfin, 118 elementsynapse, 122 arriman, 129 house, 130 grimmory, 133 seanime, 134 romm
- Destroyed (archaeology): 100 arr, 106 flaresolverr, 107 marimo, 109 syncthing, 110 photoprism, 111 karakeep, 112 immich, 115 reticulum, 123 claudio-bot, 125 seafile, 126 plato, 127 mule-photos-new — see containers/index.md
Cross-cutting infrastructure
- Infrastructure index — map of every cross-cutting system
- Glossary — term definitions
- DNS — split-horizon
- Ingress — Caddy + VPS traefik
- Mesh — Tailscale → Netbird migration
- Monitoring — Hermes health watchdog
- Media permissions —
mediaGID 10000 - SSH access
- Backups — rclone → Proton Drive (LXC 132); restic-on-USB deprecated
- Auto-deploy — gitea-webhook pipelines
- VPS hardening — IONOS / netbird control plane
- Homelab context distribution — cross-client
/opt/homelab-context+ MCP + secrets-issuance
Investigations
Time-stamped incident notes / experiments in investigations/index.md.
Resolved cases move to investigations/archive/.
Operations
- Command cheatsheet
- Agent enrollment — bootstrap a new client (workstation, LXC, VM) into the homelab context system
Conventions
- Each node page ends with a
## Changelogsection. Reverse-chronological. Entry format:### YYYY-MM-DD — short title one or two lines on what changed and why. - Cross-linking is mandatory. If a page references another node or system, link to it. Treat orphans as a bug.
- Live state wins. When something here disagrees with
pct config/docker inspect/ running config, fix the wiki and note the change in the relevant changelog. - Tracked configs. A node whose config lives in a Gitea repo (Caddy, Gitea customizations, Artifacto, mule-image) is auto-deployed via webhook — see auto-deploy. Edits there must be pushed, not left local.
- No secrets. This is a private repo on
git.hubris.network, but still: paths to secret files are fine, secret values are not.
Maintaining this wiki
When you change a node:
- Update the relevant page (config snapshot, ports, mounts).
- Add a changelog entry at the bottom of that page.
- If the change touches a cross-cutting system (DNS, Caddy, Authentik, mesh), update that page too and link it from the changelog entry.
- If it's an incident, add an entry to
investigations/.
See also
CONTRIBUTING.md— page templates and tone