Deployment lifecycle
Deployment is waiting in the build queue. CupaDev processes up to 3 builds concurrently.
CupaDev is cloning your repo, installing dependencies, running your build command, and packaging the Docker image.
The Docker image is pushed to the registry and the Kubernetes deployment is being updated.
Your app is live and accepting traffic.
The build or deployment failed. Check Build Logs or Pod Logs for details.
Build configuration
CupaDev auto-detects your framework and sets sensible defaults. You can override any setting in project settings.
| Setting | Default (Next.js) | Default (Node.js) |
|---|---|---|
| Install command | npm install --legacy-peer-deps | npm install --legacy-peer-deps |
| Build command | npm run build | (none — skip) |
| Output directory | .next | Source directory |
| Node version | 20 (Alpine) | 20 (Alpine) |
| PORT | 3000 (auto-injected) | 3000 (auto-injected) |
Reading logs
Go to Project → Logs tab to access all log types:
Pod Logs
Container stdout/stderr in real time. This is where startup errors, uncaught exceptions, and runtime crashes appear. Refreshes every 10 seconds.
Build Logs
Full output of the build process: npm install, build command, Docker build. Check here for compile errors and missing dependencies.
Runtime Logs
HTTP request logs (method, path, status code, response time). Useful for debugging 404s, 500s, and slow requests.
All Logs
Combined view of build + runtime logs for a quick overview.
Redeploy & Rollback
Manual redeploy
From Project → Overview → Deployments, click the Redeploy button on any deployment to rebuild and redeploy from the same commit.
After adding env vars
When you add or edit environment variables, CupaDev prompts you to redeploy. This is required for the new values to take effect — running containers are not automatically updated.
Rollback
Go to Project → Versions tab and click Redeploy on any previous deployment to instantly roll back to a known-good version.
Auto-deploy from GitHub
CupaDev registers a webhook on your GitHub repo when you first import a project. Every push to the configured production branch (main by default) triggers a new deployment.
Setup requirements
- GitHub repository must be accessible by your connected account
- Webhook is registered automatically — no manual setup needed
- Only pushes to the production branch trigger deployments (not all branches)
Cron Jobs
Schedule recurring HTTP calls to your application from Project → Cron Jobs tab. CupaDev will call a URL on your app at the configured interval.
Deployment failed?
Check the Build Logs and Pod Logs tabs in your project. For a full list of common errors and their fixes:
View Error Codes & Troubleshooting →