The Documize Update Process
Documize is available as both cloud and self-host options – and that brings it’s own challenges from a release and installation perspective.
For the self-host option, the following represents the process for applying the latest product release on your server:
Download the correct binary for your OS (Windows, Linux, macOS).
Stop your existing Documize instance.
Replace your existing binary with the newly downloaded binary.
Start Documize again.
Documize will self-migrate the SQL database with any schema changes introduced in the new release.
Some points of interest:
You don’t need to upgrade in sequence so feel free to jump from v1.60.0 to v1.65.0 (for example).
The process works in a clustered, multi-machine environments as well as single machine deployments – the migration process automatically elects a leader to perform the database upgrade process.
The Documize cloud/SaaS offering uses the same binary that you install on your servers so we dog-food the process each time there is a new release.
We release updates frequently, usually twice a month. Documize adminstrators automatically receive an in-app notification about the latest product update. You will presented with a change summary for the new update.
Post-upgrade, regular Documize users receive a “What’s New” message providing a friendly introduction to any changes and new features.
The upgrade process usually only takes a few minutes from start to finish.