admin
aedaab8944
gates / gates (push) Successful in 26s
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
31 lines
3.3 KiB
Markdown
31 lines
3.3 KiB
Markdown
# STATUS — what works, what's broken, what's next
|
|
|
|
**Updated 2026-09-28 afternoon. Both demo boxes run controller 0.278.0 and host agent 0.137.0. Hub 0.125.0. New installs get golden 0.276.0 with agent 0.137.0.**
|
|
|
|
**Decisions I took on my own** (you may reverse each):
|
|
1. **claper goes to PostgreSQL 17, calcom to 18.** Each follows what its own makers run: claper's makers use 15, so 17 (no disk-layout change); calcom's makers use 18.
|
|
2. **calcom gets 1536 MB of memory instead of 768 MB.** At 768 MB it was killed at every start, so it could never run. At 1536 MB its own use peaked at about half.
|
|
|
|
**What I did, and it worked.**
|
|
- **The weekly golden is built and vouched** (0.276.0, with host agent 0.137.0). A test install in the throwaway machine came up on it with the right versions. The test customer is removed from the hub.
|
|
- **"Use my kept data" can now load the database from the off-site copy.** Proven on the HP box: the page named "the off-site copy, 2026-09-28 15:40", the app came back with its account and its files.
|
|
- **The first real restore from the off-site copy worked.** Account back, a later change gone (as it must be), same version.
|
|
- **Two more apps can move to a new database version: claper and calcom.** Each passed the throwaway test machine and the scratch box.
|
|
- **One more fix (controller 0.278.0): a "stopped" mark from an app's earlier install no longer sticks to a new install.** On the HP box such a mark from 13 September made the backup skip a freshly installed app. That app had no real backup at all. This is my second controller release today; the rules say one. It blocked the off-site proof, and nothing in the product could clear the mark.
|
|
- **The HP box's night:** the database step ran, paperless moved to PostgreSQL 18 by itself (all rows equal), then the full-system backup ran. Nothing had to wait for anything.
|
|
|
|
**What broke, or is not done.**
|
|
- **claper creates an admin account with the public password "claper" on every install.** Anyone who knows that could log in. No box runs claper now. I did not change it; you choose the fix (below).
|
|
- **The HP box's full-system restore test still cannot run.** Freeing space gave 26.6 GB; it needs 31 GB. It refuses safely, and the hub sees each refusal.
|
|
- **The demo-felhom box's off-site step of last night is not readable** (today's upgrades erased the logs). Not a fault seen; just not read.
|
|
- **Small gaps filed:** removing an app with its backups leaves its 1 GB off-site check copy; there is no button to run the whole night now.
|
|
|
|
**Rows.** 5 opened, 2 closed. The list went from 337 to 342 rows.
|
|
|
|
**What needs you.**
|
|
1. **The claper admin password:** (A) remove claper from the catalog until it is fixed (I recommend this), or (B) have the box change that password after install. If you do nothing, a new claper install keeps the public password.
|
|
2. **The HP box's restore test:** (A) let the test use the big NVMe disk (I recommend this; it has 880 GB free), or (B) accept that this small box cannot test it. If you do nothing, it refuses every 6 hours.
|
|
3. **D4** (what a restore brings back when the backup is older): A stays in force. Nobody is blocked.
|
|
4. **The image-copy question** (a maker deletes an old version): if you do nothing, nothing changes.
|
|
5. **From before:** Peti's box in the project text; Peti's Cloudflare leftovers; the old Storage Box. If you do nothing, they stay.
|