Finally we've decided to upgrade removing all the code and installating new one via tar. Plugins will alse be installed again and upgraded if needed. Plugin list and settings will be saved centrally.
In reply to Juan Daniel Burró Aláez
Ri: Re: Moodle unattended upgrades inside docker
by Corrado Nestola -
Really interesting.
I'm going to do the same for my company activities. Nice to browse your git!
let me study your solution and then try to contribute
Corrado
In reply to Corrado Nestola
Re: Ri: Re: Moodle unattended upgrades inside docker
I'm not involved in this deploy anymore, but related somehow. It started on production 3 months ago and everything is going ok.
In reply to Juan Daniel Burró Aláez
Re: Ri: Re: Moodle unattended upgrades inside docker
by Shane Hughes -
A little late to the party, but did you ever figure out how to persist your plugins? that's the issue I am running into trying to deploy to kubernetes. I have the moodle code baked into the container and moodledata persists but I need to figure out how to keep customizations and plugins between container reloads. I noticed in your entrypoint you install the plugins on each boot but what about the config for said plugins? my case is the oidc plugin I need to keep the configuration for it, And will be the first of many config files needed to persist.
In reply to Shane Hughes
Re: Ri: Re: Moodle unattended upgrades inside docker
We persist not only moodledata but also moodle code dir. Moodle arquitecture is not really good from a docker perspective. (same as Wikipedia and opposite to Wordpress).
Our scripts are executed just once, then we remove x permissions. However if we make an upgrade (Moodle version) we just remove all our Moodle code and make a fresh install (executing plugin scripts again), that's the reason why we have all plugins through scripts using moosh.
Our scripts are executed just once, then we remove x permissions. However if we make an upgrade (Moodle version) we just remove all our Moodle code and make a fresh install (executing plugin scripts again), that's the reason why we have all plugins through scripts using moosh.
In reply to Juan Daniel Burró Aláez
Re: Ri: Re: Moodle unattended upgrades inside docker
by Shane Hughes -
Ahh see I was thinking of doing the same, then I thought about the upgrade path. Have you ben through one yet? How was it like? Did you loose anything between upgrades replacing the code like that?
In reply to Shane Hughes
Re: Ri: Re: Moodle unattended upgrades inside docker
Just testing everything was ok or was fixed without important issues. What really matters is to automate with the script what you do with the admin backend, and to understand what each plugin is doing in the moodlecode dir. Something out of sync could be a problem so we tested it carefully. As we had many installations it was a time well spent.
In reply to Juan Daniel Burró Aláez
Re: Ri: Re: Moodle unattended upgrades inside docker
by Shane Hughes -
Thank you again for your insight, I will be busy today adding some scripts lol..