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>
84 lines
2.1 KiB
YAML
84 lines
2.1 KiB
YAML
app:
|
|
id: mempool-api
|
|
name: Mempool API
|
|
version: 3.0.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: mempool/mempool
|
|
description: Backend API for mempool explorer.
|
|
|
|
container:
|
|
image: source.archipelago-foundation.org/lfg2025/mempool-backend:v3.0.0
|
|
pull_policy: if-not-present
|
|
network: archy-net
|
|
# CORE_RPC_HOST must follow the node's actual Bitcoin container — Knots or
|
|
# Core — resolved at apply time from host facts (B12). Hardcoding either
|
|
# breaks mempool's RPC connection on the other.
|
|
derived_env:
|
|
- key: CORE_RPC_HOST
|
|
template: "{{BITCOIN_HOST}}"
|
|
secret_env:
|
|
- key: CORE_RPC_PASSWORD
|
|
secret_file: bitcoin-rpc-password
|
|
- key: DATABASE_PASSWORD
|
|
secret_file: mempool-db-password
|
|
|
|
dependencies:
|
|
- app_id: bitcoin-knots
|
|
version: ">=26.0"
|
|
- app_id: electrumx
|
|
version: ">=1.18.0"
|
|
- app_id: archy-mempool-db
|
|
version: ">=11.4.10"
|
|
- bitcoin:archival
|
|
|
|
resources:
|
|
memory_limit: 2Gi
|
|
disk_limit: 20Gi
|
|
|
|
security:
|
|
capabilities: []
|
|
readonly_root: false
|
|
network_policy: isolated
|
|
|
|
ports:
|
|
- host: 8999
|
|
container: 8999
|
|
protocol: tcp
|
|
bind: 127.0.0.1
|
|
auth: local
|
|
|
|
volumes:
|
|
- type: bind
|
|
source: /var/lib/archipelago/mempool
|
|
target: /data
|
|
options: [rw]
|
|
|
|
environment:
|
|
- MEMPOOL_BACKEND=electrum
|
|
- ELECTRUM_HOST=electrumx
|
|
- ELECTRUM_PORT=50001
|
|
- ELECTRUM_TLS_ENABLED=false
|
|
- CORE_RPC_PORT=8332
|
|
- CORE_RPC_USERNAME=archipelago
|
|
- DATABASE_ENABLED=true
|
|
- DATABASE_HOST=archy-mempool-db
|
|
- DATABASE_DATABASE=mempool
|
|
- DATABASE_USERNAME=mempool
|
|
|
|
health_check:
|
|
type: http
|
|
endpoint: http://localhost:8999
|
|
path: /api/v1/backend-info
|
|
interval: 30s
|
|
timeout: 5s
|
|
retries: 3
|
|
|
|
bitcoin_integration:
|
|
rpc_access: read-only
|
|
sync_required: true
|
|
pruning_support: false
|