Waymaker Host
Deployment History
Learn about Deployment History in WaymakerOS.
DeploymentsHistory
View the full history of every deployment for your app. Each push to your connected repository triggers a new deployment, and Host keeps a record of every one.
Viewing Deployments
- Open Host and select your app
- Go to the Deployments tab
Each deployment shows:
| Field | Description |
|---|---|
| Status | Building, success, or failed |
| Commit | The git commit that triggered the deployment |
| Time | When the deployment started |
While a deployment is in progress, Host checks the status every 5 seconds and updates automatically.
Deployment Statuses
| Status | Meaning |
|---|---|
| Building | The app is being built and deployed — spinner shown |
| Queued | Waiting for a build slot |
| Success | Deployed and live |
| Failed | Build or deployment error — check your build settings |
Triggering a Deployment
Deployments are triggered by pushing to your connected GitHub repository. Every push to the configured branch starts a new build.
git push origin main
There is no manual "deploy" button — deployments are always tied to a git commit.
When a Deployment Fails
- Check the deployment status in the Deployments tab
- Review your build settings in the Settings tab:
- Is the branch correct?
- Is the build command correct? (e.g.,
npm run build) - Is the output directory correct? (e.g.,
dist,.next,build)
- Check your GitHub repository for build errors
- Fix the issue and push again — a new deployment will start automatically
Deploying a Previous Version
To go back to a previous version, revert your code in Git and push:
git revert HEAD
git push origin main
This creates a new deployment with the reverted code, keeping your full deployment history intact.
Next Steps
- Hosting Apps — creating and configuring apps
- GitHub Integration — connecting your repository
- Environment Variables — managing build-time and runtime configuration