Deploying
Git-push deploys
Automatic deployments from your GitHub repository
How it works
When you connect a GitHub repository to Zanode, we automatically deploy your app whenever you push to your configured branch.
Private repositories require either GitHub OAuth access or a GitHub App installation.
Automatic deploys
By default, every push to your main branch triggers a production deployment. The watched branch is configurable in Settings → Git Configuration.
Push your code
git add .
git commit -m "New feature"
git push origin main Build starts automatically
Zanode receives a webhook from GitHub and starts building your app.
Deploy completes
Once the build succeeds, your app is live within seconds.
Preview deployments (coming soon)
Preview deployments for pull requests are on our roadmap and coming soon.
Once available, pushing to any non-main branch will create a preview deployment with a unique URL like:
feature-new-header--your-project.zano.click
Manual redeploys
You can trigger a redeploy from the dashboard:
- Go to your project
- Click deploy in the project header
This is useful when:
- Environment variables have changed
- You want to rebuild without pushing code
Build logs
View real-time build logs in your dashboard:
- Go to your project → Deployments tab
- Click on any deployment row to expand it and stream the build log
Logs include:
- Dependency installation (
npm install) - Build output (
npm run build) - Deployment status and errors
Sensitive tokens (e.g. GitHub access tokens) are automatically redacted from build logs.