archipelagoandClaude Opus 5
eb48eab946
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>
82 lines
2.2 KiB
YAML
82 lines
2.2 KiB
YAML
app:
|
|
id: alby-hub
|
|
name: Alby Hub
|
|
version: 1.23.0
|
|
# Where this app comes from, so scripts/check-upstream-releases.py can
|
|
# tell us when the pin below has fallen behind. Without it nothing can:
|
|
# container.image names our mirror, not the project it was mirrored from.
|
|
upstream:
|
|
kind: github
|
|
repo: getAlby/hub
|
|
description: Self-custodial Lightning wallet hub. Runs its own Lightning node on your Archipelago and connects your apps to it over Nostr Wallet Connect — one hub, every app pays through it.
|
|
category: money
|
|
|
|
container:
|
|
image: source.archipelago-foundation.org/lfg2025/alby-hub:v1.23.0
|
|
pull_policy: if-not-present
|
|
|
|
dependencies:
|
|
- storage: 1Gi
|
|
|
|
resources:
|
|
cpu_limit: 1
|
|
memory_limit: 512Mi
|
|
disk_limit: 2Gi
|
|
|
|
security:
|
|
capabilities: []
|
|
readonly_root: true
|
|
no_new_privileges: true
|
|
network_policy: bridge
|
|
|
|
ports:
|
|
- host: 8187
|
|
container: 8080
|
|
protocol: tcp
|
|
bind: 127.0.0.1
|
|
auth: gated
|
|
|
|
volumes:
|
|
- type: bind
|
|
source: /var/lib/archipelago/alby-hub
|
|
target: /data
|
|
options: [rw]
|
|
|
|
environment:
|
|
- WORK_DIR=/data
|
|
- PORT=8080
|
|
# LDK peers are dialed outbound-only in v1; no inbound p2p port is
|
|
# advertised, so no extra port mapping is needed for payments to work.
|
|
- LOG_LEVEL=info
|
|
|
|
health_check:
|
|
type: http
|
|
endpoint: http://localhost:8080
|
|
path: /
|
|
interval: 30s
|
|
timeout: 5s
|
|
retries: 5
|
|
|
|
interfaces:
|
|
main:
|
|
name: Web UI
|
|
description: Alby Hub wallet interface
|
|
type: ui
|
|
port: 8187
|
|
protocol: http
|
|
|
|
metadata:
|
|
icon: /assets/img/app-icons/alby-hub.svg
|
|
repo: https://github.com/getAlby/hub
|
|
tier: optional
|
|
launch:
|
|
# Embedded: the gate neutralizes Alby Hub's X-Frame-Options: DENY on
|
|
# proxied responses. Nodes older than the gate fix show a blocked
|
|
# frame — flip to true only if targeting such nodes.
|
|
open_in_new_tab: false
|
|
features:
|
|
- Self-custodial Lightning node (LDK) with a friendly wallet UI
|
|
- Connect wallets and apps via Nostr Wallet Connect (NWC)
|
|
- Per-app budgets and isolated sub-wallets
|
|
- Works with the Alby browser extension and mobile app
|