Learn how CupaDev handles deployments, from automatic Git integration to preview environments and production rollbacks.
Every push to your Git repository triggers an automatic deployment. No manual intervention required.
Every commit pushed to your repository is automatically built and deployed. You'll receive a unique URL for each deployment.
Production branch (usually main or master) goes to your production domain. All other branches create preview deployments with unique URLs.
Every deployment goes through these stages:
Deployment is waiting for available build resources
Installing dependencies and running build command
Uploading build output to edge network
Deployment is live and accessible via URL
Build failed - check logs for details
If something goes wrong, you can instantly rollback to any previous deployment.
Note: Rollbacks are instant because the old deployment files are still available on our edge network. No rebuild required.
Configure different settings for production and preview deployments.
| Setting | Production | Preview |
|---|---|---|
| Environment Variables | Production values | Preview/Development values |
| Domain | Custom domain | cupadev.app subdomain |
| Analytics | Full tracking enabled | Optional tracking |
| Caching | Aggressive caching | Minimal caching |
Customize how your application is built and deployed.
The command that builds your application
npm run buildWhere your built files are located
.next (Next.js) or dist (Vite/React)How to install your dependencies
npm install (or yarn, pnpm)Trigger actions when deployments succeed or fail.
Configure webhooks to receive notifications about deployment events: