OpenKM Professional Edition and Migration Tool with Docker

Problems with installing OpenKM? No problemo, the solution is closer than you think.
Forum rules
Please, before asking something see the documentation wiki or use the search feature of the forum. And remember we don't have a crystal ball or mental readers, so if you post about an issue tell us which OpenKM are you using and also the browser and operating system version. For more info read How to Report Bugs Effectively.
Post Reply
Phoenix880
Fresh Boarder
Fresh Boarder
Posts: 5
Joined: Thu Jun 21, 2018 2:50 pm

OpenKM Professional Edition and Migration Tool with Docker

Post by Phoenix880 » Tue Jul 03, 2018 10:52 am

We run OpenKM Comunity Edition in a Docker Container with the official OpenKM Image:
https://hub.docker.com/r/openkm/openkm/

Since the Community Edition lacks a migration tool for automatic database migration during version upgrades, we are considering switching to the Professional Edition. So I have a few questions:

1. Is there a Docker Image for Professional Edition too ?

2. How does the OpenKM Professional Editions Migration Tool work together with Docker ?

3. Is it possible to run the migration tool automatically without any user interactions ?

jllort
Moderator
Moderator
Posts: 10169
Joined: Fri Dec 21, 2007 11:23 am
Location: Sineu - ( Illes Balears ) - Spain
Contact:

Re: OpenKM Professional Edition and Migration Tool with Docker

Post by jllort » Sat Jul 14, 2018 10:33 am

We do not have special support for docker with Professional edition, because of a license requirement what is quite difficult to get it running automatically in docker scenario. Usually, docker scenario has been thought for start and stop fresh containers ( when stopping you usually destroy the environment and then the start process goes ahead with fresh one, that's what is not a good scenario for the application like OpenKM what needs static database and repository where to keep information in time ). You

The OpenKM "upgrade tool", takes control of your OpenKM installation and applies all action to upgrade application version 6.4.x to 6.4.x+1

A user must execute the upgrade tool, we consider is an administrator task what might have some supervision. Although the upgrade process is well tested, the customer configurations might have some singularities what has not been taken into consideration what might raise some warning or error. During the last 2 years we have the upgrade tool running, only we have found an issue with a customer, caused by non-standard authentication configuration based in LDAP what caused a low-level issue ( needed to apply change into OpenKM.xml ). The upgrade tool is not able to break anything in your data, the most dangerous issue you can get is after the upgrade the scripts of the startup application need some change for right starting up. Data will never be damaged due to the characteristics of how is doing the upgrade.

Hope these will give to you some light about it.

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests