From 121033f9daab96501883d0ba8901539cfa970df2 Mon Sep 17 00:00:00 2001 From: Taksh Kothari Date: Sat, 25 Jul 2026 07:40:48 +0530 Subject: [PATCH] docs: point readme at deploy compose bundle (#2363) ## Summary - production Compose already lives under `deploy/compose/`; root README only described the local-dev stack - add a one-liner so VPS / single-node setups find the right bundle (follow-up to #2323) ## Test plan - [ ] README Quick start links to `deploy/compose/README.md` and clarifies root `docker-compose.yml` is for local dev Made with [Cursor](https://cursor.com) Signed-off-by: Taksh --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 6aa3eeff0..89a131e73 100644 --- a/README.md +++ b/README.md @@ -154,6 +154,8 @@ Relay on `ws://localhost:3000`. Desktop app pops up. You're in. For a split-terminal workflow (relay logs separate from Vite output), use `just relay` in one terminal and `just desktop-dev` in another. +Want a single-node / VPS relay instead of the local-dev stack? Use the production Compose bundle in [`deploy/compose/`](deploy/compose/README.md) (`docker compose` + Postgres, Redis, MinIO, optional Caddy/TLS). The root [`docker-compose.yml`](docker-compose.yml) is for day-to-day development only. + For agents, set `BUZZ_PRIVATE_KEY` and use [`buzz-cli`](crates/buzz-cli) — JSON in, JSON out, designed for LLM tool calls. ---