summaryrefslogtreecommitdiff
path: root/docs/catalog.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/catalog.md')
-rw-r--r--docs/catalog.md25
1 files changed, 21 insertions, 4 deletions
diff --git a/docs/catalog.md b/docs/catalog.md
index cd6eec9..24b6fb9 100644
--- a/docs/catalog.md
+++ b/docs/catalog.md
@@ -39,7 +39,15 @@ but its Cloudflare poke API is not reproduced locally.
## Builds and watch
-The dashboard has Build, Watch, Cancel, and Log controls. Builds execute in the
+The regular 9web interface has **files**, **sites**, and **services** views in
+catalogue mode. They share the existing header, stylesheet, tables and file
+browser. The root opens files; `/?view=sites` and `/?view=services` are direct
+links to the other tabs. Browser history and reload preserve the selected view.
+Switching tabs preserves unsaved file edits. Ordinary upstream mode shows only
+files and does not poll the catalogue API.
+
+The sites table has build, watch and cancel controls, plus files and log links
+that open the same file browser. Builds execute in the
configured working directory with the service's environment. One child job runs
per site. Repeated build requests during a build coalesce into one later build.
Build writes enqueue work immediately; serving does not wait for compilation.
@@ -101,9 +109,11 @@ durable history of every transition. 9P flush cancels parked reads. State events
also work through `/fs/sites/<name>/events?follow=1` as SSE. `status` is the finite
snapshot to use for ordinary polling.
-The dashboard reads `GET /_cloud9/catalog.json` and uses
-`POST /_cloud9/sites/<name>/ctl` with a plain-text command. The existing
-`PUT /fs/sites/<name>/ctl` also reaches the same control implementation.
+The sites and services views read `GET /_cloud9/catalog.json` while visible.
+Build controls use `PUT /fs/sites/<name>/ctl`, through the same HTTP-to-9P mapping
+as file editing. The earlier `POST /_cloud9/sites/<name>/ctl` endpoint remains
+compatible for existing clients. Logs use the normal file viewer rather than a
+separate dialog. Polling preserves site-row focus and pauses in background tabs.
## Passive discovery
@@ -156,6 +166,7 @@ registry, which should remain writable only by its owner.
```
zig build catalog-test http-fs-test mux-test -Doptimize=ReleaseSafe
+zig build catalog-ui-test -Doptimize=ReleaseSafe
```
The catalogue integration test uses temporary real sites and processes. It checks
@@ -165,6 +176,12 @@ build status, process-group cancellation, nonblocking event readers, and actual
socket ownership discovery. Existing gateway HTTP/filesystem and mux suites cover
the original mode.
+The Chromium UI test checks the shared shell and styles, view navigation and
+history, direct tab links, builds through `/fs`, logs in the file browser,
+preservation of unsaved edits and focused controls, and mobile layout. It writes
+inspection screenshots to `.zig-cache/catalog-ui/`. It uses the installed
+`google-chrome-stable` binary (or `CLOUD9_CHROME`), with no npm dependencies.
+
## Installed workstation configuration
The initial workstation setup uses dashboard port 8090 and site ports 8091–8095: