admin
1f4702fe50
Golden 0.146.0 baked on the drill VM and published to gitea: felhom-golden/0.146.0/golden.tar.zst sha256 4834c703162c5437467a329144b1a523019bf5693ab9d439558be7323587e955 612696588 B (584 MB archive), controller 0.146.0 confirmed baked in All pass markers green: Result=success/ExecMainStatus=0, 0 FATAL/exclusions, docker OK (overlay2), ALL THREE mounts included (rootfs + mp0 /var/lib/docker + mp1 /mnt/sys_drive), pre-delete HTTP 404 (the pre-gate — version did not exist), upload HTTP 201. Integrity verified independently of the build host: anonymous GET | sha256sum matches byte-for-byte, ranged GET 206, content-length matches the bake's bytes. The version now appears in the hub dropdown (0.136.0, 0.143.0, 0.146.0). Teardown per GL-1: log copied out as evidence first (180:/mnt/5_hdd/felhom.eu/drill/bake-0.146.0.log), guest 9100 purged, token + script + log shredded in-VM, VM off, qemu confirmed gone via `ps -eo comm` (not the self-matching pgrep -f), drill disk reverted to the virgin snapshot exactly as found. Token-leak grep = 0 against the LITERAL token value, on the bake log and both ISO build logs from this session. REMAINING is operator-only and password-gated: Day-0 manifest Golden -> 0.146.0 (Agent stays 0.90.0, MinAgent stays 0.90.0 — v0.146.0 declares no new agent coupling), then the floor -> v0.146.0 saved LAST. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Nn3VgQk9iwEGgyx6QJ2NvE
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.
architecture/01-topology-and-trust.md— topology & trust modelarchitecture/03-host-agent.md— the host agent (Go; v0.29.1)architecture/04-control-plane-authorization.md— signing, escrow, authzarchitecture/02-controller-module-map.md— historical v0.33 planning map; the live map iscontroller/module-map.mdproxmox-platform.md— Proxmox platform reference
Hub (operator backend) — architecture/05
architecture/05-hub-architecture.md— hub architecture (v0.11.0)
Security audits & remediation — audits/
audits/deep-sweep-2026-06-13.md— cross-repo deep audit (controller + agent) with remediation statusaudits/bughunt-reconcile-2026-06-13.md— reconciliation of the v0.30.3 BUGHUNT against current code + merged fix list
Spike & test findings — tests/
Per-slice spike/validation findings (phases 0–5, slices 7–10). 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.