apunkt/omnigraph
1
0
Fork 0
mirror of https://github.com/ModernRelay/omnigraph.git synced 2026-06-18 02:24:27 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 5

docs(readme): widen --server to <name|url>; show --as on cluster apply (#264)

Browse source 
Two accuracy nits from the #263 bot review, against the cookbook's authoritative
addressing reference: `--server` accepts a name OR a literal `http(s)://` URL
(prose had narrowed it to `<name>`), and `cluster apply` should show `--as
<actor>` so the control-plane action's attribution is explicit.

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Andrew Altshuler 2026-06-16 11:43:45 +03:00 • committed by GitHub
parent df0b0eadd1
commit 1493ea4ce6
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

8
README.md
View file

@ -82,12 +82,12 @@ A deployment is a **cluster**. A `cluster.yaml` declares its graphs, schemas,
stored queries, and policies; you converge it with `cluster apply` and serve it.
The server is cluster-first — it boots only from a cluster and serves every graph
under `/graphs/{id}/…`. Day-to-day work goes through that server: graphs are
addressed with `--server <name>` (+ `--graph <id>`), and `query`/`mutate` invoke
a stored query from the catalog **by name**.
addressed with `--server <name|url>` (+ `--graph <id>`), and `query`/`mutate`
invoke a stored query from the catalog **by name**.
```bash
# 1. Converge the declared cluster, then serve it
omnigraph cluster apply --config ./company-brain
# 1. Converge the declared cluster, then serve it (--as attributes the apply)
omnigraph cluster apply --config ./company-brain --as you
omnigraph-server --cluster ./company-brain --bind 0.0.0.0:8080
# or config-free from object storage — the bucket IS the deployment:
# omnigraph-server --cluster s3://my-bucket/company-brain --bind 0.0.0.0:8080