archipelagoandClaude Opus 5
8e814ca06a
Demo images / Build & push demo images (push) Failing after 2m22s
Replaces the registry host across 86 files: 309 references, covering all 40 app manifests, the orchestrator and container crates, the release and catalog scripts, both demo-images workflows, the ISO builder, demo-deploy, and the frontend marketplace data. Verified the domain actually serves the registry before rewriting anything, rather than assuming the web host implies the registry: - TLS verifies clean, HTTP/2 on the web root - an anonymous token grants a manifest fetch (HTTP 200) with no credentials - skopeo inspect --no-creds resolves an image and lists its tags That last check is the one that matters: an outside developer with no account can now pull, which was the functional blocker for publishing at all. Plain-HTTP references become HTTPS in the same pass, so OTA downloads stop crossing the network in the clear. Deliberately NOT rewritten: - The public FIPS anchor on port 8444. It is a functional network endpoint every node dials to bootstrap the mesh — closer to Bitcoin Core's hardcoded seeds than to leaked infrastructure. The domain does resolve to the same host, so it could become a hostname, but that adds a DNS dependency to the path used precisely when things are broken. Worth a deliberate decision, not a side effect of this change. - The companion APK on port 2100. The domain returns 404 for that path, so rewriting it would swap a working URL for a broken one. The Releases page does serve (200), which is where the plan already wants those binaries. - releases/app-catalog.json, releases/manifest.json and release-manifest.json. These carry `signature` and `signed_by`; editing their contents invalidates the signature and the fleet refuses artifacts that fail verification. They were rewritten in a first pass and reverted — they must be regenerated and re-signed through the signing ceremony instead, which needs the mnemonic. So the catalog still advertises the old host until that ceremony runs. Nodes resolve images through the signed catalog, not the on-disk manifests, so this commit alone does not change what a node pulls. Verified: archipelago-container 75/75; every manifest still parses with a top-level app block; no signed artifact modified. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
99 lines
3.5 KiB
YAML
99 lines
3.5 KiB
YAML
app:
|
|
id: fedimint-gateway
|
|
name: Fedimint Gateway
|
|
version: 0.10.0
|
|
description: Fedimint gateway service with automatic LND-or-LDK backend selection.
|
|
|
|
container:
|
|
image: source.archipelago-foundation.org/lfg2025/gatewayd:v0.10.0
|
|
pull_policy: if-not-present
|
|
network: archy-net
|
|
entrypoint: ["sh", "-lc"]
|
|
# The bitcoind host comes from $FM_BITCOIND_URL, filled by the
|
|
# {{BITCOIN_HOST}} derived-env below — it resolves to whichever bitcoin
|
|
# container is actually running (Knots, Core, or any future distro archy
|
|
# ships), so the gateway is never pinned to one node's container name.
|
|
# (Was hardcoded http://host.archipelago:8332 — the host gateway IP where
|
|
# bitcoind does not listen — which crash-looped the gateway, 2026-07-22.)
|
|
custom_args:
|
|
- >-
|
|
if [ -f /lnd/tls.cert ] && [ -f /lnd/data/chain/bitcoin/mainnet/admin.macaroon ]; then
|
|
exec gatewayd --data-dir /data --listen 0.0.0.0:8176 --bcrypt-password-hash "$FEDI_HASH" --network bitcoin --bitcoind-url "$FM_BITCOIND_URL" --bitcoind-username "$FM_BITCOIND_USERNAME" --bitcoind-password "$FM_BITCOIND_PASSWORD" lnd --lnd-rpc-host lnd:10009 --lnd-tls-cert /lnd/tls.cert --lnd-macaroon /lnd/data/chain/bitcoin/mainnet/admin.macaroon;
|
|
else
|
|
exec gatewayd --data-dir /data --listen 0.0.0.0:8176 --bcrypt-password-hash "$FEDI_HASH" --network bitcoin --bitcoind-url "$FM_BITCOIND_URL" --bitcoind-username "$FM_BITCOIND_USERNAME" --bitcoind-password "$FM_BITCOIND_PASSWORD" ldk --ldk-lightning-port 9737 --ldk-alias archipelago-gateway;
|
|
fi
|
|
derived_env:
|
|
- key: FM_BITCOIND_URL
|
|
template: "http://{{BITCOIN_HOST}}:8332"
|
|
# The gateway's admin API is gated by a bcrypt password hash. Generate it on
|
|
# first install (random password + its bcrypt hash, both 0600 rootless-owned)
|
|
# so the app installs from its manifest alone — `fedimint-gateway-hash` holds
|
|
# the hash passed to gatewayd, `fedimint-gateway-hash.pw` the plaintext for
|
|
# any client that must authenticate. Self-heals a wrongly root-owned hash.
|
|
generated_secrets:
|
|
- name: fedimint-gateway-hash
|
|
kind: bcrypt
|
|
secret_env:
|
|
- key: FM_BITCOIND_PASSWORD
|
|
secret_file: bitcoin-rpc-password
|
|
- key: FEDI_HASH
|
|
secret_file: fedimint-gateway-hash
|
|
data_uid: "1000:1000"
|
|
|
|
dependencies:
|
|
- app_id: bitcoin-core
|
|
version: ">=26.0"
|
|
- app_id: fedimint
|
|
version: ">=0.10.0"
|
|
|
|
resources:
|
|
cpu_limit: 2
|
|
memory_limit: 2Gi
|
|
disk_limit: 10Gi
|
|
|
|
security:
|
|
capabilities: []
|
|
readonly_root: true
|
|
network_policy: isolated
|
|
|
|
ports:
|
|
- host: 8176
|
|
container: 8176
|
|
protocol: tcp
|
|
auth: none
|
|
auth_rationale: >-
|
|
Fedimint gateway API, protected by its own bcrypt password (--bcrypt-password-hash)
|
|
and reached by federation peers and clients that cannot hold a browser session.
|
|
- host: 9737
|
|
container: 9737
|
|
protocol: tcp
|
|
auth: none
|
|
auth_rationale: >-
|
|
LDK Lightning p2p for the gateway. The BOLT-8 noise handshake authenticates and
|
|
encrypts the connection itself.
|
|
|
|
volumes:
|
|
- type: bind
|
|
source: /var/lib/archipelago/fedimint-gateway
|
|
target: /data
|
|
options: [rw]
|
|
- type: bind
|
|
source: /var/lib/archipelago/lnd
|
|
target: /lnd
|
|
options: [ro]
|
|
|
|
environment:
|
|
- FM_BITCOIND_USERNAME=archipelago
|
|
|
|
health_check:
|
|
type: http
|
|
endpoint: http://localhost:8176
|
|
path: /
|
|
interval: 30s
|
|
timeout: 5s
|
|
retries: 3
|
|
|
|
bitcoin_integration:
|
|
rpc_access: admin
|
|
sync_required: true
|