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
CLAUDE.md
+4 -3
View File
@@ -38,9 +38,10 @@ unused — the port in `CMD` is hardcoded.
Mirrors `../elprice/deploy-citadel.sh`; no registry.
- `docker-compose.citadel.yml` → remote `docker-compose.yml`; `.env.citadel` → remote `.env`.
- Standalone (no `btc-network`): citadel has no btcdata, so `BTCDATA_URL` points at the btcdata
on omarchy, `http://192.168.50.42:4102`.
- Live at http://192.168.50.195:4041. A separate btcprice also still runs on omarchy at :4041.
- btcdata also runs on citadel, so both attach to the external `btc-network` there and
`BTCDATA_URL` is `http://btcdata:4102` (service name, not a LAN address). The deploy script
creates the network on the remote if it is missing.
- Live at http://192.168.50.195:4041.
## Architecture