Files
2026-11-01 15:54:36 +10:00

41 lines
1.6 KiB
YAML

version: '3.7'
services:
app_proxy:
environment:
APP_HOST: fedimintd_fedimintd_1
APP_PORT: 8175 # ui
fedimintd:
image: fedimint/fedimintd:v0.13.0@sha256:9bc451298a9cf34f982379754386aa446b72cb00dca5d25ad57d41429f247119
ports:
- 8173:8173/tcp # p2p tls
- 8173:8173/udp # p2p iroh
- 8174:8174/udp # api iroh
- 8184:8184/udp # transitional Iroh 1.0 api
volumes:
- ${APP_DATA_DIR}/data:/data
environment:
FM_ENABLE_IROH: "true"
FM_DATA_DIR: "/data"
FM_BITCOIN_NETWORK: ${APP_BITCOIN_NETWORK_ELECTRS}
FM_BITCOIND_USERNAME: ${APP_BITCOIN_RPC_USER}
FM_BITCOIND_PASSWORD: ${APP_BITCOIN_RPC_PASS}
FM_BITCOIND_URL: "http://${APP_BITCOIN_NODE_IP}:${APP_BITCOIN_RPC_PORT}"
FM_BIND_UI: 0.0.0.0:8175
# Guardian admin credentials, split in two since v0.12.0.
#
# FM_PASSWORD_UI gates the web UI. When unset, fedimintd falls back to the
# legacy password.private file, and if that is absent too it serves the UI
# with no login form. Upstream treats that as safe only for the default
# loopback bind, but we bind 0.0.0.0 above.
#
# FM_PASSWORD_API gates admin RPCs on the public API (WS on bind-api and
# iroh on 8174/udp) and is what fedimint-cli admin authenticates with.
# It never falls back to disk; unset means admin RPCs return 401. Public
# client endpoints are unaffected either way. Same value as the UI so the
# guardian can read it from Umbrel's "Show password".
FM_PASSWORD_UI: "${APP_PASSWORD}"
FM_PASSWORD_API: "${APP_PASSWORD}"
restart: on-failure