archipelagoandClaude Fable 5
58cdea5e79
Demo images / Build & push demo images (push) Successful in 3m33s
Some apps carry a complete account system and are broken by an upstream challenge: git clients speak basic-auth (not browser cookies), and a BTCPay checkout link handed to a customer must open for that customer. Both were behind the gate's login page — the "non-browser clients need an access token" gap disclosed in five consecutive releases. - New manifest port policy `auth: open`: the daemon still fronts the port exactly like `gated` (loopback pin, external binds, frame-header fixes, app-down retry page, Tor upstream) but serves it without the login challenge. Requires auth_rationale, same burden of proof as `none`. Gitea 3001 and BTCPay 23000 declare it. - Runtime operator override per app (security.set-app-gate → app-configs/ <id>.json "gateEnabled"), surfaced as Settings → app → Access control. Wins over the manifest in both directions and applies on the next request — no restart, and it works today on catalog-covered apps whose signed manifest still says `gated`. - The gate resolves policy per-request from the live port map, so a toggle takes effect without waiting for the 60s rebind sweep. "Off" never releases the port: gated apps are loopback-pinned, so releasing would strand them, not open them. - security.app-gate-status now reports gate_enabled + any override. - New guard test pins the `auth: open` set (both entries reviewed); the `auth: none` count moves 25 → 26, absorbing pre-existing drift from the phoenixd onboarding (loopback JSON API with its own generated password). - Docs: the manifest spec's ports row documented only host/container/ protocol — bind, auth, auth_rationale and session_passthrough were undocumented. Added a full "Ports & the app gate" section plus a developer-guide entry telling app authors to enforce their own auth regardless, since the operator can flip the gate either way. Verified live on archi-dev-box from an external address: gated → 401 gate page; override off → Gitea 200 own page, BTCPay 302 to its own login, git-over-HTTP info/refs 200; override on → 401 again; clear → default. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
108 lines
3.1 KiB
YAML
108 lines
3.1 KiB
YAML
app:
|
|
id: btcpay-server
|
|
name: BTCPay Server
|
|
version: 2.4.2
|
|
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
|