This repository was archived by the owner on Jul 20, 2022. It is now read-only.
How to manage upgrades in production? #5
Description
Hi,
Thanks for the tutorial!
When thinking on migrating a traditional hosting-based moodle install to a docker/kubernetes model, one of the things stopping us is the management of upgrades.
More specifically we are looking for a sort-of-foolproof way to prevent the container to start if the image moodle version is more recent (or, weirdly enough, older) than what the database thinks?
A brute force approach would be to always run the upgrade cli command, but can take ages to run.
Thx