coulomb/the-custodian
4
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

Orientation §2: record why bao.coulomb.social fails and the fixed workstation default
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 8s
Details

Browse source 
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
codex 2026-09-22 22:32:57 +02:00
parent b41610b8f4
commit 7980edd7e2
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/agent-environment-orientation.md
View file

@ -31,7 +31,7 @@ Services are private by default (railiance-master ADR-0008) and are reached thro
| OpenBao | `http://127.0.0.1:18200` | `openbao-ui-railiance01` |
| k3s API | `https://127.0.0.1:16444` (`~/.kube/config` → `config-railiance01`) | `k3s-api-railiance01` |
**Trap:** the shell default `BAO_ADDR=https://bao.coulomb.social` is **unreachable** from the workstation. Use `BAO_ADDR=http://127.0.0.1:18200` (and `VAULT_ADDR` the same) for any `bao` command.
**Trap (fixed on the workstation 2026-09-22):** `BAO_ADDR`/`VAULT_ADDR` used to default to `https://bao.coulomb.social`, which is **unreachable**: it resolves to railiance01, but Traefik serves its default self-signed certificate there and no route matches the host (`-k` still gives 404). `~/.bashrc` now exports `http://127.0.0.1:18200` for both. A shell opened before that change, or any other host, still needs the prefix on every `bao` command. Whether the public name should exist at all is railiance-platform's call (hub message `e8ccbc2f`).
## 3. Permissions and the agent harness (Claude Code)