Docs Updates
Updates
The console never updates itself
Automatic updates are switched off at several levels, and the console has no Update button or auto-update switch. Settings › Updates is a read-only page: it shows which version is running, the version of Coolify it is based on and its licence. Nobody can start an upgrade from the browser, by accident or on purpose.
How releases are made
We pin every component of Dekota to an exact version and build our own images. Each build is checked before it goes onto a live console. The next step, which we are adding now, is a sealed test copy: a copy of the console with no network access, restored from a recent backup, that a build has to pass before the swap.
How an update is installed today
On the consoles we run, an operator starts the update with one command on the server, cloud-update. It then:
- takes a backup of the console's own database;
- builds the new version from pinned sources;
- swaps only the console container, so your apps, databases and the proxy keep running;
- checks the console's health, version, sign-in page and every hosted app;
- goes back to the previous version on its own if any check fails.
On Dekota Cloud we will follow the same steps for you and announce each update in advance.
Planned for the Community release
Self-hosted consoles will get the same commands: one to update after a backup and checks, and one to roll back. Until the source is released there is no self-hosted update path, and this page will change when there is.