Update zadam version 0.63.7 to TriliumNext version

[miltuss]

Hello, I am currently using the version docker.io/zadam/trilium

How do I update this version to the latest version of TriliumNext?
Are there any interim updates that need to be done to avoid breaking the database?

[dosubot[bot]]

You can upgrade directly from zadam/trilium 0.63.7 to the latest TriliumNext Docker image—no interim updates are needed and the migration process is safe. Here’s how:

1. Back up your data directory, especially document.db and the backup folder.
2. Stop your current Trilium server.
3. Update your Docker configuration to use the triliumnext/trilium image instead of zadam/trilium.
4. Start the server with the new image. TriliumNext will automatically handle all necessary database migrations.
5. After upgrading the server, update all client applications to the matching version before enabling sync to avoid protocol mismatches.

TriliumNext creates a backup before any migration, so you can restore if needed. There are no special migration steps required—just switch the Docker image and let the migration complete uninterrupted. If you run into sync or consistency issues, use the “force full sync” and “fix consistency issues” commands in the app. For more details, see this migration discussion and the official upgrade guide.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[eliandoran]

@dosu answered almost perfectly.
triliumnext/trilium is the Docker image name to be used.

[dosubot[bot]]

You can upgrade directly from zadam/trilium 0.63.7 to the latest TriliumNext using the triliumnext/trilium Docker image—no interim updates are needed and the migration is safe and automatic. Just back up your data directory (especially document.db and the backup folder), stop your current server, switch your Docker config to use triliumnext/trilium, and start the new container. TriliumNext will handle all database migrations and create a backup before migrating. After upgrading the server, update all clients to the matching version before syncing to avoid protocol mismatches. If you run into sync or consistency issues, use the “force full sync” and “fix consistency issues” commands in the app. More details are in the official upgrade guide and migration discussion.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.