diff --git a/docs/install/northflank.mdx b/docs/install/northflank.mdx index 18ca33345af..310759142ca 100644 --- a/docs/install/northflank.mdx +++ b/docs/install/northflank.mdx @@ -2,46 +2,32 @@ summary: "Deploy OpenClaw on Northflank with one-click template" read_when: - Deploying OpenClaw to Northflank - - You want a one-click cloud deploy with browser-based setup + - You want a one-click cloud deploy with browser-based Control UI title: "Northflank" --- -Deploy OpenClaw on Northflank with a one-click template and finish setup in your browser. -This is the easiest “no terminal on the server” path: Northflank runs the Gateway for you, -and you configure everything via the `/setup` web wizard. +Deploy OpenClaw on Northflank with a one-click template and access it through the web Control UI. +This is the easiest "no terminal on the server" path: Northflank runs the Gateway for you. ## How to get started 1. Click [Deploy OpenClaw](https://northflank.com/stacks/deploy-openclaw) to open the template. -2. Create an [account on Northflank](https://app.northflank.com/signup) if you don’t already have one. +2. Create an [account on Northflank](https://app.northflank.com/signup) if you don't already have one. 3. Click **Deploy OpenClaw now**. -4. Set the required environment variable: `SETUP_PASSWORD`. +4. Set the required environment variable: `OPENCLAW_GATEWAY_TOKEN` (use a strong random value). 5. Click **Deploy stack** to build and run the OpenClaw template. 6. Wait for the deployment to complete, then click **View resources**. 7. Open the OpenClaw service. -8. Open the public OpenClaw URL and complete setup at `/setup`. -9. Open the Control UI at `/openclaw`. +8. Open the public OpenClaw URL at `/openclaw` and connect using your `OPENCLAW_GATEWAY_TOKEN`. ## What you get - Hosted OpenClaw Gateway + Control UI -- Web setup at `/setup` (no terminal commands) - Persistent storage via Northflank Volume (`/data`) so config/credentials/workspace survive redeploys -## Setup flow - -1. Visit `https:///setup` and enter your `SETUP_PASSWORD`. -2. Choose a model/auth provider and paste your key. -3. (Optional) Add Telegram/Discord/Slack tokens. -4. Click **Run setup**. -5. Open the Control UI at `https:///openclaw` - -If Telegram DMs are set to pairing, web setup can approve the pairing code. - ## Connect a channel -Paste your Telegram or Discord token into the `/setup` wizard. For setup -instructions, see the channel docs: +Use the Control UI at `/openclaw` or run `openclaw onboard` via SSH for channel setup instructions: - [Telegram](/channels/telegram) (fastest — just a bot token) - [Discord](/channels/discord) diff --git a/docs/install/railway.mdx b/docs/install/railway.mdx index fa1b4d8c089..315bf334b70 100644 --- a/docs/install/railway.mdx +++ b/docs/install/railway.mdx @@ -2,21 +2,20 @@ summary: "Deploy OpenClaw on Railway with one-click template" read_when: - Deploying OpenClaw to Railway - - You want a one-click cloud deploy with browser-based setup + - You want a one-click cloud deploy with browser-based Control UI title: "Railway" --- -Deploy OpenClaw on Railway with a one-click template and finish setup in your browser. -This is the easiest “no terminal on the server” path: Railway runs the Gateway for you, -and you configure everything via the `/setup` web wizard. +Deploy OpenClaw on Railway with a one-click template and access it through the web Control UI. +This is the easiest "no terminal on the server" path: Railway runs the Gateway for you. ## Quick checklist (new users) 1. Click **Deploy on Railway** (below). 2. Add a **Volume** mounted at `/data`. -3. Set the required **Variables** (at least `SETUP_PASSWORD`). +3. Set the required **Variables** (at least `OPENCLAW_GATEWAY_PORT` and `OPENCLAW_GATEWAY_TOKEN`). 4. Enable **HTTP Proxy** on port `8080`. -5. Open `https:///setup` and finish the wizard. +5. Open `https:///openclaw` and connect using your `OPENCLAW_GATEWAY_TOKEN`. ## One-click deploy @@ -33,15 +32,12 @@ Railway will either: Then open: -- `https:///setup` — web setup (password protected) - `https:///openclaw` — Control UI ## What you get - Hosted OpenClaw Gateway + Control UI -- Web setup at `/setup` (no terminal commands) - Persistent storage via Railway Volume (`/data`) so config/credentials/workspace survive redeploys -- Backup export at `/setup/export` to migrate off Railway later ## Required Railway settings @@ -61,25 +57,14 @@ Attach a volume mounted at: Set these variables on the service: -- `SETUP_PASSWORD` (required) -- `PORT=8080` (required — must match the port in Public Networking) +- `OPENCLAW_GATEWAY_PORT=8080` (required — must match the port in Public Networking) +- `OPENCLAW_GATEWAY_TOKEN` (required; treat as an admin secret) - `OPENCLAW_STATE_DIR=/data/.openclaw` (recommended) - `OPENCLAW_WORKSPACE_DIR=/data/workspace` (recommended) -- `OPENCLAW_GATEWAY_TOKEN` (recommended; treat as an admin secret) - -## Setup flow - -1. Visit `https:///setup` and enter your `SETUP_PASSWORD`. -2. Choose a model/auth provider and paste your key. -3. (Optional) Add Telegram/Discord/Slack tokens. -4. Click **Run setup**. - -If Telegram DMs are set to pairing, web setup can approve the pairing code. ## Connect a channel -Paste your Telegram or Discord token into the `/setup` wizard. For setup -instructions, see the channel docs: +Use the Control UI at `/openclaw` or run `openclaw onboard` via Railway's shell for channel setup instructions: - [Telegram](/channels/telegram) (fastest — just a bot token) - [Discord](/channels/discord) @@ -87,11 +72,13 @@ instructions, see the channel docs: ## Backups & migration -Download a backup at: +Export your configuration and workspace: -- `https:///setup/export` +```bash +openclaw backup create +``` -This exports your OpenClaw state + workspace so you can migrate to another host without losing config or memory. +This creates a portable backup archive you can restore on any OpenClaw host. See [Backup](/cli/backup) for details. ## Next steps