phase: 28_gateway_agent_proxy
**Phase 28 final pass — complete, 100 % green.** All five tasks were already `complete/`; this pass verified the criteria, re-ran the live half, and did the docs pass. - Gate `bash .agents/validate.sh` **rc=0**: `1650 passed, 15 skipped`, coverage **98.97 %** (floor 94), `ruff` clean, `pyright` **0 errors**, `node --check` clean, hygiene clean (`/tmp/validate-done.log`). - Live: `pytest -m live --live` **11 passed**; `./scripts/dev-server.sh status` nine sources `ok`; mTLS re-read of `gateway` → agent **1.2.0**, all three sections `available: true`, 6/6 frontends routed, 11 nginx servers + `$targetBackend`, **19** listeners, no core errors (`data/logs/28-finalpass-live.out`); installed agent file byte-identical to this tree (`b0e9ebf1b718…`). - Criteria: 1 ✅ pytest/coverage · 2 ✅ three sections over a captured tree, `false`/`null` + one `errors` line each elsewhere with `cpu`/`mem`/`disk_io`/`system` intact · 3 ✅ `AGENT_VERSION` 1.2.0 + SCHEMA names all three · 4 ✅ six fixtures verbatim, capture refuses a bad read, 116 socket address columns hold no globally routable endpoint · 5 ✅ gateway runs 1.2.0 and answers over mTLS (transcript `data/logs/28-task05-rollout.md`, `28-finalpass-live.out`) · 6 ✅ validate · 7 ✅ additive: HEAD's 1.1.0 and this 1.2.0 `collect()`ed over one `--root` are key-for-key equal plus the three new sections, `--no-proxy` equal exactly (`data/logs/verify-28-final.py` → 41 PASS, `28-final-verify.out`). - Docs fixed (README/AGENTS/Containerfile, all re-green): README's opening said "Four dashboards" above a five-row table and said the new sections are "stored in the snapshot" (they are in the **agent's** document — no `/api` payload, no `sample` row, nothing charts them until phase 29); `Containerfile`'s header still said "three dashboards"; AGENTS's coverage figure (98.94 → **98.97 %**), invariant 6 gained the captured-socket-table identifier rule, the agent bullet gained "phase 28 stops at the wire", and the fleet record names the stash-and-compare control plus the volatile listener count. Full record: `data/logs/NOTES-28-final.md`. - Deviations: none functional; no git index/history touched, phase files untouched (`PLAN.md` and `complete/` unchanged). `uv pip list --outdated` still lists 4 packages (fastapi 0.153→0.161 etc.) — advisory only, dependencies untouched by this phase, left for a deliberate pass. - Next pending phase: `.agents/phases/todo/29_gateway_dashboard_page/` (the page that consumes these three sections).
This commit is contained in:
@@ -0,0 +1,40 @@
|
||||
# Verbatim /etc/nginx/stream.d/stream.conf from gateway-ops, read read-only over the ssh key by
|
||||
# ./scripts/capture-gateway-config.sh (AGENTS.md invariant 7: verify against the
|
||||
# deployed upstream, never guess its shape).
|
||||
# Nothing here is rewritten: it is this fleet's ingress map, and the domains in it are
|
||||
# the data — an inbound name and the target it routes to are what these config sections
|
||||
# exist to report. Key material appears only as the file paths the proxy reads.
|
||||
map $ssl_preread_server_name $targetBackend {
|
||||
default 127.0.0.1:4443;
|
||||
homepage.reeseapps.com reeseapps-homepage.reeselink.com:443;
|
||||
ntfy.reeseapps.com reeseapps-ntfy.reeselink.com:443;
|
||||
gitea.reeseapps.com reeseapps-gitea.reeselink.com:443;
|
||||
aipi.reeseapps.com reeseapps-litellm.reeselink.com:443;
|
||||
chatreesept.reeseapps.com reeseapps-openwebui.reeselink.com:443;
|
||||
keycloak.reeseapps.com reeseapps-keycloak.reeselink.com:443;
|
||||
forgejo.reeseapps.com reeseapps-forgejo.reeselink.com:443;
|
||||
brain.reeseapps.com reeseapps-brain-of-reese.reeselink.com:443;
|
||||
brain-of-code.reeseapps.com reeseapps-brain-of-code.reeselink.com:443;
|
||||
immich.reeseapps.com reeseapps-immich.reeselink.com:443;
|
||||
|
||||
stackexpected.com stackexpected.reeselink.com:443;
|
||||
gitea.stackexpected.com stackexpected-gitea.reeselink.com:443;
|
||||
keycloak.stackexpected.com stackexpected-keycloak.reeselink.com:443;
|
||||
nextcloud.stackexpected.com stackexpected-nextcloud.reeselink.com:443;
|
||||
hedgedoc.stackexpected.com stackexpected-hedgedoc.reeselink.com:443;
|
||||
wellsfamilycounseling.reeseapps.com wfc.reeselink.com:443;
|
||||
}
|
||||
|
||||
server {
|
||||
listen 443;
|
||||
listen [::]:443;
|
||||
|
||||
proxy_connect_timeout 1800s;
|
||||
proxy_timeout 1800s;
|
||||
proxy_protocol on;
|
||||
|
||||
proxy_pass $targetBackend;
|
||||
ssl_preread on;
|
||||
|
||||
resolver 10.1.0.1;
|
||||
}
|
||||
Reference in New Issue
Block a user