Script for updates

[matthias-ronge]

If more frequent updates are up to come in the future, it should be easy to install them. The idea is to create a script that does the updates, which typically requires the following steps:

• copy out existing configuration from webapps/kitodo*/WEB-INF/classes/
• stop Tomcat
• delete webapp, delete corresponding Tomcat work directory
• start Tomcat
• delete modules
• copy in new modules
• (if necessary: update database)
• copy in new webapp
• wait for deploy
• copy back / merge config
• restart tomcat

These steps could be summarized in a script. The script should read a properties file with the necessary config (paths etc.). It should be bundeled with the release files, making an update easy.

Question is, if this script should be kept in the Kitodo.Production repository, or if a separate repository should be created for it.

[henning-gerhardt]

This can be simplified regarding to stop and starting the Tomcat service:

• stop Tomcat
• copy out existing configuration from webapps/kitodo*/WEB-INF/classes/
• delete webapp, delete corresponding Tomcat work directory
• delete existing modules
• copy in new modules
• copy web app war file into deploy directory
• unzip war file and change owner
• (if necessary: update database)
• copy back / merge config
• start Tomcat

I'm doing this to deploy the application on our experimental system but with 2 differences:

• I'm using flyway to migrate / update the database
• I'm doing the configuration files update before updating and copying this files from a location into the unzipped war file directory structure

[matthias-ronge]

I don’t know if Flyway can start migrating from a random database state (previous migration steps were done without Flyway, the database schema contains custom non-Kitodo.Production tables, etc.) Maybe this can be a config option.