Files
felhom.eu/documentation
admin f39b51782a R-244: measure the teardown residue rather than estimate it — still owed
Read-only census, no truncation. app_log_issues holds 1309 rows; 71 reference
a torn-down venue (finalwalk, c11, rewalk, part4). Of those 44 are ORPHANS,
naming only torn-down customers and safely deletable, and 27 are SHARED with a
live customer and must be de-referenced, never deleted. 1238 untouched.

The 27 are exactly why the leg was never written, and why a DELETE ... WHERE
customer LIKE would destroy a live customer's issue history.

NOT fixed here, and the reason is stated on the row rather than left implied:
the fix is hub code, this session's scope forbade a hub version bump, and a
hand-run SQL mutation over 71 rows - 27 needing surgical de-referencing - with
no tested code path and no red-proof is the shape that goes wrong on a live
database. The next session now starts from data instead of a guess.
2026-08-07 13:01:09 +02:00
..

Felhom — Documentation

Felhom is a managed home-server service for Hungarian households, built on a three-component model over Proxmox:

  • Hub — operator backend on k3s (hub.felhom.eu). Repo: felhom.eu/hub/.
  • Host agent — one per Proxmox host; operator-tier; owns all Proxmox interaction. Repo: felhom-agent/.
  • In-guest controller — one per customer LXC; Docker-only; manages the customer's apps. Repo: felhom-controller/.

This directory is the central, code-verified documentation home for all three components plus the platform and the security-audit record.

Sections

Controller (in-guest) — controller/

The Docker-only app-domain controller. Full per-area docs grounded in current source (v0.59.0). → controller/README.md: module map, deploy & stack lifecycle, backup architecture, storage/monitoring/metrics, auth/hub/sync/integrations.

Host agent & platform — architecture/, proxmox-platform.md

The operator-tier agent and the Proxmox platform.

Hub (operator backend) — architecture/05

Security audits & remediation — audits/

Spike & test findings — tests/

Per-slice spike/validation findings (phases 05, slices 710). See tests/.

Conventions

  • Code-verified, not memory-derived. Architectural claims here are checked against the actual current source; if a claim can't be verified it is omitted and flagged, not guessed.
  • Per-repo operational working files (CLAUDE.md, CONTEXT.md, CHANGELOG.md, BUGHUNT.md, REPORT.md, TASK.md) live in their own repos — they are operational, not published docs.
  • Authoritative versions at last refresh: controller v0.59.0, agent v0.29.1, hub v0.11.0.