Documentation
Deploying on Deployra
Understand how deploys work and how to manage them.
Deployra can automatically deploy your application each time you merge a change to your codebase. You can also trigger manual deploys, both programmatically and in the Deployra Dashboard. All service types redeploy with zero downtime, ensuring your applications remain available throughout the process.
Connect to your GitHub repository and deploy automatically when you push to your main branch.
Deploy on-demand through the dashboard or via API when you need more control over timing.
Keep your services available throughout the deployment process with a seamless rollout strategy.
Automatic Deploys
As part of creating a service on Deployra, you link a branch of your GitHub repo (such as main or production). Whenever you push or merge a change to that branch, by default Deployra automatically rebuilds and redeploys your service.
Branch-based deploys
Any code changes to your linked branch will trigger a new deployment automatically.
Immediate detection
Deployra immediately detects when new commits are pushed to your repository.
Automated process
The entire deployment process runs automatically without requiring manual intervention.
Disabling Auto-Deploys
If you always want to trigger deploys manually, you can disable auto-deploys in the Deployra Dashboard:
Go to your service's Settings page
Navigate to your service dashboard and click the Settings tab
Set Auto-Deploy to No
Click Save
Your changes will take effect immediately
Manual Deploys
From your service's page in the Deployra Dashboard, you can manually trigger a deployment whenever needed. This is useful for deploying specific versions or when you have auto-deploys disabled.
Dashboard Manual Deploy
To trigger a manual deploy from the dashboard:
Navigate to your service's overview page
Click the "Manual Deploy" button in the header
Confirm the deployment
Managing Deploys
Canceling a Deploy
You can cancel an in-progress deploy in the Deployra Dashboard:
Go to your service's Events page
Click the word Deploy in the corresponding event entry
Click Cancel deploy
The deployment process will be stopped immediately
Restarting a Service
If your service is misbehaving, you can perform a restart from the service's page in the Deployra Dashboard. Click the Restart service button.
Zero-Downtime Deploys
Whenever you deploy a new version of your service, Deployra performs a sequence of steps to make sure the service stays up and available throughout the deploy process—even if the deploy fails.
This zero-downtime deploy sequence applies to web services and private services, ensuring your applications remain accessible to users at all times.
Your new code is built into a new container image
A new instance of your service is started with the new image
Health checks verify the new instance is ready to accept traffic
Traffic is gradually shifted from old to new instances
Once all traffic is on new instances, old instances are terminated
If health checks fail on the new instance, Deployra detects the failure
No traffic is routed to the unhealthy new instance
Existing instances continue to serve all traffic without interruption
Detailed logs of the failure are captured for debugging
You receive a notification about the failed deployment