Files
felhom.eu/STATUS.md
T

8.0 KiB
Raw Blame History

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

Ready for Tester 2? Yes — tell the friend go (hand-over list: documentation/pilot/TESTER2-handover.md).

Updated 2026-10-23 (morning). Your three picks are built (the tunnel repairs itself with a new key, the hub skips a keyless deleted install, the controller repository stays public), and the night copy can no longer outlive the controller. Four fresh reviews found 34 points, every real one fixed or a row; the test night is running and its verdict lands here at 07:00. Nothing was released or deployed; the morning list has the order, and the DooPlex survey asks four questions (D32–D35).

What works

  • A box installs from nothing with the public installer, links to the hub, and moves to the floor by itself (map A1, A3, A4).
  • 65 catalog apps install, update one tested step at a time, and a failed update undoes itself (map B1, B3, B4, B6).
  • Backups: database dumps, a second-drive copy, an off-site copy and whole-box copies; restore tests run by themselves (map C1–C4, A17, A18).
  • A restore brings an app back with its data and its database password; a failed or cut restore puts the app back as it was — off-site live, local on the test image (map C5, D6, D16).
  • After a power cut the box starts by itself, cleans up a half-written backup, and Immich repairs broken photos (map C10, F12).
  • A second drive is offered as the backup target; media apps see every drive; a one-disk box gets its own data area (map D1, D13, D15).
  • The three test boxes answer only over https; the hub's key opens nothing on a box; password guesses are counted (map E12, E13, E17).
  • The hub mails alarms and recoveries, and keeps one whole-box copy per week on ep0; CC uses its own limited token, not your password (map F1, F11, G15).

What is broken

  • P1: about 12 homelab logins still use a password that was public, and the public Gitea repo is not decided (R-925, yours).
  • Tester 2 is off since 2026-10-04: old emergency password, no off-site check, no bootstrap (R-1139, R-1104, R-862).
  • DooPlex: the failed disk is still in the box, its alarms silenced (R-934); something sets the shared checkout to „bare" (R-935).
  • The scratch box cannot use agent features (R-1083).

What we work on

  • Dated checks, run by CC. 2026-10-23: no app stop when the host is busy (R-1173). 2026-10-26: each hub daily job ran once on the clock-change day (R-1183). 2026-10-27: the weekly clean-up window (R-435; the logs of the last one were lost to restarts).

Waiting on you — decide

Newest first. CC's pick is in the „Pick" column. Each row also has its full text in the register.

# Row Question Pick (why) The other option costs If you do nothing Blocked
D36 R-1225, R-1226 Two website sentences before the publish: „8 GB runs the basics; the photo app needs 16 GB” and „what you open from outside the home passes Cloudflare's network, readable there; the backups leave only encrypted”? Yes, both (the patch's own aim is the whole truth) — the patch publishes with both promises a little too strong —
D35 R-1228 After the release week, serve the website and the installer from Cloudflare, like the ISO? Yes, later (no new installs stop when DooPlex is down) keep them home: after a DooPlex loss, no install until it is back the same —
D34 R-232 Copy the hub database to ep0 every 6 hours instead of every night? Yes (0 €, about 30 minutes, one DooPlex change) keep nightly: up to a day of hub changes lost, e.g. a new box's recovery package the same —
D33 R-1227 Copy the released images and agent packages to ep0 every night? Yes (0 €, about 2 hours of CC, a few GB on ep0) a timed rebuild drill instead: about 3 hours once, and rebuilt images are not the same after a DooPlex loss no box updates, reinstalls or installs until everything is rebuilt —
D32 R-923, R-924 Print the break-glass sheet now (eight keys and logins + ep0's fingerprint) and keep it outside the home? Yes (30 minutes; nothing else opens the off-site copies after a loss) an encrypted USB stick outside the home: ~10 €, 1 hour, one more passphrase after a DooPlex loss no off-site copy opens —
D9 R-1062 Split the N100's USB drive in two, for multi-drive tests? No — keep one drive (the lived-in box keeps its nightly whole-box backup) Split: the box loses its local whole-box backup, or you buy a second drive first it stays one drive; multi-drive tests stay on Tester 1 —
D7 R-990, R-989 Rule on the forum ideas and the selfh.st ideas now, or park them? Park them (P4; nothing waits on them) Rule now: about one hour of reading nothing changes; the research gets old —

Waiting on you — do

Still needed? (yes/no) — CC could not check these. Answer yes or no per line.

  1. Look at roms/roms/ on the N100's drive in the file manager (R-1099). Since 2026-10-16.
  2. The N100 sheet, about 30 minutes: Plex, the admins in Prowlarr, Sonarr and Radarr, your download sources (documentation/audits/n100-lived-in-2026-10-15/SHEET.md). Since 2026-10-15.
  3. Look at these pages on demo-hp when you have time: Calibre-Web („Adatok és mentés"), the file manager, AdventureLog, Plex, the app page, the Plex and Sonarr guides („Útmutató"). Since 2026-10-16.
  4. Remove the test server „plex-k6" from your Plex account (plex.tv → Settings → Authorized Devices). Since 2026-10-15.
  5. Ask Google to index https://felhom.eu/sajat-felho-tarhely in Search Console (R-1035). Since 2026-10-14.
  6. BIOS: on the N100, read „After Power Loss"; on the HP, set „Bypass F1 Prompt on Configuration Changes" to Enable. Since 2026-10-14.
  7. Pin the first Facebook post (R-917), and look at the new cover in the Facebook phone app (R-919). Since 2026-10-12.

Morning, 2026-10-23 — in this order.

  1. Hold or go: The test night is running; its verdict lands here at 07:00. One question from the review: D31 as built also covers an install that got the whole-box password but no recovery package — its password is rotated without your press (R-1205). CC: go. If not: revert one hub commit before item 4.
  2. Release controller 0.340.0 (main after tonight; tested as rc.8 on the scratch box, rc.6 on the test box): the safe night copy, the catch-up fix, R-49, R-1187, R-1189, R-1214. If not: these wait.
  3. Release the agent (the tunnel repair, its tunnel field, the root-SSH bundle) and the installer tag with the root-SSH removal (R-1204, R-982); then vouch. If not: a clock-ahead box stays cut off; root keeps its password on the LAN.
  4. Build and deploy hub 0.167.0 (D31, the tunnel alarm and its clearing). If not: a dead tunnel stays silent.
  5. Publish the website patch (D3, D5), with D36's two sentences if yes. If not: the old wording stays.
  6. On the hub's Hosts page: Discard appliance 49, and delete host Tester4-16fdef (tonight's test box). If not: two dead entries alarm.
  7. The DooPlex hour: D32–D35 in the table. If not: a DooPlex loss stays as the survey describes. The rest
  • Pull the failed disk Z6A07P2G out of DooPlex (R-934). If not: its alarms return on 11 November. Since 2026-10-12.
  • Rotate the reused homelab logins and decide the Gitea repo's visibility (R-925, P1). Since 2026-10-09.
  • Two leftovers on DooPlex: the Facebook first-post/ folder in leftovers/2026-10-14/ (keep, commit or delete); the deny-list edit in homelab-manifests' .claude/settings.json (commit or drop). If not: they stay. Since 2026-10-14.
  • Before the first paying customer: Tandoor's permission (R-789); a lawyer for the licence list and the terms (R-802, R-813); SparkyFitness by e-mail (R-784); print the break-glass sheet and the signing keys (R-923, R-924).
  • Later (yours, not urgent): R-1229 (ArgoCD's sync settings into git), R-862 (Tester 2's bootstrap, when it is back), R-504, R-1071, R-1073, R-1077, R-1042, R-132, R-908, R-779, R-904, R-232, R-433, R-933, R-213, R-832, R-388, R-882, R-883, R-814, R-1056, R-1164, R-930, R-920, R-902.