Deployments Overview
Deployments are how your code gets from GitHub to your server. You can trigger them manually from the dashboard or automatically on git push.
Your source code is cloned and built directly on your server — it never passes through Reoclo’s infrastructure.
Triggering a Deployment
Section titled “Triggering a Deployment”Manual
Section titled “Manual”Navigate to your application in the dashboard and click Deploy. This deploys the latest commit from the configured branch immediately.
Use manual deployments when you want explicit control over when code ships to production.
Auto-Deploy
Section titled “Auto-Deploy”Enable auto-deploy in your application settings to trigger deployments automatically when you push to the configured branch.
Auto-deploy is great for staging environments or development servers where you want continuous deployment. For production apps that need manual approval, leave it disabled.
Deployment States
Section titled “Deployment States”| State | Meaning |
|---|---|
PENDING | Scheduled, waiting for execution |
RUNNING | Building and deploying on the server |
SUCCEEDED | Health checks passed, new container is live |
FAILED | Something went wrong, previous container restored |
Zero-Downtime Deploys
Section titled “Zero-Downtime Deploys”Reoclo uses a blue-green deployment strategy:
- The new container starts alongside the old one
- Health checks run against the new container
- Only after the health check passes does the old container stop
- On failure, the old container stays running and the new one is removed
Failed deployments don’t cause downtime. If your new code breaks the health check, the old version keeps serving traffic.
Viewing Deployments
Section titled “Viewing Deployments”The dashboard shows deployment history with:
- Status (pending, running, succeeded, failed)
- Duration
- Commit SHA and message
- Full pipeline logs
Click any deployment to see the complete log output. This is useful for debugging build failures or understanding why a health check failed.
Next Steps
Section titled “Next Steps”- Configure your deployment with environment variables, health checks, and Docker settings
- Understand server connections to see how Reoclo connects to your infrastructure
- Review encryption to understand how secrets are protected