Deployment
Railway
Deploy Repix to Railway with automatic Dockerfile detection.
Railway automatically detects and uses the Dockerfile at the root of your repository.
Quick Deploy (Template)
Use the ready-to-deploy template for a one-click setup:
The template uses the official Docker image. After deployment, generate a domain under Settings → Networking → Generate Domain.
Prefer the template for the fastest path to production. Use the manual steps below if you need to deploy from your own GitHub fork or customize the build.
Deploy Steps (Manual)
1. Create a Project
- Go to Railway Dashboard
- Click New Project
- Select Deploy from GitHub repo
- Connect and choose the
repixrepository
2. Configure Service
Railway detects the Dockerfile and builds your image. No extra build config needed.
3. Environment Variables
Add variables in Variables tab:
| Variable | Value |
|---|---|
NODE_ENV | production |
PORT | 3210 |
SOURCE_PREFIX | https:// |
4. Expose Port
- Go to Settings → Networking
- Click Generate Domain to get a public URL
Your Repix instance will be at:
https://repix-production-xxxx.up.railway.app
Railway sets
PORT automatically. The Dockerfile exposes 3210; Railway maps it correctly.Custom Domain
- Settings → Networking → Custom Domain
- Add your domain (e.g.,
images.yourdomain.com) - Update DNS with the CNAME record Railway provides
Scaling
Railway supports horizontal scaling. To run multiple instances:
- Settings → Replicas — Increase instance count
- Use Railway's load balancer for distribution
Troubleshooting
"Stopping Container" right after startup
- Set health check path – In Settings → Health Check, set the path to
/health(path only, not full URL). Railway waits for this to return 200 before marking the deploy live. - Do not set
PORT– RemovePORTfrom Variables; Railway injects it (e.g. 8080). - Generate domain – Settings → Networking → Generate Domain so the service is routable.
Dockerfile Path
If using a non-standard path, set:
RAILWAY_DOCKERFILE_PATH=/path/to/Dockerfile