Shipping changes
Update your app from GitHub
Each change that you push goes live on its own, and you can go back to an earlier version.
Why use it
You keep working in Lovable, Claude or your editor as usual. When you push to GitHub, the new version goes live. You do not need to log in to the console for each change.
How it works
- You push a change to your main branch.
- GitHub Actions builds the app.
- GitHub proves to Apervia which repository and which workflow sent the build. No password is stored in GitHub.
- Apervia starts the new version. When it is ready, people see it.
If the new version does not start, the old version keeps running. Nobody sees a broken app.
See what happened
Open the Releases page of the app. It shows each release, who made it and if it worked. Select an earlier release to go back to it.
Keep secrets out of the code
Do not put a password or an API key in your repository. Put it in the settings and secrets of the app.