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
This commit is contained in:
@@ -49,13 +49,13 @@ architecture (citadel is x86_64 → `linux/amd64`), copies `docker-compose.citad
|
||||
pipes the image over SSH with `docker save | docker load`, and runs
|
||||
`docker compose up -d --no-build`. No registry involved.
|
||||
|
||||
Deployed btcprice listens on **http://192.168.50.195:4041** and proxies to the btcdata already
|
||||
running on omarchy (`http://192.168.50.42:4102`, set via `BTCDATA_URL` in `.env.citadel`) —
|
||||
citadel runs no btcdata of its own, so the deployment compose is standalone with no
|
||||
`btc-network`.
|
||||
Deployed btcprice listens on **http://192.168.50.195:4041** and proxies to the btcdata running
|
||||
on citadel as well. Both attach to the external `btc-network` there, so `BTCDATA_URL` is
|
||||
`http://btcdata:4102` (set in `.env.citadel`) — the service name inside the network, not a LAN
|
||||
address. The deploy script creates `btc-network` on the host if it does not exist yet.
|
||||
|
||||
Overridable: `BTCPRICE_DEPLOY_HOST`, `BTCPRICE_DEPLOY_DIR`, `BTCPRICE_IMAGE_NAME`,
|
||||
`BTCPRICE_PLATFORM`.
|
||||
`BTCPRICE_PLATFORM`, `BTCPRICE_NETWORK`.
|
||||
|
||||
## Environment Variables
|
||||
|
||||
|
||||
Reference in New Issue
Block a user