remove the agent's live terminal page and the endpoints only it used
This commit is contained in:
parent
802151820c
commit
6289b8d64b
1 changed files with 127 additions and 4053 deletions
|
|
@ -17,7 +17,7 @@ always on), the gateway proxies all operator-facing traffic, and
|
|||
## Two principals, two paths
|
||||
|
||||
- **Operator** — reaches every UI (the dashboard + every
|
||||
per-agent page) through the gateway, on one origin.
|
||||
per-agent web server) through the gateway, on one origin.
|
||||
The core daemon serves operator-authority actions
|
||||
(answer-as-operator, lifecycle POSTs), reachable only via the
|
||||
gateway.
|
||||
|
|
@ -67,13 +67,11 @@ netns-isolated for the same reason.
|
|||
|
||||
The boundary rests on three layers:
|
||||
|
||||
1. **Gateway** — fronts all surfaces (dashboard + every per-agent UI)
|
||||
on one origin. An nginx nixos-container proxies per-agent UIs under
|
||||
`/agent/<name>/`, which is what lets each agent page's inbox panel
|
||||
POST `mark-all-read` to the core dashboard's
|
||||
`/api/agent/{name}/mark-all-read` go same-origin instead of needing
|
||||
a cross-origin CORS shim. Pure ergonomics — no behavioural risk on
|
||||
its own.
|
||||
1. **Gateway** — fronts all surfaces (dashboard + every per-agent web
|
||||
server) on one origin. An nginx nixos-container proxies the per-agent
|
||||
servers under `/agent/<name>/`, so the dashboard's links to them go
|
||||
same-origin instead of needing a cross-origin CORS shim. Pure
|
||||
ergonomics — no behavioural risk on its own.
|
||||
2. **Network isolation** — the load-bearing layer: every agent
|
||||
container runs in a private netns behind the hive bridge, always
|
||||
on and unconditional. This is what turns the operator/agent split
|
||||
|
|
|
|||
Loading…
Reference in a new issue