3 Commits

Include renames

Author	SHA1	Message	Date
archipelagoandClaude Opus 5	eb48eab946	feat(apps): find out when an app has fallen behind upstream ... Nodes offer an update when the signed catalog pins something newer than what's running, and that machinery is fine. The missing step was the one before it: nothing told *us* when upstream shipped. A pin could sit at fedimintd v0.10.0 for months while every node in the fleet correctly and confidently reported "up to date". The reason nothing could tell us is that a manifest records only our mirror — `source.archipelago-foundation.org/lfg2025/fedimintd:v0.10.0` says nothing about the project it was mirrored from. So this adds an optional `app.upstream` block naming the real source, and a script that asks each one what it has released. Running it answers the question that prompted this. Of 58 apps, 28 are behind, including LND v0.18.4-beta against v0.21.2-beta, Bitcoin Core 28.4 against 31.1, and fedimintd/gatewayd v0.10.0 against v0.10.1. Two choices worth stating. An app with no `upstream` block is reported as UNTRACKED rather than skipped — a silent skip is how this stayed invisible, and before this commit all 58 were silently skipped. And a suggestion prefers our own tag variant: telling someone pinned to `postgres:16.13-alpine` that the newest tag is `18.6-trixie` is true and useless, because swapping the base image is a different decision from bumping a version. Five apps are deliberately left untracked (barkd, immich-postgres, indeedhub-minio, lightning-stack, pine-whisper): I could not establish their upstream with confidence, and a wrong `repo` produces a confident wrong verdict, which is worse than an honest gap. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-17 08:04:33 -04:00
archipelagoandClaude Fable 5	76e6f06995	fix(phoenixd): dot-free datadir + data_uid; docs: iframe rules ... phoenixd: the orchestrator treats bind paths containing a dot as file mounts and never creates their source dir, so the image's default /phoenix/.phoenix target crash-looped the unit (statfs: no such file). Datadir moved to /data via PHOENIX_DATADIR; data_uid 1000:1000 matches the image's phoenix user — without it phoenixd dies on phoenix.conf 'Permission denied'. Both verified end-to-end on archi-dev-box: orch install OK, seed.dat + db on the host, authenticated /getinfo answers. alby-hub: launch flips to embedded — pairs with the gate change that neutralizes upstream frame blocking. Dev guide: iframe embedding rules (who blocks framing and why the gate may strip it; when open_in_new_tab is legitimate; test in the embedded session, never a tab). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-08-12 12:38:17 -04:00
archipelagoandClaude Fable 5	fdd26ba1e3	feat(apps): Alby Hub 1.23.0 + phoenixd 0.9.0 manifests with official icons ... Both images mirrored to the Foundation registry. Alby Hub: gated web UI on 8087, LDK data under /var/lib/archipelago/alby-hub. phoenixd: headless loopback API on 9740 (own password auth), seed dir preserved under /var/lib/archipelago/phoenixd. Not yet in the signed catalog — disk manifests only, pending install verification on archi-dev-box. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-08-12 11:55:17 -04:00