magnus/btcprice
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Point citadel btcprice at the local btcdata over btc-network

Browse Source 
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
This commit is contained in:
magnus
2026-09-11 18:52:49 +02:00
co-authored by Claude Opus 5
parent 2af8b6f62d
commit 864674bd09
5 changed files with 25 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.env.citadel
+3 -2
View File
@@ -1,8 +1,9 @@
# 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 omarchy (192.168.50.42), publishing its Docker port 4102.
BTCDATA_URL=http://192.168.50.42:4102
# 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