From dd8c7fd7bda0296a3c56e05abb95412041ee71f3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Andr=C3=A9=20Padez?= Date: Sat, 29 Aug 2026 14:30:07 +0100 Subject: [PATCH] deploy 2026.08.29.04: 7 of 7 hosts, officer-dev skipped as the host it ran on Co-Authored-By: Claude Opus 5 (1M context) --- deploy/2026.08.29.04.report.md | 76 ++++++++++++++++++++++++++++++++++ 1 file changed, 76 insertions(+) create mode 100644 deploy/2026.08.29.04.report.md diff --git a/deploy/2026.08.29.04.report.md b/deploy/2026.08.29.04.report.md new file mode 100644 index 00000000..6b8948d0 --- /dev/null +++ b/deploy/2026.08.29.04.report.md @@ -0,0 +1,76 @@ +# 2026.08.29.04 — deploy report + +**7 of 7 targets succeeded. `officer-dev` skipped by design — it is the host the rollout ran on.** + +Every host went `03fbb118` → `e9b71522` except `fofos`, which started further back at `2738f799` and +travelled further. All eight rows below end on `e9b71522`, the commit `deploy/2026.08.29.04` points at. + +Nothing failed. Nothing was left half-applied. No host was unreachable — `macbookpro` was awake. + +## What ran, per host + +The same four steps everywhere: tracked-only dirty check, `git fetch origin --tags`, +`git merge --ff-only deploy/2026.08.29.04`, `bun run plugins:update`, then `pm2 restart officer` and +nothing else. The plan asked for no `bun install` and no `bun db:push`, and neither was run. + +| Host | HEAD before | HEAD after | plugins | `officer` restarts | health | `ls` | +| --- | --- | --- | --- | --- | --- | --- | +| `officer-dev` | — | — | **SKIPPED — the rollout ran here** | — | — | — | +| `alpha` | `03fbb118` | `e9b71522` | 15/15 | 5 → 6 | 401 | 200, 77 entries | +| `fofos` | `2738f799` | `e9b71522` | 5/5 | 93 → 94 | 401 | 200, 39 entries | +| `macbookpro` | `03fbb118` | `e9b71522` | none installed | 5 → 6 | 401 (9010) | 200, 62 entries | +| `macbruno` | `03fbb118` | `e9b71522` | 1/1 | 8 → 9 | 401 | 200, 41 entries | +| `production-pertento-bridge` | `03fbb118` | `e9b71522` | 1/1 | 6 → 7 | 401 (9010) | 200, 53 entries | +| `edge-pertento-bridge` | `03fbb118` | `e9b71522` | 2/2 | 7 → 8 | 401 | 200, 29 entries | +| `deadpool-rezio-bridge` | `03fbb118` | `e9b71522` | 2/2 | 24 → 25 | 401 | 200, 49 entries | + +`plugins:update` exited 0 on every host that has plugins. `401` on `/api/health` is healthy — the plan +says so and every host gave the same answer. + +## The file browser check + +This release rewrote the file browser and the viewer, so the plan asked for one signed +`/api/file-browser/ls` call per host. **Seven hosts, seven `200`s**, each with a plausible entry count +for that machine. The counts differ because the homes differ; none was zero and none was a 500. + +Signed as user id 1 with that host's own owner, which is not the same address everywhere — +`conceiba@gmail.com` on `macbruno` and `brunorezio@gmail.com` on `deadpool-rezio-bridge`. Read from each +host's own `users` table rather than assumed. + +## Schema + +**No schema verification was performed, because this release changes no schema.** The plan states that +and shows the two `git diff --name-only` commands behind the claim. No `bun db:push` step exists in it +and none was improvised. + +The plugin sidecars did apply their own schemas during `plugins:update` — `music` on `alpha`, +`fofos-admin` and `proxy-manager` on `fofos`, `proxy-manager` on `macbruno`, `offscale` on +`edge-pertento-bridge`, `email` on `deadpool-rezio-bridge`. Each printed its own +`schema: applied … (N table(s) verified)`. That belongs to the plugin updater, not to this release. + +## More restarted than `officer` + +`plugins:update` restarts a sidecar whenever it moves a plugin, before the plan's own restart. Naming +only `officer` would understate what moved, so: `officer-music` on `alpha`, `officer-av-club` on +`fofos`, `officer-gitea` on `production-pertento-bridge`, `officer-gitea` and `officer-offscale` on +`edge-pertento-bridge`, `officer-email` on `deadpool-rezio-bridge`. Every one came back `online`. + +`ecosystem.config.cjs` was never restarted anywhere. No vault was touched. + +## What I did not do + +- **`officer-dev` — skipped entirely.** Not pulled, nothing restarted. It already sits on this code, and + restarting it would have ended the session writing this report. The owner restarts it deliberately, + last, once happy with the rest. +- **`fofos` has an untracked `scripts/chk.ts`.** Untracked is not dirty; the fast-forward could not touch + it and it was left exactly where it was. A note, not a skip. +- **`production-pertento-bridge` prints an nvm warning** on every interactive shell — its `~/.npmrc` has a + `globalconfig`/`prefix` setting nvm objects to. It is noise, it broke nothing, and it is not this + release's doing. Worth clearing at some point so it stops appearing in deploy output. +- **No `--force` anywhere**, no dependency install, no database write. + +## One thing worth knowing + +The plan flags a **platform event bus** — `files:uploaded`, `files:placed`, `archive:extracted` — that no +plugin subscribes to yet. The dispatch path therefore ships unexercised. If something odd shows up near an +upload on any of these hosts, that is the first place to look.