From 1493ea4ce6afdc3bee3b640e05815a0631fa211f Mon Sep 17 00:00:00 2001 From: Andrew Altshuler Date: Tue, 16 Jun 2026 11:43:45 +0300 Subject: [PATCH] docs(readme): widen --server to ; show --as on cluster apply (#264) 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 ``), and `cluster apply` should show `--as ` so the control-plane action's attribution is explicit. Co-authored-by: Claude Opus 4.8 --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index b7b7ae0..bee0fa5 100644 --- a/README.md +++ b/README.md @@ -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 ` (+ `--graph `), and `query`/`mutate` invoke -a stored query from the catalog **by name**. +addressed with `--server ` (+ `--graph `), 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