| name | railway-volume-to-docker |
| description | Sync runtime data from a Railway deployment into local Docker for realistic testing. Use when the user asks to copy Railway data, clone production state locally, or test with real usage/session/config data. |
Railway Volume To Docker
Copy a Railway service's /data volume into local Docker (openclaw-railway-template) so local testing uses real runtime data.
When to use
- User asks to test locally with "real data"
- User asks to sync Railway deployment data into Docker
- User asks to copy production usage/session/config state to local
Preconditions
- Railway CLI is installed and logged in.
- Local repo
~/Projects/openclaw-railway-template exists.
- Service uses
/data as persistent root (ALPHACLAW_ROOT_DIR=/data).
- User accepts that secrets/tokens may be copied locally.
Safety notes
- This process can copy sensitive data (
/data/.env, sessions, logs).
- Never commit snapshot files.
- Prefer local secure machine only.
- Remove snapshot artifacts after restore.
Workflow
Run these commands from ~/Projects/openclaw-railway-template.
1) Confirm Railway target
railway status
Expected output should show project/environment/service linked to the intended deployment.
2) Verify remote volume path exists
railway ssh -- sh -lc "pwd && ls -la /data"
If /data is missing, stop and confirm service/container setup.
3) Build a remote snapshot archive