mirror of
https://github.com/openclaw/openclaw.git
synced 2026-07-11 15:06:07 +00:00
f7d7148cf0
Source-grounded rewrite of 529 published docs pages with per-unit information-loss verification: 1,713 factual corrections cited to src/**, generated surfaces regenerated, frontmatter titles preserved for i18n, release notes pages untouched. All docs gates green. Closes #100141
76 lines
2.6 KiB
Plaintext
76 lines
2.6 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.
|
|
|
|
## One-click deploy
|
|
|
|
<a href="https://railway.com/deploy/clawdbot-railway-template" target="_blank" rel="noreferrer">
|
|
Deploy on Railway
|
|
</a>
|
|
|
|
<Steps>
|
|
<Step title="Deploy the template">
|
|
Click **Deploy on Railway** above.
|
|
</Step>
|
|
|
|
<Step title="Add a volume">
|
|
Attach a volume mounted at `/data` (required for persistent state).
|
|
</Step>
|
|
|
|
<Step title="Set variables">
|
|
Set the required **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)
|
|
|
|
</Step>
|
|
|
|
<Step title="Enable public networking">
|
|
Under **Public Networking**, enable **HTTP Proxy** for the service on port `8080`.
|
|
</Step>
|
|
|
|
<Step title="Connect">
|
|
Find your public URL in **Railway -> your service -> Settings -> Domains** -- either a generated domain (often `https://<something>.up.railway.app`) or your attached custom domain.
|
|
|
|
Open `https://<your-railway-domain>/openclaw` and connect using the configured shared secret. The template uses `OPENCLAW_GATEWAY_TOKEN` by default; if you replace it with password auth, use that password instead.
|
|
|
|
</Step>
|
|
</Steps>
|
|
|
|
## What you get
|
|
|
|
- Hosted OpenClaw Gateway + Control UI
|
|
- Persistent storage via the Railway Volume (`/data`), so `openclaw.json`, per-agent `auth-profiles.json`, channel/provider state, sessions, and workspace survive redeploys
|
|
|
|
## Connect a channel
|
|
|
|
Use the Control UI at `/openclaw` or run `openclaw onboard` via Railway's shell for channel setup instructions:
|
|
|
|
- [Discord](/channels/discord)
|
|
- [Telegram](/channels/telegram) (fastest -- just a bot token)
|
|
- [All channels](/channels)
|
|
|
|
## Backups and migration
|
|
|
|
Export your state, config, auth profiles, and workspace:
|
|
|
|
```bash
|
|
openclaw backup create
|
|
```
|
|
|
|
This creates a portable backup archive with OpenClaw state plus any configured workspace. 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)
|