Docs Rollback
Rollback
Roll back an app
Dekota keeps recent builds of each app on the server. To go back:
- Open the app and choose Rollback.
- Find the build you want. Each one shows its commit and when it was built.
- Choose Roll back next to it. Dekota starts that build, waits for its health check, then moves traffic to it.
A rollback does not change your database. If the newer version ran a migration, check that the older code still works with it, or restore a backup taken before the change.
You can set how many builds to keep. More builds use more disk.
Roll back the console
Not in the console. There is no Roll back button for the console itself. Console rollback is a command on the server, run by the operator.
On the consoles we run, cloud-update rolls back by itself when a check fails after an update. An operator can also run cloud-rollback by hand: it puts back the previous console image, and if the update changed the console's database, restores the backup taken just before it. Your apps keep running during the change.
For self-hosters, the same rollback command is planned for the Community release.
Rolling back the console only affects the console. Apps, databases and services on your servers stay as they are.