Deployment
Provision PostgreSQL, set secrets, migrate, and host Openfront Rideshare.
Requirements
- PostgreSQL you can migrate
DATABASE_URLand aSESSION_SECRETof at least 32 characters (startup throws in production otherwise)- Optional: S3-compatible storage (five
S3_*variables, active whenS3_BUCKET_NAMEis set), SMTP for password reset,STRIPE_SECRET_KEYfor rider card payments,OPENROUTER_API_KEYandOPENROUTER_MODELfor the dashboard assistant
Build and run
| Step | Command |
|---|---|
| Build | npm run build (keystone build --no-ui && next build, no migration) |
| Migrate | npm run migrate (prisma migrate deploy). Back up retained data first |
| Start | npm start |
Railway
railway.toml builds with keystone build --no-ui && next build and starts with npm run migrate && next start, because builds cannot reach internal databases. Add Postgres, set the variables, and deploy.
Vercel
The README's Deploy with Vercel button prompts for DATABASE_URL and SESSION_SECRET. Run npm run migrate against the production database as a release step.
After deploy
- Open
/dashboard/initto create the first user (Admin role). - Run onboarding or follow Set up a fleet.
- In Settings set the fleet to
active, operations mode tomanual, and rider accounts toopenorclosed. - For card payments set
STRIPE_SECRET_KEYand install the Stripe provider. See Payment providers.
Set PUBLIC_SIGNUPS_ALLOWED=true only if you want open dashboard and rider signup.