Clarify Railiance01 production IP vs CoulombCore bootstrap
Some checks failed
ci / validate-registry (push) Has been cancelled

Production hub runs on 92.205.62.239; document config-hosteurope deploy path.
This commit is contained in:
2026-06-15 10:24:32 +02:00
parent 74570c6a4c
commit 21747a7e07
2 changed files with 9 additions and 3 deletions

View File

@@ -31,9 +31,14 @@ Mount a PVC at `/data` for persistence. Inject secrets via Kubernetes Secret
| Item | Value |
|---|---|
| URL | `https://reuse.coulomb.social` |
| DNS A record | `92.205.62.239` (operator confirmed 2026-06-15) |
| DNS A record | **`92.205.62.239`** (Railiance01 production) |
Verify propagation: `dig +short reuse.coulomb.social A`
CoulombCore (`92.205.130.254`) held a bootstrap deploy; production release uses
`KUBECONFIG=~/.kube/config-hosteurope`. Verify propagation:
```bash
dig +short reuse.coulomb.social A # must return 92.205.62.239
```
## Client configuration

View File

@@ -15,7 +15,8 @@ state_hub_workstream_id: "c4171a8c-604e-4214-b189-2094477aa6ea"
# Federation hub service on railiance01 and hub CLI
Close the next federation gap: a **hosted registry hub** on production cluster
node `railiance01` (`92.205.130.254`) that records which repositories publish
node **Railiance01** (`92.205.62.239`; CoulombCore `92.205.130.254` is
bootstrap only) that records which repositories publish
capability indexes, plus a **CLI client** for registering and updating those
records without hand-editing `registry/federation/sources.yaml` on every machine.