mirror of
https://github.com/openclaw/openclaw.git
synced 2026-02-19 18:39:20 -05:00
c18452598a
* docs: restructure Get Started tab and improve onboarding flow - Flatten nested Onboarding group into linear First Steps flow - Add 'What is OpenClaw?' narrative section to landing page - Split wizard.md into streamlined overview + full reference (reference/wizard.md) - Move Pairing to Channels > Configuration - Move Bootstrapping to Agents > Fundamentals - Move macOS app onboarding to Platforms > macOS companion app - Move Lore to Help > Community - Remove duplicate install instructions from openclaw.md - Mirror navigation changes in zh-CN tabs - No content deleted — all detail preserved or relocated * docs: move deployment pages to install/, fix Platforms tab routing, clarify onboarding paths - Move deployment guides (fly, hetzner, gcp, macos-vm, exe-dev, railway, render, northflank) from platforms/ and root to install/ - Add 'Hosting and deployment' group to Install tab - Slim Gateway & Ops 'Remote access and deployment' down to 'Remote access' - Swap Platforms tab before Gateway & Ops to fix path-prefix routing - Move macOS app onboarding into First steps (parallel to CLI wizard) - Rename sidebar titles to 'Onboarding: CLI' / 'Onboarding: macOS App' - Add redirects for all moved paths - Update all internal links (en + zh-CN) - Fix img tag syntax in onboarding.md
54 lines
2.0 KiB
Plaintext
54 lines
2.0 KiB
Plaintext
---
|
||
title: Deploy on 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.
|
||
|
||
## 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.
|
||
3. Click **Deploy OpenClaw now**.
|
||
4. Set the required environment variable: `SETUP_PASSWORD`.
|
||
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`.
|
||
|
||
## What you get
|
||
|
||
- Hosted OpenClaw Gateway + Control UI
|
||
- Web setup wizard at `/setup` (no terminal commands)
|
||
- Persistent storage via Northflank Volume (`/data`) so config/credentials/workspace survive redeploys
|
||
|
||
## Setup flow
|
||
|
||
1. Visit `https://<your-northflank-domain>/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://<your-northflank-domain>/openclaw`
|
||
|
||
If Telegram DMs are set to pairing, the setup wizard can approve the pairing code.
|
||
|
||
## Getting chat tokens
|
||
|
||
### Telegram bot token
|
||
|
||
1. Message `@BotFather` in Telegram
|
||
2. Run `/newbot`
|
||
3. Copy the token (looks like `123456789:AA...`)
|
||
4. Paste it into `/setup`
|
||
|
||
### Discord bot token
|
||
|
||
1. Go to https://discord.com/developers/applications
|
||
2. **New Application** → choose a name
|
||
3. **Bot** → **Add Bot**
|
||
4. **Enable MESSAGE CONTENT INTENT** under Bot → Privileged Gateway Intents (required or the bot will crash on startup)
|
||
5. Copy the **Bot Token** and paste into `/setup`
|
||
6. Invite the bot to your server (OAuth2 URL Generator; scopes: `bot`, `applications.commands`)
|