admin
a2ca6eb413
gates / gates (push) Failing after 6m36s
Search Console (3 months, read 2026-10-14): 48 impressions, 1 click, average position 73.6; the top query is „felhő tárhely" (19). No page on the site used the phrase — Google was showing the home page by accident. New pair /sajat-felho-tarhely + /en/own-cloud-storage: what cloud storage is and the three ways to have one; what to do when the Google or iCloud storage is full (the free clean-up first, linked to Google's and Apple's own help; the paid options second); a five-year cost table; where the data sits; who should NOT choose this; the closed test. Registered in site_gates.py TWINS/URL/SHELL, both URLs in sitemap.xml (22 -> 24). FAQPage JSON-LD derived from the visible text. Prices each read 2026-10-14 on the provider's own Hungarian page, with the URLs and the date in an HTML comment and a visible „Árak" line: Google AI Plus (2 TB) — Google One's 2 TB plan — 35 990 Ft/év (behind the „Éves" toggle; a plain fetch sees only the monthly 3 590 Ft), iCloud+ 2 TB 4 490 Ft/hó, Microsoft 365 Családi (2 TB shared, no longer 1 TB per person) 46 499 Ft/év. Felhom's own cost follows what the site already said (operator ruling): machine and install one-off, power, off-site storage monthly by volume, operation OPTIONAL, no fee during the closed test. Power is stated as an idle measurement (nyugalmi állapotban 7-9 W, ~75 kWh/év, from audits/night-power-2026-10-13) and the page says a year with daytime use is more; no daytime figure and no electricity tariff are given, because neither is measured or sourced. FAQ corrected (both languages, JSON-LD re-derived): the cost answer carried unsourced, undated prices and summed Spotify and a password manager into a storage comparison; and the page contradicted itself on electricity („havi néhány ezer forint" vs „évi 5.000–15.000 Ft"). App count 60 -> 62 in the four places that were stale. Three defects found on the rendered page and fixed: a .vs-row link fell back to the browser-default blue (contrast 1.99 -> 7.17); 24px of horizontal scroll at 390px because .method-pros li is a nowrap flex row and the new items contain links (each item's content wrapped in one span); .info-card and .method-pros were scoped to the pages that first used them. site.css ?v=31 on all 26 pages. The shared .content-section padding was NOT changed — it is identical on every page; the new page only lacked the alt-bg alternation, and now has it. R-1033 the apps page lags the catalog by two apps (plant-it, wger); R-1034 gate 17 checks the FAQ JSON-LD on two hard-coded pages only; R-1035 the SEO result, with dated checks on 2026-11-11 and 2026-12-09.
53 lines
7.1 KiB
Markdown
53 lines
7.1 KiB
Markdown
# 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-14 (evening).** Agent 0.156.1 + its bundle on all three boxes; controller 0.311.0 on demo-hp (its own floor), 0.310.0 on the other two; hub 0.150.0; golden 0.310.0. Open items: see `documentation/backlog/OPEN-ITEMS.md`. Older notes, day by day:
|
||
`documentation/backlog/STATUS-HISTORY.md`. Reports: `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
|
||
- 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 demo-hp only until the floor moves).
|
||
- 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-1033). 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); the hub build must refuse a stale checkout (R-1021).
|
||
- Media apps on every drive (R-1023): the layout is proven on Tester 1 — a download reaches the library as one file, no copy. The live templates get fixed next (R-1014).
|
||
|
||
## 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 | — |
|
||
| D9 | R-1023 | Media apps: bind the whole `media` folder (download apps can then write into Photos and Music), or move films and shows to their own folder first? | **Own folder** (`15-media-library.md` §2) | Whole `media`: no move, but the internet-facing apps reach the family photos | the build waits for this answer | the build |
|
||
|
||
## Waiting on you — do
|
||
- **Controller 0.311.0 to the N100 and Tester 1:** bake golden 0.311.0 (CC, ~30 min), vouch it, then the global floor 0.311.0 (MinAgent 0.155.0) and clear demo-hp's own floor. If not: only demo-hp repairs Immich after a power cut; demo-hp's own floor stays above the golden.
|
||
- **The shared `git/felhom.eu` checkout** is behind and its pull fails on untracked leftovers (R-1021): say whose they are, or let CC move them aside. If not: the hub build script builds stale code.
|
||
- **The media test on Tester 1** (about one hour): `documentation/audits/media-all-drives-2026-10-14/TEST-SHEET.md`, then write „done". Then the teardown word when you want (R-1022).
|
||
- **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.
|