Back
App Hosting // Deploying
Deploying
Docs › App Hosting
Deploying
Every deploy is checked the way Make Live checks it, and goes live only if the app starts and answers.
The Deploy menu
Deploy latest commitThe newest commit on your GitHub branch. Without a linked repository: Deploy latest version, your NOVA project as it is now.
Deploy a specific commitPick one from the branch's recent commits.
Roll back to thisPut an earlier deploy back live, exactly as it was.
RestartStart the live app again as it is: no new build, no new code. Use it after changing environment variables.
Deploying a commit puts that commit's files in your NOVA project. What was there before stays in Version History, so nothing is lost.
Auto-deploy
Turn on Deploy automatically on every push in Build and deploy, and choose the branch (main if you leave it empty).
From GitHubNOVA looks at the branch every two minutes and deploys a new commit. The repository must be linked by the project's owner.
From NOVA CLIA nova push to that branch deploys straight away.
First switch-onTurning it on only notes where the branch is. The next new commit deploys.
What happens in a deploy
- 1NOVA installs, builds and starts the new version beside the one that is live.
- 2It waits for the app to answer at its health check path (or
/). A build or start that fails is refused, the live version keeps running, and you are told why by email. - 3When the new version answers, it takes over and the old one is stopped. Visitors never see a gap.
Build and start commands, root folder, health check path and port are kept with each deploy, so an app that wakes up or is rolled back starts exactly as it was deployed. A changed setting applies from the next deploy.
Join our Discord
Chat with our engineers and become part of the active NOVA developer community.
Need help?
Open an issue on GitHub or email support@bridgeye.com.