@ours.network/cowork 0.3.6 → 0.4.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/mufl_code/BBAE58CF78DEE59692F456EAFFA9A6109835B66846FC3989F6D201B8F4523A55.muflo
CHANGED
|
Binary file
|
package/docs/11-web-console.md
CHANGED
|
@@ -10,6 +10,17 @@ The command safely starts the daemon only when it is absent, waits for `GET /` r
|
|
|
10
10
|
|
|
11
11
|
The console and HTTP room RPC have no authentication. They bind only to `127.0.0.1`; both the `127.0.0.1` and `localhost` browser URLs are accepted. Do not use port forwarding, a reverse proxy, or another mechanism to expose this listener to other hosts.
|
|
12
12
|
|
|
13
|
+
## API description
|
|
14
|
+
|
|
15
|
+
The same loopback listener serves an OpenAPI 3.1 description of the room management REST API and a browser UI for it:
|
|
16
|
+
|
|
17
|
+
- `http://127.0.0.1:3052/openapi.json` — the machine-readable document.
|
|
18
|
+
- `http://127.0.0.1:3052/docs` — the UI that renders the document and can send requests.
|
|
19
|
+
|
|
20
|
+
Both are read-only GET routes with no authentication, exactly like the console itself, and they are available whenever `rest.enabled` is true. They ship inside the daemon and load no remote assets, so they work on an offline host. Do not expose either route to another host.
|
|
21
|
+
|
|
22
|
+
Every room operation is carried by the single route `POST /rpc` with the envelope `{ "version": 1, "id": ..., "method": ..., "params": ... }`; the document describes the seventeen methods the REST listener serves, discriminated on `method`. Operations that carry an invite secret are not part of it — they are reachable only over `management.sock`.
|
|
23
|
+
|
|
13
24
|
## Room setup
|
|
14
25
|
|
|
15
26
|
1. Choose Create room and enter the friendly Name, Goal, and Briefing. The name is shown in the room list, workspace header, and room details.
|