admin
6b2176e480
gates / gates (push) Successful in 27s
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
33 lines
4.1 KiB
Markdown
33 lines
4.1 KiB
Markdown
# STATUS — what works, what's broken, what's next
|
|
|
|
**Updated 2026-09-25 (morning). Both demo boxes run controller 0.271.0 and host agent 0.134.0. Automatic app updates are built and ran on their own last night. The HP box can back up again.**
|
|
|
|
**Decisions I took on my own (you may reverse them).**
|
|
- **The box takes one tested step per app per night.** Your brief said "one tested step per app". An app three steps behind now needs three nights.
|
|
- **After the 5-hour mark, the full-system backup waits only for an update step that is already running, and never more than 30 minutes.** Starting the backup in the middle of a step would stop the app while it is being checked and undo a good update.
|
|
- **The controller does not update itself while the night's app updates run.** A controller restart in the middle would stop the rest of that night's updates.
|
|
|
|
**What I did, and it worked.**
|
|
- **The fixed host agent reached both demo boxes.** I signed it for each box. The restore test is on again. On the N100 box it passed (85 seconds). On the HP box it said "not enough space" and created nothing, which is correct.
|
|
- **The HP box backs up again (your option A).** It now keeps one old whole-box backup instead of three. I removed the two oldest. A backup started with the backup page's own button fitted: 8 GB, and the disk is now 60 % full.
|
|
- **Automatic updates are built.** Each night, after the off-site copy, the box updates its apps by itself: one app at a time, one tested step each, the previous version ready to put back. There is a switch on the settings page, in both languages, on by default. A successful update sends no mail; the app page shows a line.
|
|
- **Proven on the scratch box first, over six simulated nights.** A failing update was put back and not tried again until the catalog re-tested it. A step marked "needs a person" was never taken. A power cut during an update: the box finished it after the restart. The controller killed during an update: the update was cleanly put back. Switch off: nothing happened. The app data read back after every night.
|
|
- **The demo boxes' first real automatic night.** The N100 box updated opengist (1.13 → 1.15) by itself at 04:15, in 20 seconds. The HP box had nothing to update, and said so. Both reported to the hub.
|
|
- **A new host agent (0.134.0) skips a whole-box backup that cannot fit**, and says why, before it starts. It is on both demo boxes.
|
|
- **Two more apps moved in the catalog** (n8n, mealie), each tested twice before it moved.
|
|
|
|
**What broke, or is not done.**
|
|
- **My own test started a real whole-box backup on the HP box for 5 minutes.** I stopped it. Nothing was left behind, and the apps kept running. The cause was a bug in the new agent, and I fixed it before the release.
|
|
- **If the controller restarts in the night, the rest of that night's updates wait for the next night.** Your decision is below.
|
|
- **The backup-page sentence for "backup does not fit" is not built yet.** The agent half is done. The page half needs the next controller release.
|
|
- **Last night no whole-box backup was due on either box**, so the "backup waits for the updates" rule did not happen for real yet. The tests prove it.
|
|
|
|
**Rows.** 3 opened, 6 closed, 2 updated. The list went from 341 to 338.
|
|
|
|
**What needs you.**
|
|
1. **Peti's box: what should its automatic updates be before it comes back online?** It has been silent since 15 July, on a very old version. The switch is on by default. If it comes back and takes the new version, it updates its apps by itself from its first night.
|
|
- **A (my choice): hold Peti's box on its current version until someone looks at it after it returns.** Cost: it stays behind until then, and the hold must be removed later by hand.
|
|
- **B: leave it.** Cost: on its first night online it jumps many versions and updates its apps by itself, with nobody watching.
|
|
- **If you do nothing, B happens.**
|
|
2. **If the controller restarts in the night, should the box continue that night's updates?** (A) Yes: the box remembers the night and continues until the 5-hour mark. (B) No: it waits a day, as now. I would choose A. If you do nothing, B stays.
|