CKEditor Ecosystem Documentation
Search
Home/Cloud Services/On-Premises

guideUpgrading the Docker installation

We release a new Collaboration Server On-Premises version every 6 weeks. It comes with new features, bug fixes, and security updates. Some new CKEditor 5 features may not be compatible with older versions of Collaboration Server On-Premises, too. For these reasons, it is highly recommended to keep your Collaboration Server On-Premises server up-to-date.

Using Docker containers greatly simplifies the process of upgrading the Collaboration Server On-Premises version. The upgrade process may differ depending on the deployment tools and platforms used. Refer to the steps below for the correct order of actions.

If possible, you should first try to upgrade a non-production instance of the Collaboration Server On-Premises using a copy of the production data.

# Upgrading to a new version

  1. Backup your database - this will ensure, that in the case of any issues after the upgrade, you can restore the database and roll back to the previously used Collaboration Server On-Premises version.
  2. Stop all instances of the Collaboration Server On-Premises servers.
  3. Start the Collaboration Server On-Premises servers using a higher minor version - you should not skip any minor versions when upgrading. For example, if you are currently running Collaboration Server On-Premises version 3.12 and you would like to upgrade it to the latest version, you should start with an upgrade to 3.13.
  4. Verify whether the Collaboration Server On-Premises servers are up and running.
  5. Repeat steps 2, 3, and 4 until you have the desired version of the Collaboration Server On-Premises running.

All important changes are added to the Collaboration Server On-Premises changelog. You can find it in the CKEditor Ecosystem customer dashboard.

We are working on zero-downtime upgrade of the Collaboration Server On-Premises servers by allowing multiple versions to run at the same time, but we cannot guarantee it yet. This is due to the fact that migrations may change the database structure and the old version of the On-Premises server might not be able to work properly. Therefore, before launching the new version, we recommend turning off all instances of the Collaboration Server On-Premises servers.