Railway provisions a libredesk service alongside managed PostgreSQL and Redis from a single template. The database schema installs automatically on first deploy.
Deploy
Click Deploy on Railway
Sign in to Railway, then set LIBREDESK_SYSTEM_USER_PASSWORD in the deploy form. It must be at least 10 characters with uppercase, lowercase, numeric, and special characters (e.g. MyPassword@123).
Wait for the build
Railway provisions PostgreSQL, Redis, and the libredesk app, and assigns a *.up.railway.app domain to the libredesk service. The schema installs automatically on first boot.
Log in
Visit the assigned domain and sign in with:
- Email:
System - Password: the password from step 1
Configuration
To override any libredesk setting, add an environment variable under the libredesk service's Variables tab. All variables use the LIBREDESK_ prefix with double underscores (__) for nested keys.
| Setting | Environment variable |
|---|---|
| Max attachment / request body size (bytes) | LIBREDESK_APP__SERVER__MAX_BODY_SIZE |
| Session lifetime | LIBREDESK_APP__SERVER__SESSION_LIFETIME |
Log level (debug, info, warn, error) |
LIBREDESK_APP__LOG_LEVEL |
See the full configuration reference for the complete list.
Warning:
Don't change the auto-injected database and Redis variables. Railway manages those references.
Updating libredesk
Redeploy the libredesk service from the Railway dashboard. It pulls the latest image and runs any pending migrations on startup.