From f165145b63f8380de38e30d0bb52453df2189c5b Mon Sep 17 00:00:00 2001 From: aaltshuler Date: Wed, 10 Jun 2026 22:54:26 +0300 Subject: [PATCH] =?UTF-8?q?docs(deploy):=20address=20review=20=E2=80=94=20?= =?UTF-8?q?consistent=20placeholders,=20complete=20ECS=20command?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The ECS day-2 apply gains its required --config flag (the image ships no omnigraph.yaml, so the CLI cannot locate the cluster dir without it), and the docker-exec example uses the placeholder convention instead of a real-looking actor name. Co-Authored-By: Claude Fable 5 --- docs/user/deployment.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/user/deployment.md b/docs/user/deployment.md index eb181e3..563a501 100644 --- a/docs/user/deployment.md +++ b/docs/user/deployment.md @@ -67,7 +67,7 @@ so the day-2 loop runs in-container with no `omnigraph.yaml`: ```bash docker exec -it sh -c \ - 'omnigraph cluster apply --as andrew --config /var/lib/omnigraph/cluster' + 'omnigraph cluster apply --as --config /var/lib/omnigraph/cluster' # then restart the container to pick up the applied state ``` @@ -81,7 +81,8 @@ docker exec -it sh -c \ (or the `--features aws` build's native Secrets Manager source). 4. ALB in front for TLS; target the container's 8080 with `/healthz` checks. 5. Day-2: ECS exec into the task → edit/upload config on the volume → - `omnigraph cluster apply --as ` → force a new deployment (restart). + `omnigraph cluster apply --as --config /var/lib/omnigraph/cluster` + → force a new deployment (restart). For a deployment that doesn't need the cluster control plane, the classic stateless shape — `OMNIGRAPH_TARGET_URI=s3://bucket/graph.omni`, no volume —