[Koha-bugs] [Bug 22796] koha-common and mariadb start in the wrong order

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22796

David Cook <dcook at prosentient.com.au> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dcook at prosentient.com.au

--- Comment #3 from David Cook <dcook at prosentient.com.au> ---
This is a really interesting point. 

I've been thinking a lot about database upgrades lately. 

Kong Gateway can be installed by a Debian package, but it requires a person
running "kong migrations up" to trigger an actual database upgrade. 

Keycloak will apply database migrations/upgrades automatically when you start
the application. 

I'd suggest moving a lot of the code from koha-common.postinst into the
koha-common service (ie /etc/init.d/koha-common). 

Then koha-common.postinst could just restart the koha-common service.

An optional dependency on Mariadb could be added, so koha-common would wait to
restart until after Mariadb is available. If the Mariadb service isn't
available on that server, it'll just ignore the dependency.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.