REPORT + STATUS: P1 fixes — supervisor proven incl. crash-loop resume and hub events; publish; rows
gates / gates (push) Successful in 18s
gates / gates (push) Successful in 18s
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
This commit is contained in:
@@ -1,5 +1,42 @@
|
||||
# STATUS — what works, what's broken, what's next
|
||||
|
||||
**Updated 2026-09-15 (P1 fixes) — the big night's blockers, fixed and shipped.**
|
||||
|
||||
> **Ready for a volunteer: almost.** The file manager has a real password, the backup page tells the truth, the
|
||||
> installer is published with its download page, and a dead controller now comes back by itself — proven on the HP.
|
||||
> Two things still stand in the way: a volunteer's own tunnel is unproven until their box exists, and every box except
|
||||
> the HP still runs the old agent until you sign its update.
|
||||
|
||||
**Decisions I took.** None under the unattended rule. Three things I did not do, each with its reason: I did not send a
|
||||
real connect e-mail to test it, because deleting a test customer would touch the off-site server; I did not build a
|
||||
„release PBS token" button, because the off-site server has no way to remove only the token; the memory warning does not
|
||||
say „restarted", because nothing restarts the app.
|
||||
|
||||
**What I exercised, on the HP.** Killed the controller: back in 59 seconds. Parked it: it stayed off. Killed it during an
|
||||
update: the update rolled itself back. After three kills in 13 minutes the box stopped retrying for 30 minutes and you were
|
||||
e-mailed — that is the safety brake, and it worked. When the brake ended, it started the controller again by itself, and told you that too.
|
||||
File manager: a new box gets its own password; the HP, where you set one, was left alone. Backup page: correct on the HP.
|
||||
Vaultwarden refuses strangers. Paperless took 20 documents at once without losing one.
|
||||
|
||||
**What broke, and whether I fixed it.** The backup tile printed „0 B" after an agent restart — fixed, ships next release.
|
||||
The memory-warning check sees nothing inside our guests, because Docker reports nothing there — not fixed, filed.
|
||||
|
||||
**Rows.** Closed 9, opened 9. Register: 232 before, 232 after.
|
||||
|
||||
**Needs you.**
|
||||
1. **Sign the agent update for the N100 (and later Peti's box).** If you do nothing: the N100 keeps the old agent, its
|
||||
dead controller does not restart, and its controller update stays held.
|
||||
2. **Say where your signing keys live between sessions.** They were readable by other users on DooPlex; I tightened them.
|
||||
If you do nothing: the keys stay on the build server.
|
||||
3. **When the next box for „Tester 1" exists, check the tunnel opens from outside.** If you do nothing: the „No TLS Verify"
|
||||
fix stays unproven.
|
||||
4. **Allow one test customer to be deleted (it resets on the off-site server), or accept the unit test.** If you do
|
||||
nothing: the automatic connect e-mail is untested with a real mailbox.
|
||||
|
||||
---
|
||||
|
||||
## Previous note
|
||||
|
||||
**Updated 2026-09-15 (morning note) — the big night: a household's first month on one fresh box.**
|
||||
|
||||
> **Ready for a volunteer: not yet — three things stop them.** The dashboard link still does not open through
|
||||
|
||||
Reference in New Issue
Block a user