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>
114 lines
3.4 KiB
YAML
114 lines
3.4 KiB
YAML
app:
|
|
id: btcpay-server
|
|
name: BTCPay Server
|
|
version: 2.4.2
|
|
# 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: btcpayserver/btcpayserver
|
|
description: Self-hosted Bitcoin payment processor. Accept Bitcoin payments without intermediaries.
|
|
|
|
container:
|
|
image: docker.io/btcpayserver/btcpayserver:2.4.2
|
|
pull_policy: if-not-present
|
|
network: archy-net
|
|
secret_env:
|
|
- key: BTCPAY_BTCRPCPASSWORD
|
|
secret_file: bitcoin-rpc-password
|
|
- key: BTCPAY_DB_PASS
|
|
secret_file: btcpay-db-password
|
|
# Internal LND node. Generated by the daemon (lnd macaroon as hex +
|
|
# tls.cert thumbprint) — see container::lnd::ensure_btcpay_lnd_connection_secret.
|
|
# Optional: nodes without LND run btcpay without an internal node.
|
|
- key: BTCPAY_BTCLIGHTNING
|
|
secret_file: btcpay-lnd-connection
|
|
optional: true
|
|
derived_env:
|
|
- key: BTCPAY_HOST
|
|
template: "{{HOST_IP}}:23000"
|
|
|
|
dependencies:
|
|
- app_id: bitcoin-core
|
|
version: ">=26.0"
|
|
- app_id: archy-btcpay-db
|
|
version: ">=15.17"
|
|
- app_id: archy-nbxplorer
|
|
version: ">=2.6.0"
|
|
|
|
resources:
|
|
cpu_limit: 2
|
|
memory_limit: 2Gi
|
|
disk_limit: 20Gi
|
|
|
|
security:
|
|
capabilities: []
|
|
readonly_root: false
|
|
network_policy: isolated
|
|
|
|
ports:
|
|
- host: 23000
|
|
container: 49392
|
|
protocol: tcp
|
|
bind: 127.0.0.1
|
|
# open, not gated: BTCPay has its own account system, and its public
|
|
# surfaces (checkout/invoice pages, payment buttons, webhooks) must be
|
|
# reachable by anonymous payers and machines — a dashboard login in
|
|
# front of a checkout link breaks the product. The gate still fronts
|
|
# the port; the operator can force the dashboard login back on from
|
|
# Settings → BTCPay Server → Access control.
|
|
auth: open
|
|
auth_rationale: >-
|
|
BTCPay enforces its own login for administration, and its checkout,
|
|
invoice and webhook endpoints are designed to be reached by
|
|
anonymous payers and payment processors.
|
|
|
|
volumes:
|
|
- type: bind
|
|
source: /var/lib/archipelago/btcpay
|
|
target: /datadir
|
|
options: [rw]
|
|
|
|
environment:
|
|
- ASPNETCORE_URLS=http://0.0.0.0:49392
|
|
- BTCPAY_PROTOCOL=http
|
|
- BTCPAY_CHAINS=btc
|
|
# Plugins must live on the persistent volume: the image default
|
|
# (/root/.btcpayserver/Plugins) is container-local, so every recreate
|
|
# silently wiped installed plugins.
|
|
- BTCPAY_PLUGINDIR=/datadir/Plugins
|
|
- BTCPAY_BTCEXPLORERURL=http://archy-nbxplorer:32838
|
|
- BTCPAY_BTCRPCURL=http://bitcoin-knots:8332
|
|
- BTCPAY_BTCRPCUSER=archipelago
|
|
- BTCPAY_POSTGRES=Username=btcpay;Password=${BTCPAY_DB_PASS};Host=archy-btcpay-db;Port=5432;Database=btcpay
|
|
|
|
health_check:
|
|
type: http
|
|
endpoint: http://localhost:49392
|
|
path: /
|
|
interval: 30s
|
|
timeout: 30s
|
|
retries: 5
|
|
|
|
bitcoin_integration:
|
|
rpc_access: read-only
|
|
sync_required: true
|
|
|
|
lightning_integration:
|
|
payment_processing: false
|
|
invoice_management: true
|
|
|
|
interfaces:
|
|
main:
|
|
name: Web UI
|
|
description: BTCPay Server dashboard
|
|
type: ui
|
|
port: 23000
|
|
protocol: http
|
|
path: /
|
|
|
|
metadata:
|
|
launch:
|
|
open_in_new_tab: true
|