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

Document Postgres on citadel, drop stale omarchy references

Browse Source 
The database moved to citadel (192.168.50.195); .env and the deployed
container already point there, but env.example still handed out the old
omarchy address.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EWRh3vxBcqwDbuWv2dfQYF
This commit is contained in:
magnus
2026-09-11 16:04:16 +02:00
co-authored by Claude Opus 5
parent 61679c5ddc
commit fb334c7703
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
env.example
+3 -3
View File
@@ -20,10 +20,10 @@ STRIKE_ENABLED=false
KRAKEN_ENABLED=false
# --- Docker (docker compose up -d) ---
# Runs alongside local dev on its own port. `postgres` resolves to the Docker
# host via extra_hosts: host-gateway.
# Runs alongside local dev on its own port. Points at the Postgres on citadel
# (192.168.50.195) directly, so it works from any host that can reach that LAN.
DOCKER_BTCDATA_PORT=4102
DOCKER_JDBC_URL=jdbc:postgresql://postgres:5432/btcprod?user=postgres&password=changeme
DOCKER_JDBC_URL=jdbc:postgresql://192.168.50.195:5432/btcprod?user=postgres&password=changeme
DOCKER_CORS_ORIGIN=http://localhost:4041
DOCKER_FRANKFURTER_URL=http://frankfurter:8080