mirror of https://github.com/openclaw/openclaw.git
88 lines
2.5 KiB
Plaintext
88 lines
2.5 KiB
Plaintext
---
|
|
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 Control UI
|
|
title: "Railway"
|
|
---
|
|
|
|
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 `OPENCLAW_GATEWAY_PORT` and `OPENCLAW_GATEWAY_TOKEN`).
|
|
4. Enable **HTTP Proxy** on port `8080`.
|
|
5. Open `https://<your-railway-domain>/openclaw` and connect using your `OPENCLAW_GATEWAY_TOKEN`.
|
|
|
|
## One-click deploy
|
|
|
|
<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.
|
|
|
|
Then open:
|
|
|
|
- `https://<your-railway-domain>/openclaw` — Control UI
|
|
|
|
## What you get
|
|
|
|
- Hosted OpenClaw Gateway + Control UI
|
|
- Persistent storage via Railway Volume (`/data`) so config/credentials/workspace survive redeploys
|
|
|
|
## Required Railway settings
|
|
|
|
### Public Networking
|
|
|
|
Enable **HTTP Proxy** for the service.
|
|
|
|
- Port: `8080`
|
|
|
|
### Volume (required)
|
|
|
|
Attach a volume mounted at:
|
|
|
|
- `/data`
|
|
|
|
### Variables
|
|
|
|
Set these variables on the service:
|
|
|
|
- `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)
|
|
|
|
## Connect a channel
|
|
|
|
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)
|
|
- [All channels](/channels)
|
|
|
|
## Backups & migration
|
|
|
|
Export your configuration and workspace:
|
|
|
|
```bash
|
|
openclaw backup create
|
|
```
|
|
|
|
This creates a portable backup archive you can restore on any OpenClaw host. See [Backup](/cli/backup) for details.
|
|
|
|
## Next steps
|
|
|
|
- Set up messaging channels: [Channels](/channels)
|
|
- Configure the Gateway: [Gateway configuration](/gateway/configuration)
|
|
- Keep OpenClaw up to date: [Updating](/install/updating)
|