Stabilize Datum container networking
This commit is contained in:
13
README.md
13
README.md
@@ -46,12 +46,13 @@ Allowlist of npubs is set via `NOSTR_ALLOWED_NPUBS`. Anything else is rejected b
|
||||
- Repository URL: `https://git.tx1138.com/lfg2025/gashboard`
|
||||
- Compose path: `docker-compose.yml`
|
||||
- Add env vars (see `.env.example`)
|
||||
- Set `DATUM_URL` to Datum's current container IP:
|
||||
```bash
|
||||
docker inspect -f '{{.NetworkSettings.Networks.umbrel_main_network.IPAddress}}' datum_datum_1
|
||||
```
|
||||
- Use it as `DATUM_URL=http://<that-ip>:21000`.
|
||||
- If Datum/Umbrel recreates the container, refresh this IP in Portainer and redeploy.
|
||||
- Remove any old `DATUM_URL=http://10.21...` value from the stack env vars.
|
||||
Leave `DATUM_URL` unset unless your Datum container name is different. By
|
||||
default the stack uses `http://datum_datum_1:21000` on Umbrel's
|
||||
`umbrel_main_network`, so Datum can be recreated without changing a stale
|
||||
IP address.
|
||||
- If your Umbrel install uses a different Datum container name, set
|
||||
`DATUM_URL=http://<container-name>:21000`.
|
||||
|
||||
4. Open the dashboard, log in with one of the allowed npubs, watch your boards lose at hashing in style.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user