5 Commits

Include renames

Author	SHA1	Message	Date
archipelago	f133d5555a	feat(apps): surface Portainer's first-run setup token in the credentials interstitial ... Portainer >=2.21 no longer lets whoever loads the page first claim the admin account: on a fresh install it mints a one-time setup token and prints it ONLY to the server logs. On an appliance that is a dead end — 'check the Portainer server logs' is exactly what a user cannot follow, and after the 2.45.0 update it made a freshly restarted Portainer look broken ('disappeared', then demands a token nobody can find). package.credentials — the same RPC that powers the login-credentials card on the app page — now extracts the setup_token line from portainer's recent container logs and hands it over with the existing copy-button treatment, titled and explained for a first-time user. The token stops being printed once setup completes, and any container recreate drops the log line, so the card disappears on its own and no dead token lingers. Parsing is a pure, unit-tested scan against the live-captured 2.45.0 log shape (64 hex chars after setup_token=).	2026-09-01 10:28:57 -04:00
archipelago	c188d9de78	fix(lifecycle): abort unsafe declarative uninstall	2026-08-23 07:59:40 -04:00
archipelagoandClaude Fable 5	9ccc325a4d	fix(container): reap ghost containers so an app can't be locked out of itself ... A ghost is a container whose process tree is still running while podman has no record of it: the exit-command's `cleanup --rm` deletes the record, conmon and the payload survive. It keeps owning exactly what the app needs — the published host port and the file locks in its data dir — so the replacement container either fails to bind ("address already in use") or starts and dies on the lock, and Restart=always loops it there forever. Nothing in the stack could see it: every podman-level stop/rm/recreate misses a container podman lost. Seen twice now: 752 restarts on a fleet node (2026-08-10) and again on the dev box today, where Gitea flapped until it fell out of My Apps. Both were cleared by hand; container-doctor.sh has the same logic but is an out-of-band script the daemon never calls. - New container::ghost_reaper: finds conmon processes whose 64-hex container id is absent from `podman ps -a --no-trunc -q`, then kills the payload's children and conmon (TERM, 5s grace, then KILL — the Gitea ghost ignored TERM). Id-based, never name-based: killing by name would hit the live managed container. A failed `podman ps` reaps nothing rather than treating every container as a ghost. - Hooked at repair_before_package_start (covers package.start, package.restart and the orchestrator start path) and in the boot reconciler's 30s tick, so ghosts are cleared before an app is asked to start and swept for every app continuously. Restart feedback: the lifecycle RPCs return {"status":"restarting"} in milliseconds and work in the background, so "Restarting..." flashed for a few frames and the buttons went idle while the app was still down — the click read as a no-op. The hero buttons now show a spinner and hold it off the node's own state (starting/stopping/restarting/updating, plus running + health=starting), and the just-clicked action is held until the backend confirms it picked the work up, with a 12s cap so an unresponsive node still releases the controls. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-08-16 13:45:45 -04:00
archipelagoandClaude Fable 5	6833920778	feat(bitcoin): autoprune default raised 550 → 50000 MB ... Small-disk nodes (<1000 GB data volume) keep the same dynamic prune-vs-archival logic but now retain ~50 GB of recent blocks instead of the bare 550 MB minimum. Takes effect for catalog-covered installs at the next catalog regeneration + signing. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-08-15 09:23:57 -04:00
Archipelago	b67e1527a2	Archipelago — open-source initial import	2026-08-12 10:55:50 +00:00