Servers
Updating
Update Jokku in place. It backs up first, rolls back on failure, and your apps keep serving throughout.
Update a server#
On the server:
It shows the new version and asks before changing anything.
What happens#
- Jokku downloads the new release and checks it against the release's checksums.
- It backs up its database and the current binary. The newest five backups are kept, in
/var/lib/jokku/backups/. - It installs the new binary and runs
jokku setup, which brings the server to the state the new release needs, then waits until the new version is answering. - If any of that fails, it puts the previous version and data back automatically.
Your apps keep running and serving traffic throughout. Each microVM runs in its own system service rather than inside the Jokku daemon, and the proxy and internal DNS are separate services too, restarted only when their own code changed. The control commands are unavailable for a few seconds while Jokku restarts.
Clusters#
With more than one server, update the control server first, then run sudo jokku update on each of the others. The control server accepts workers one release behind, so you can update them one at a time.
Servers on v0.0.2 or older#
These don't have jokku update yet. Update them once with: