Skip to content

Commit 08b7783

Browse files
docs: scrub environment-specific endpoint from proxy spec
Replace the real tailnet hostname and IP with honcho.example.net / a generic tailnet reference — specs and PRs should carry examples, not live endpoints.
1 parent 3ea6a73 commit 08b7783

1 file changed

Lines changed: 9 additions & 9 deletions

File tree

‎docs/superpowers/specs/2026-06-02-honcho-api-proxy-design.md‎

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@
1010

1111
The web build (`@openconcho/web`) talks to Honcho directly from the browser. When
1212
the configured instance URL is a different origin than the page (e.g. a self-hosted
13-
Honcho at `https://honcho.hydra-capella.ts.net` while the UI runs on
13+
Honcho at `https://honcho.example.net` while the UI runs on
1414
`http://localhost:8080`), the browser issues a CORS preflight on the `Authorization`
1515
header and the request fails — Honcho ships no `CORSMiddleware`.
1616

@@ -23,12 +23,12 @@ the moment a user typed an absolute URL into Settings — which is the bug that
2323

2424
### Evidence gathered
2525

26-
- Browser → `honcho.hydra-capella.ts.net` is reachable; the CORS error proves the
26+
- Browser → `honcho.example.net` is reachable; the CORS error proves the
2727
request reached Honcho and only the browser policy check failed.
2828
- A Docker container under Colima **also** reaches the tailnet: `docker run ...
29-
curl https://honcho.hydra-capella.ts.net/health` returned **HTTP 200**, connected
30-
to `100.72.133.27:443` with TLS verified. So a container-side proxy is viable on
31-
this host (Colima forwards container egress through the host's tailnet routing).
29+
curl https://honcho.example.net/health` returned **HTTP 200**, connected over the
30+
tailnet on `:443` with TLS verified. So a container-side proxy is viable on this
31+
host (Colima forwards container egress through the host's tailnet routing).
3232

3333
## Decisions
3434

@@ -53,15 +53,15 @@ the moment a user typed an absolute URL into Settings — which is the bug that
5353
```
5454
WEB (docker + dev):
5555
browser ──same-origin──▶ /api/v3/... (openapi-fetch base = "/api")
56-
X-Honcho-Upstream: https://honcho.hydra-capella.ts.net (from instance.baseUrl)
56+
X-Honcho-Upstream: https://honcho.example.net (from instance.baseUrl)
5757
Authorization: Bearer … (unchanged, when set)
5858
│ proxy: validate header, allowlist-check, strip "/api",
5959
│ proxy_pass $upstream, set SNI/Host, drop routing header
6060
▼
61-
https://honcho.hydra-capella.ts.net/v3/... (server-side hop — no CORS)
61+
https://honcho.example.net/v3/... (server-side hop — no CORS)
6262
6363
TAURI:
64-
webview ──reqwest──▶ https://honcho.hydra-capella.ts.net/v3/... (unchanged)
64+
webview ──reqwest──▶ https://honcho.example.net/v3/... (unchanged)
6565
```
6666

6767
**Why a custom header is free here:** `X-Honcho-Upstream` rides a *same-origin*
@@ -156,7 +156,7 @@ the docker image (local/CI parity).
156156
`src/lib/runtimeConfig.ts`.
157157
- **Retire `HONCHO_UPSTREAM`** from compose — the upstream now comes from the header.
158158
- New optional `OPENCONCHO_UPSTREAM_ALLOWLIST` (comma-separated host globs, e.g.
159-
`honcho.hydra-capella.ts.net,*.honcho.dev`). The entrypoint renders it into the
159+
`honcho.example.net,*.honcho.dev`). The entrypoint renders it into the
160160
nginx `map` for `$allow_upstream`; unset ⇒ map default 1.
161161

162162
## Data flow (Fleet aggregation, web mode)

0 commit comments

Comments
 (0)