From 446121efd3a5cd57ea68da63556161e11234ba91 Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Tue, 21 Apr 2026 18:35:09 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@dcf131e54c611297329354eebc60a5e4acae8869 --- .openclaw-sync/source.json | 4 ++-- docs/gateway/multiple-gateways.md | 39 +++++++++++++++++++++++++++++++ 2 files changed, 41 insertions(+), 2 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index cd5992b41..000abda42 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "b2b43085bcb2c0a3262f7207b5d6020ae7efca04", - "syncedAt": "2026-04-21T18:04:46.605Z" + "sha": "dcf131e54c611297329354eebc60a5e4acae8869", + "syncedAt": "2026-04-21T18:35:08.909Z" } diff --git a/docs/gateway/multiple-gateways.md b/docs/gateway/multiple-gateways.md index 04ab0f68c..c0fdde04b 100644 --- a/docs/gateway/multiple-gateways.md +++ b/docs/gateway/multiple-gateways.md @@ -77,6 +77,45 @@ In practice, that means the rescue bot gets its own: The prompts are otherwise the same as normal onboarding. +## General Multi-Gateway Setup + +The rescue-bot layout above is the easiest default, but the same isolation +pattern works for any pair or group of Gateways on one host. + +For a more general setup, give each extra Gateway its own named profile and its +own base port: + +```bash +# main (default profile) +openclaw setup +openclaw gateway --port 18789 + +# extra gateway +openclaw --profile ops setup +openclaw --profile ops gateway --port 19789 +``` + +If you want both Gateways to use named profiles, that also works: + +```bash +openclaw --profile main setup +openclaw --profile main gateway --port 18789 + +openclaw --profile ops setup +openclaw --profile ops gateway --port 19789 +``` + +Services follow the same pattern: + +```bash +openclaw gateway install +openclaw --profile ops gateway install --port 19789 +``` + +Use the rescue-bot quickstart when you want a fallback operator lane. Use the +general profile pattern when you want multiple long-lived Gateways for +different channels, tenants, workspaces, or operational roles. + ## Isolation Checklist Keep these unique per Gateway instance: