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>
97 lines
2.9 KiB
YAML
97 lines
2.9 KiB
YAML
app:
|
|
id: electrumx
|
|
name: ElectrumX
|
|
version: 1.18.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: spesmilo/electrumx
|
|
description: Electrum server indexing Bitcoin chain data for lightweight wallet queries.
|
|
|
|
container:
|
|
image: source.archipelago-foundation.org/lfg2025/electrumx:v1.18.0
|
|
pull_policy: if-not-present
|
|
network: archy-net
|
|
data_uid: "1000:1000"
|
|
entrypoint: ["sh", "-lc"]
|
|
# The bitcoin backend container is bitcoin-knots OR bitcoin-core depending
|
|
# on which version the node runs (multi-version switch) — probe which name
|
|
# resolves on archy-net instead of hardcoding knots, which left electrumx
|
|
# permanently disconnected (block index 0) on core nodes.
|
|
custom_args:
|
|
- >-
|
|
for h in bitcoin-knots bitcoin-core; do
|
|
if getent hosts "$h" >/dev/null 2>&1; then BTC_HOST="$h"; break; fi;
|
|
done;
|
|
export DAEMON_URL="http://archipelago:$(printenv BITCOIN_RPC_PASS)@${BTC_HOST:-bitcoin-knots}:8332/";
|
|
exec electrumx_server
|
|
secret_env:
|
|
- key: BITCOIN_RPC_PASS
|
|
secret_file: bitcoin-rpc-password
|
|
|
|
dependencies:
|
|
- app_id: bitcoin-knots
|
|
version: ">=26.0"
|
|
- storage: 50Gi
|
|
- bitcoin:archival
|
|
|
|
resources:
|
|
cpu_limit: 0
|
|
memory_limit: 6Gi
|
|
disk_limit: 50Gi
|
|
|
|
security:
|
|
capabilities: [DAC_OVERRIDE]
|
|
readonly_root: false
|
|
network_policy: isolated
|
|
|
|
ports:
|
|
- host: 50001
|
|
container: 50001
|
|
protocol: tcp
|
|
auth: none
|
|
auth_rationale: >-
|
|
Electrum wire protocol over TCP. Electrum wallets speak it directly and cannot hold a session cookie.
|
|
|
|
volumes:
|
|
- type: bind
|
|
source: /var/lib/archipelago/electrumx
|
|
target: /data
|
|
options: [rw]
|
|
|
|
environment:
|
|
- COIN=Bitcoin
|
|
- DB_DIRECTORY=/data
|
|
- SERVICES=tcp://:50001,rpc://0.0.0.0:8000
|
|
- CACHE_MB=1024
|
|
- MAX_SEND=10000000
|
|
|
|
# The ElectrumX dashboard tile is served by the host-networked companion UI
|
|
# (archy-electrs-ui) on port 50002, NOT by this container. Declaring it here
|
|
# lets the catalog generator emit electrumx -> 50002 into GENERATED_APP_PORTS
|
|
# so the tile resolves a launch URL without relying on the hand-maintained
|
|
# override in appSessionConfig.ts (which the generator can clobber). The
|
|
# backend only validates this block — it does not proxy/health-check it.
|
|
interfaces:
|
|
main:
|
|
name: Web UI
|
|
description: ElectrumX server status and connection details
|
|
type: ui
|
|
port: 50002
|
|
protocol: http
|
|
|
|
health_check:
|
|
type: tcp
|
|
endpoint: localhost:50001
|
|
interval: 30s
|
|
timeout: 5s
|
|
retries: 3
|
|
start_period: 10m
|
|
|
|
bitcoin_integration:
|
|
rpc_access: read-only
|
|
sync_required: true
|
|
pruning_support: false
|