admin
f3d1ba3062
Viktor deleted 11 immich photos to test offsite restore; both place runs merged 0 files and flashed success. Two-layered root cause: - A UI delete means TRASH, not deletion — no file left the disk, so there was genuinely nothing missing to restore. The test proved nothing. - A valid test would also have failed: no offsite path loads a database. All three buttons are file-only (offbox_restore.go:171-232, :346-421). Files return; the library stays empty. The only DB replay is RestoreFromRecoveryUnit, reachable solely from the LOCAL restore panel. Compounding: the manual push never refreshes dumps (offbox_handlers.go: 203-227) — today's unit dump is from 02:30 and probes to asset:0 / user:0 / album:0, predating both the admin user and the photos. Had a full restore loaded it, it would have written an empty DB over the live one, destroying the trashed rows that were the only surviving recovery path. Answer to "can a customer trust same-day offsite?" for a DB-indexed app: no — files come back, content does not. No product code changed. Photos left in trash (recovery not wanted). Capability map: customer-restore row stays MISSING by finding, not by absence of attempt; offsite-restore row flagged scope-contested pending a ruling on whether CAMPAIGN-6D exercised the DB half. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01P9Nn14TWGzKoqAJAiVwC2s
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.