Deploy and Host Rustpad Persistent on Railway

Run Rustpad, a lightweight collaborative editor, with SQLite-backed persistence on a Railway volume.

About Hosting Rustpad Persistent on Railway

• rustpad: public collaborative editor service
• Persistent /data volume
• SQLite database stored at /data/rustpad.sqlite3
• Railway public domain and single-service deployment

Why Deploy Rustpad Persistent on Railway

The published template deploy test created rustpad, reached SUCCESS, served HTTP 200, accepted a WebSocket edit, and still had that edit in history after a rustpad restart.

This is intentionally small: one app service, one volume, one public URL.

Common Use Cases

• Temporary team notes
• Lightweight collaborative scratchpads
• Internal writing rooms
• Small workshops or classrooms
• Rustpad evaluation environments

Dependencies for Rustpad Persistent Hosting

Rustpad does not need an external database. SQLite persistence is enabled through SQLITE_URI, and Railway provides the backing volume.

Deployment Dependencies

• PORT: internal HTTP port, set to 3030
• SQLITE_URI: SQLite file path, set to sqlite:///data/rustpad.sqlite3
• EXPIRY_DAYS: inactive document retention window

After Deploy

1. Open the Rustpad public URL.
2. Create a pad and make a test edit.
3. Restart the service if you want to confirm persistence.

Support Checklist

If a deploy fails, include the rustpad deployment ID, public URL response, and any logs mentioning SQLite or /data.