Files
magnusandClaude Opus 5 864674bd09 Point citadel btcprice at the local btcdata over btc-network
omarchy is gone, but the citadel deployment still set
BTCDATA_URL=http://192.168.50.42:4102 and ran standalone on its own
compose network. Every request that proxies to btcdata failed with
httpx.ConnectError: All connection attempts failed.

btcdata now runs on citadel too, so attach btcprice to the external
btc-network there and reach it by service name at http://btcdata:4102.
deploy-citadel.sh creates the network on the remote if missing, as
btcdata's own deploy script already does.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TRkiLhK5qhkZjP2adxpA3e
2026-09-11 18:52:49 +02:00

10 lines
390 B
Bash

# Environment for the citadel deployment. deploy-citadel.sh copies this to
# $APP_DIR/.env on the target host. No secrets — btcprice has none.
# btcdata runs on citadel too, in the shared btc-network. Reached by service
# name; the port must match DOCKER_BTCDATA_PORT in ../btcdata/.env.
BTCDATA_URL=http://btcdata:4102
# Host port; container always listens on 4040.
BTCPRICE_PORT=4041