Files
archy/apps
archipelagoandClaude Opus 5 c19c411b91 chore(apps): mirror and bump the upgrades that carry no data migration
With registry push access, the 24 mirror-backed apps stopped being
blocked. Ten images are now mirrored (single-platform amd64, matching
the existing convention) and their pins moved:

  alby-hub          v1.23.0       -> v1.24.0
  mempool-frontend  v3.0.1        -> v3.3.1     (mempool, archy-mempool-web)
  mempool-backend   v3.0.0        -> v3.3.1
  fedimintd         v0.10.0       -> v0.10.1
  gatewayd          v0.10.0       -> v0.10.1
  nostr-rs-relay    0.9.0         -> 0.10.0
  portainer         2.39.1        -> 2.39.6
  vaultwarden       1.30.0-alpine -> 1.37.1-alpine
  jellyfin          10.8.13       -> 10.11.11
  home-assistant    2026.7.3      -> 2026.8.2

Every one verified pullable from our mirror after copying, so none can
become an image-not-found on a node. image-versions.sh moved in lockstep
— it is the baseline the update badge compares against when the catalog
does not cover an app, and leaving it behind would have kept advertising
an update that had already been applied.

Chosen by risk, not by count: these are patch/minor bumps with no data
migration. The ones held back are held for a reason each — Postgres
15->18 and 16->18 refuse to start on an older cluster, Redis 7->8,
Valkey 7->9, Nextcloud 29->32 must go one major at a time, plus
uptime-kuma 1->2, grafana 10->13, electrumx 1->2, photoprism, and
core-lightning's three years of schema migrations. Those are each a
migration plan, not a pin edit. LND (v0.18.4 -> v0.21.2) is held
separately: it is only a minor bump by version but it migrates its
channel database irreversibly, and this box holds real funds.

Note the checker still reports several of these as behind, and that is
correct: it reads the *catalog* pin, which is what nodes actually act on.
These land when the catalog is regenerated and re-signed.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-17 11:22:42 -04:00
..

Archipelago App Manifests

Containerized applications for the Archipelago Bitcoin Node OS. All apps run in rootless Podman with security hardening (cap-drop ALL, readonly root, non-root user, memory limits).

App Categories

Bitcoin & Lightning

  • bitcoin-knots — Full Bitcoin node (v28.1)
  • lnd — Lightning Network Daemon (v0.17.4-beta)
  • btcpay-server — Payment processor (v1.13.5)
  • mempool — Block explorer and fee estimator (v2.5.0)
  • electrumx — Electrum server
  • fedimint — Federated Bitcoin minting (v0.10.0)

Nostr

  • nostr-rs-relay — High-performance Rust relay (v0.9.0)
  • nostrudel — Nostr web client (v0.40.0)

Web5 & Identity

  • did-wallet — Web5 DID Wallet

Self-Hosted Services

  • nextcloud (v28), jellyfin (v10.8.13), immich (release), photoprism (v240915)
  • vaultwarden (v1.30.0-alpine), penpot (v2.4)
  • homeassistant (v2024.1), filebrowser (v2.27.0), searxng (2024.11.17)
  • ollama (v0.5.4), grafana (v10.2.0), portainer (v2.19.4)

Networking

  • tailscale (stable), nginx-proxy-manager (v2.12.1)

Custom & External

  • indeedhub — Bitcoin documentary streaming (custom build)
  • router — Mesh routing and network management
  • botfights — External web app

Manifest Format

Each app has a manifest.yml defining container image, resources, dependencies, security policies, health checks, and network config. See docs/app-manifest-spec.md for the spec.

Quick Reference