Update the server to a new release
Pull the new image and restart. The database updates itself on start, and every device switches to the new app by itself.
About 3 minutes · For the person who runs the server · Last reviewed
What you need
- A recent backup, or at least a backup schedule that ran. Turn on backups
- The release notes for what changed: What’s new.
With Docker Compose
- Run
docker compose pull && docker compose up -d. The new container replaces the old one and applies migrations at startup. Updating - Open the address and check the version at the top of the in-app docs. Done. Updating
With Coolify
- If you pinned a release line such as
0.3, patch releases arrive on the next Deploy; for a new minor version, change the tag in the compose file first. One-click template - Select Deploy. Coolify starts the new container before stopping the old one, which OpenTodo supports from 0.2.0 on. Updating
On everyone’s devices
Nothing to do. The app fetches the new version in the background and switches to it on its own, usually with one quick reload. Someone who still sees the old version closes the app completely and opens it again. Updates
Good to know
- Pin a release line (
ghcr.io/pixari/opentodo:0.3) rather thanlatest, which follows the main branch. Option A: Docker Compose from the repository - Maintenance commands such as restore need every server process stopped. Updating