How Deployments Work
Understand what happens when you deploy an app on Zynnode.
Every time you deploy through Zynnode — whether it's your first deployment or an automatic redeploy triggered by a push — the same process runs behind the scenes. This page explains what happens at each stage.
The Deployment Pipeline
When a deployment starts, Zynnode runs through these stages in order:
- Clone — Zynnode pulls the latest code from your GitHub repository and the branch you selected.
- Install — Dependencies are installed using the package manager detected in your project (npm, yarn, or pnpm).
- Build — Your build command runs (e.g.,
npm run build), producing the output files. - Deploy — The built output is sent to the cloud provider and deployment target you configured (e.g., Cloudflare Pages, AWS S3, GCP Cloud Run).
You can watch each stage in real-time through the build logs on the deployment detail page.
Deployment Statuses
Every deployment has a status that tells you where it is in the pipeline:
| Status | What It Means |
|---|---|
| Pending | The deployment is queued and will start shortly. |
| Building | Zynnode is installing dependencies and running your build command. |
| Success | Everything worked. Your app is live at the deployment URL. |
| Failed | Something went wrong during the build or deploy stage. Check the logs for details. |
Viewing Build Logs
- Go to your project in the Zynnode dashboard.
- Click on any deployment in the list to open the deployment detail page.
- Build logs stream in real-time while the deployment is running. Once complete, the full log is available to review.
If a deployment fails, an error banner appears at the top of the page with the error message. The full details are in the log output below.
Automatic Deployments
Once your project is connected to GitHub, every push to your default branch triggers a new deployment automatically. You don't need to visit the dashboard — Zynnode detects the push via a GitHub webhook and starts the build.
Redeploying
To redeploy without pushing new code, open any previous deployment and click the Redeploy button. This re-runs the full pipeline using the same commit.
Viewing All Deployments
The Deployments page in the dashboard sidebar shows all deployments across all your projects. You can:
- Filter by project, environment (production or preview), or status (success, failed, building).
- Search by deployment ID, branch name, or commit message.
- Export the deployment list to CSV for your records.
Build Settings
You can review and change build settings from your project page:
- Build Command — The command that builds your app (e.g.,
npm run build). - Output Directory — Where the build output lives (e.g.,
.next,dist,build). - Framework — Auto-detected. Affects default build settings.
- Branch — The branch Zynnode builds from.
Changing build settings does not trigger a new deployment. Push a commit or use the Redeploy button to apply your changes.
Deployment Targets by Provider
The deployment target you chose during project setup determines where your built app runs. Here's a quick reference:
| Target | Provider | Best For |
|---|---|---|
| S3 + CloudFront | AWS | Static sites, single-page apps |
| EC2 | AWS | Full-stack apps, APIs |
| ECS (Fargate) | AWS | Containerized apps with auto-scaling |
| Lambda | AWS | Serverless functions |
| Cloudflare Pages | Cloudflare | Static and JAMstack sites on the edge |
| Azure VM | Azure | Full-stack apps, APIs |
| Cloud Run | GCP | Containerized apps |
| App Engine | GCP | Managed full-stack apps |
| Compute Engine | GCP | Full-stack apps on a VM |
For step-by-step guides on deploying to each provider, see:
Deploy to AWS
S3, EC2, ECS, and Lambda deployments.
Deploy to Cloudflare
Cloudflare Pages deployments.
Deploy to Azure
Azure VM deployments.
Deploy to GCP
Cloud Run, App Engine, and Compute Engine deployments.