Every change you push to GitHub goes live on its own. If a change fails to build, the version people are using keeps running. Each change goes live in Colombo.
A failed build never replaces the version that is live, and you can roll back from the console.
| Deploying by hand | Roar AI | |
|---|---|---|
| A change will not build | Your app can go down | The working version stays live |
| Finding out | Often from the people using it | An email straight away |
| Going back | Undo the change and deploy again | Pick an earlier version in the console |
| Working out what broke | Search through the build output | Read the log, or ask Roar AI to try a fix |
Automatic deployments are on by default for apps connected to GitHub.
Sign in to GitHub from the console and choose your project.
Your project’s main branch is used unless you pick another.
Every push to that branch goes live. You can turn this off and deploy by hand instead.
In Colombo. Every push to your repository deploys your app there, close to your users in Sri Lanka.
Your app keeps running the previous version, and Roar AI emails you. The console shows the build log and offers to try an AI fix.
Node, Python, Go, Ruby, PHP, Java and static sites are detected automatically. If your project has its own Dockerfile, Roar AI uses that instead.
Choose an earlier deploy and Roar AI deploys that version again, reusing the earlier build when it still has it. Your GitHub project is not changed, so your next push ships your latest code.
No. The fix is kept with your app on Roar AI and can be removed in its build settings. It only runs when you ask, and it uses your AI credit.
If Roar AI cannot take a deploy, it tries again three times before emailing you.
Yes. With deploying on push off, your app only changes when you redeploy from the console.
Create a free account, connect your GitHub project and push. Your app goes live in Colombo.