A deployment clones your code (or uses the ZIP), installs dependencies, runs the build and starts the new version next to the live one. Only when the health check path responds does traffic switch over: zero downtime. If something fails, the previous version keeps running.
Deploy on every push (webhook)
- In your app → Settings → Automatic deploys, keep the switch on and copy the Webhook URL (and the secret, if shown).
- GitHub: Settings → Webhooks → Add webhook. Payload URL: the URL; Content type: application/json; Secret: the secret; event: Just the push event.
- GitLab: Settings → Webhooks. URL and Secret token; check Push events. Bitbucket: Repository settings → Webhooks, with the URL as is and the Repository push trigger.
Only pushes to the configured branch trigger a deployment.
The history
- In Deployments you see each version with its number, commit, what triggered it (push, manual, rollback) and how long it took. View log shows the build live.
- Cancel stops a deployment in progress; the live version doesn't change.
- Roll back to this version creates a new deployment with that version's code and configuration.
- Deploy now with No cache does a fresh install (handy if you changed package manager or something got stuck).
Ask the assistant
Still have a question about this? Ask the assistant.
Was this article helpful?
Related articles
- Logs and metrics for your Node.js appWhat your app writes to the console, live, plus CPU and memory charts with your plan's limit.
- Create your first Node.js app from GitHubConnect your repository, pick the branch and we'll put your app online with HTTPS in minutes.
- Environment variables for your Node.js appAPI keys, passwords and settings your app reads from process.env, encrypted and with secret values.