felhom.eu/STATUS.md

STATUS — what works, what's broken, what's next

Ready for the first real tester (Tester-2): yes. Tester 2 (a laptop) is off; nothing was sent to it.

Updated 2026-10-15 (evening). Agent 0.156.1 + its bundle on all three boxes; controller 0.313.0 is the floor (vouched golden 0.313.0) — demo-felhom and demo-hp run it, Tester 1 still runs the test build rc.4 (R-1053); hub 0.150.0 (0.151.0 and 0.152.0 — access tokens — written, not deployed). Open items: see documentation/backlog/OPEN-ITEMS.md. Older notes, day by day: documentation/backlog/STATUS-HISTORY.md. Reports: REPORT-night-2026-10-14.md, REPORT-immich-rollout-2026-10-14.md, REPORT-seo-felho-tarhely-2026-10-14.md, REPORT-immich-repair-2026-10-14.md, REPORT-power-cut-fixes-2026-10-14.md, REPORT-night-power-2026-10-13.md, REPORT-poweroff.md.

What works

• Every public name of the three test boxes answers only over https: plain http gets a 301 to the same https address, and browsers are told to remember it for one day (29 names checked, 2026-10-14 night).
• Media apps work together on one drive: a download reaches Sonarr/Radarr as one file, no copy; the download apps see only their own folder (live catalog, proven on demo-hp).
• A power cut in the middle of a backup no longer blocks later backups: the box removes the half-written backup at start-up (proven with a real cut on demo-hp, on all three boxes now).
• After a power cut, Immich repairs the photos the cut left broken, by itself, and the app page lists any lost photo (proven with a real cut on demo-hp: 41 of 41 repaired; on all three boxes now). An Immich update cannot switch it off quietly: the catalog refuses an untested Immich version.
• A household can switch the machine off; the hub holds alarms for 14 days and clears the state by itself (N100).
• A real power cut on demo-hp: it started by itself after all 8 cuts of the night (with the BIOS set), every app back in ~4 min; stale and recovered mails true and paired.
• A page for people searching „felhő tárhely" is live (/sajat-felho-tarhely, /en/own-cloud-storage): what cloud storage is, what to do when Google or iCloud fills up, a five-year cost table with prices read 2026-10-14, and who should NOT buy this.
• The machine estimator is public (/gepigeny, /en/sizing), with figures from two machines (N100 and HP t740; raised only, 2026-10-14).
• 64 apps in the catalog, the Usenet and torrent clients included (the website lists 62 of them — R-1036). OS updates, the kernel lane too, run at night.
• The hub is closed again after the 2026-10-12 security review; one box cannot read another's data.

What is broken

• Several root-level weaknesses wait on your four decisions below (R-954, R-971, R-982, R-985).
• DooPlex: a failed disk with its alarms silenced (R-934); CI jobs still get lost (R-887); something sets the shared checkout to „bare" (R-935); a Longhorn volume at 91 %.
• Tester 2 has never made an off-site check (R-862). The scratch box cannot read the drill catalog (R-992).

What we work on

• The power-cut findings still open (R-1004, R-1005, R-1010, R-1012, R-1013).
• Media apps on every drive (R-1023): live with the 0.313.0 floor — every drive in every media app, a new drive made ready by the box, a pulled drive loses nothing, a safe removal lets go first and the drive comes back by itself.

Waiting on you — decide

#	Row	Question	Pick	The other option costs	If you do nothing	Blocked
D1	R-954	Change every box's break-glass root password, since we cannot see if the old key was used?	Yes — about one hour, one box at a time, through the vault	Accept: no work, a password that may have been read stays valid	the old root passwords stay; if they were read, they still open the boxes from the LAN or console	—
D2	R-971	Should the box refuse a catalog change that asks for dangerous container rights?	Yes — an allow-list on the box (one controller release)	Keep trusting the catalog repo: whoever can push to it reaches every box	a catalog push keeps reaching every box's apps with no check	—
D3	R-985	„Zero-knowledge": change the wording, or remove the operator's root reach to the key?	Change the wording now; revisit after the first sale	Remove the reach: a design change to break-glass	the promise stays stronger than the product	the website text
D4	R-982	Root SSH with a password from the LAN?	No — key only; the password stays for the console	Keep it: anyone on the household network can try it	the host keeps accepting root password logins from the LAN	—
D5	R-993 (R-991)	Approve the minimum machine (audits/sizing-2026-10-13/SIZING.md §5: x86-64, 4 cores, 8 GB, 256 GB SSD)?	Approve	Change it: one edit	no hardware page; a buyer with a Raspberry Pi can still download the installer	the hardware page
D6	R-992	The scratch box cannot read the private drill catalog: give it a read-only login, or make that copy readable?	A read-only login	Readable copy: the drill catalog becomes public	every new-app test needs hand-staging	new-app tests
D7	R-990, R-989	Rule yes / no / later on the forum ideas (audits/forum-research-2026-10-12/FELHOM.md §5) and the selfh.st ideas (audits/selfhst-survey-2026-10-12/FELHOM.md §6)	—	—	nothing changes; the research ages	—
D8	R-206	Install DooPlex's Docker settings from git (restarts Docker), and prune the build cache weekly: yes or no?	Yes, in a quiet window	—	a rebuild of DooPlex still has the settings in git	—

Waiting on you — do

• Hub 0.152.0 is ready: access tokens (your ruling, 11:38). It includes 0.151.0 (a mail when a drive comes back). A token lets a script use the hub without your password; you tick what it may do. Do, in order: (1) say „yes" and I deploy it; (2) Configuration → Access tokens → create „cc-releases" with Overview: read and Releases: floor: write, 90 days, and save it on DooPlex as ~/.felhom-hub/cc-token (chmod 600) — do not paste it to me; (3) after I report the token works, change the hub password. If you do nothing: I keep using your password, for the floor only.
• Decide (R-1055): a token with „Customers: write" can change a household's e-mail and resend its claim code to it. Keep that, or make „resend claim" password-only? My pick: password-only (one line). If you do nothing: it stays as you wrote it; nobody holds such a token now.
• Remove the test server „plex-k6” from your Plex account (plex.tv → Settings → Authorized Devices). The claim test passed and the server is gone from Tester 1. If not: a dead server stays listed in your Plex apps.
• System poster needs a refresh: every public name answers only over https (http → 301).
• Clear demo-hp's own floor (hub → Demo HP → floor: empty → Save floor). It still reads 0.311.0. If not: the next global raise passes demo-hp by.
• Leftovers moved out of the shared checkout to /mnt/5_hdd/felhom.eu/leftovers/2026-10-14/ (nothing deleted): the Facebook first-post/ folder is not in git — keep, commit or delete it. The rest is already in git. If not: it just stays there.
• The media tests on Tester 1 are finished — results in REPORT-night-2026-10-14.md. Say „tear it down" when you want Tester 1 back to normal (R-1022; now three test drives and a throwaway Plex).
• Ask Google to index the new page: Search Console → URL-ellenőrzés → https://felhom.eu/sajat-felho-tarhely → „Indexelés kérése". If not: the page may sit unseen, and the 11 November / 9 December checks (R-1035) read zero for a reason that is not the page.
• N100 BIOS: read „After Power Loss" (the HP's „Previous State" made it start after 8 of 8 cuts). HP BIOS: „Bypass F1 Prompt on Configuration Changes" → Enable.
• Pull the failed disk Z6A07P2G (R-934; the twin Z6A070XZ is /mnt/3_hdd). If not: its alarms return on 11 November.
• Hub master key into the password manager, then shred -u the key file (security review 2026-10-12, in the history).
• 12 reused homelab logins to rotate, and the repo-visibility decision (R-925, P1).
• Before the first paying customer: Tandoor permission (R-789); a lawyer for the licence list (R-802) and the terms (R-813); SparkyFitness (R-784 — its author replied on 2026-10-13); print the break-glass sheet (R-923).
• Smaller: pin the first Facebook post (R-917); Tester 2's bootstrap (R-862); look at the uncommitted deny-list edit in homelab-manifests/.claude/settings.json; the rest of „Your own tasks" (T6–T19) is in the history, 2026-10-10.