mirror of
https://github.com/farcasclaudiu/openclaw.git
synced 2026-06-28 19:01:47 +03:00
chore: Run pnpm format:fix.
This commit is contained in:
+23
-20
@@ -8,19 +8,22 @@ and you configure everything via the `/setup` web wizard.
|
||||
|
||||
## 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`).
|
||||
4) Enable **HTTP Proxy** on port `8080`.
|
||||
5) Open `https://<your-railway-domain>/setup` and finish the wizard.
|
||||
1. Click **Deploy on Railway** (below).
|
||||
2. Add a **Volume** mounted at `/data`.
|
||||
3. Set the required **Variables** (at least `SETUP_PASSWORD`).
|
||||
4. Enable **HTTP Proxy** on port `8080`.
|
||||
5. Open `https://<your-railway-domain>/setup` and finish the wizard.
|
||||
|
||||
## One-click deploy
|
||||
|
||||
<a href="https://railway.com/deploy/clawdbot-railway-template" target="_blank" rel="noreferrer">Deploy on Railway</a>
|
||||
<a href="https://railway.com/deploy/clawdbot-railway-template" target="_blank" rel="noreferrer">
|
||||
Deploy on Railway
|
||||
</a>
|
||||
|
||||
After deploy, find your public URL in **Railway → your service → Settings → Domains**.
|
||||
|
||||
Railway will either:
|
||||
|
||||
- give you a generated domain (often `https://<something>.up.railway.app`), or
|
||||
- use your custom domain if you attached one.
|
||||
|
||||
@@ -62,10 +65,10 @@ Set these variables on the service:
|
||||
|
||||
## Setup flow
|
||||
|
||||
1) Visit `https://<your-railway-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**.
|
||||
1. Visit `https://<your-railway-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**.
|
||||
|
||||
If Telegram DMs are set to pairing, the setup wizard can approve the pairing code.
|
||||
|
||||
@@ -73,19 +76,19 @@ If Telegram DMs are set to pairing, the setup wizard can approve the pairing cod
|
||||
|
||||
### Telegram bot token
|
||||
|
||||
1) Message `@BotFather` in Telegram
|
||||
2) Run `/newbot`
|
||||
3) Copy the token (looks like `123456789:AA...`)
|
||||
4) Paste it into `/setup`
|
||||
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`)
|
||||
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`)
|
||||
|
||||
## Backups & migration
|
||||
|
||||
|
||||
Reference in New Issue
Block a user