Upgrading to Moodle 4.1 and a look around the new stuff
HTML-код
- Опубликовано: 27 ноя 2022
- Moodle 4.1 is here! And I cannot wait to upgrade my Moodle. So, I will upgrade one of my Moodles tonight from 8:00PM (JST). And, you're all welcome to come and join me while I do the upgrade.
That's right, I will be LiveStreaming the upgrade! I messed up the LiveStream of my upgrade to 4.0, so this might end up being quite entertaining. There is a *Live-Chat function in RUclips livestreaming too, so I'll try to answer any questions you may have in real-time.
* To participate in the Live-Chat, you need to have subscribed to the channel (why not, eh?).
See you then!
Kia ora mate. This is awesome thanks. For version control our business uses bitbucket and the Moodle install is in our own repo which includes all of our customizations. How would you recommend we use git branching to update in this manner is that even possible? Currently its a manual process, and I would love this to be more automated. I was also wondering if we did a fresh install (start again using this method and submodules). Do you have a video on how to migrate users / courses and completion data?
Kia ora! The reason I really love git over one-click installers has to do with the way git can ignore plugins as "untracked" files. Is that what you mean by "customisations"? If you have actually changed Moodle core code, first, you're brave! Second, using bitbucket or Github etc is a great way to manage merges from upstream Moodle and deal with conflicts efficiently.
When I update (minor releases) or upgrade (major), I usually use "git pull" or checkout the new branch from the Moodle repo directly. My plugins remain as untracked files so stay in place (occasionally have to upgrade the plugins simultaneously during upgrades). In addition, the user data is untouched by this process so my users barely notice most of the time.
I've been considering doing an "anti-one-click installer" video for a while. Perhaps it's time...
What are the main improvements from Moodle 4.0 to 4.1?
This page has a pretty good overview of the new features. docs.moodle.org/401/en/New_features
Great tutorial. I am using moodle4.0 with postgres 10.23 but to upgrade to moodle 4.1 it need postgres 12. Any idea please on ours to upgrade postgres 10 to 12 without losing any data? Thanks
I would say that the safest way is to take a dump of the database first, then upgrade postgres and populate a new instance of the database from the dump file. Some Linux distros may appear to be able to upgrade a database in place, but I wouldn't count on it. Either way, take a dump first and save it to a local disk before trying it (always good to have a backup).
I have never heard of people having trouble using an older SQL dump to populate a new database in a newer version of Postgres. Good luck!
Why make a backup moodledata?
As part of the 3 components required for a full backup (the SQL database, moodledata, and the moodle code/www) I generally prefer to back everything up together. That way there's no mistake that this version of moodle code goes with this moodledata and this SQL database. Sure it may be overkill but when the moodledata dir is as small as mine is, there's no need to exclude it from the backup. For an upgrade such as this, technically you could get away with only backing up the SQL database, but that seems unnecessarily reckless to me. But hey, I'm paranoid...
It's only when you don't take a full backup that you end up wishing you had...
@@Wise-Cat I have a 3TB moodledata folder on my moode project, reserving for an upgrade would be quite a long task.
I can understand how that would make it more difficult. I'll never advise against taking backups though. Perhaps an offline backup could be maintained using a tool like rsync? The initial backup would take a long time but thereafter would be incremental (only changed files would be updated). Hmm. rsync could be a good topic for a video... Cheers!
@@user-df3jd5sp9y Depending on your infrastructure you could use AWS EBS volume snapshots to manage duplicating your moodledata