Deployment

Openship needs a Node.js runtime and persistent PostgreSQL. Each enabled shop or channel integration adds its own credential, network, webhook and operational requirements.

Build and migration warning

The current npm run build script generates the Keystone schema, deploys Prisma migrations, and builds Next.js. Use one reviewed release job for migrations rather than allowing multiple build workers to race against production.

Release checklist

1. Pin the source revision and install from the lockfile.
2. Generate the schema and run current static checks.
3. Back up the target and test migrations on a realistic disposable clone.
4. Store DATABASE_URL, SESSION_SECRET and integration credentials in the host's secret manager.
5. Apply migrations once, deploy the app, and run session/API-key ownership negatives.
6. Route a synthetic order through every enabled shop/channel pair.
7. Test duplicate delivery, timeout, retry, partial failure, cancellation, fulfillment and tracking updates.
8. Verify raw webhook signatures and replay IDs.
9. Monitor stuck orders and keep an operator reconciliation path.

Railway, Vercel, Render or other templates can create infrastructure. They do not verify database sizing, migration history, provider reachability, background work, retries, webhooks, backups or incident response. A successful deploy is not an order-routing readiness claim.