I am new to moodle this school year. I have been able to upgrade within the 3.9.* line using git. How do I use git to upgrade from 3.9.3 to 3.10.1?
MK
Upgrade 3.9.3+ to 3.10.*
Number of replies: 12Re: Upgrade 3.9.3+ to 3.10.*
Please see:
https://docs.moodle.org/dev/Releases
3.9.x is long term support
3.10.x is not.
However, should you decide to go forward.
In current 3.9.x site, check environment to assure no upgrades to PHP/MySQL/MariaDB
will be needed to upgrade.
CLI: cd /path/to/moodle/admin/cli/
php checks.php
To upgrade via git:
https://docs.moodle.org/310/en/Git_for_Administrators
In your case:
Site backup first ... repeat site backup first.
tar ball of Code + DB dump + tar ball of minimal moodledata/filedir
Got any plugins? Do they have a compatible version for destination version?
cd /path/to/moodlecode/
git branch -a
php cron.php
Now the switch to branch and upgrade
php maintenance.php.php --enable
git branch --track MOODLE_310_STABLE origin/MOODLE_310_STABLE
git checkout MOODLE_310_STABLE
Check version: fgrep '$release' version.php
Do upgrade
php upgrade.php
Check ownerships/permissions on files ... especially config.php (readable by globe)
out of maintenance mode
php maintenance.php.php --disable
Hit site with Web browser now and check
'SoS', Ken
Re: Upgrade 3.9.3+ to 3.10.*
Thanks Ken. So how do I know what versions are LTS vs not? I prefer sticking with the LTS versions, so I will stay with 3.9 for now.
Edit: It looks like every 4th version is LTS, is this the case or just how it turned out?
MK
Re: Upgrade 3.9.3+ to 3.10.*
There is no indication in moodle code running which is LTS and which is not nor in git branch -a. Maybe that's a 'feature request'? Checking releases page is presently the only way to know for sure.
'Every 4th' ... well, your guess is as good as mine - am sure there was discussion. Imagine since software is international and used by many large institutions/corps?, academic calendars, etc there was influence. Factors - just how much can be expected by core programmers - + other (like Covid).
Future?
'SoS', Ken
Re: Upgrade 3.9.3+ to 3.10.*
Moodle releases are generally very stable. For me, the paramount consideration when deciding whether to use LTS or non-LTS branches is what plugins I will be using on the site, as third party plugins may not be compatible with later Moodle releases, in which case having the site running a LTS version may be preferable. 3.9 is currently receiving all bug fixes, so it's fine to run it, but when it hits security-only, bear in mind that non-security related bugs won't be fixed.
If you are running Moodle core with no third-party plugins, and use Git to manage the site, I see no reason why you would not stay on the latest stable branch. The only other exception may be for *very* large installs.
If you are running Moodle core with no third-party plugins, and use Git to manage the site, I see no reason why you would not stay on the latest stable branch. The only other exception may be for *very* large installs.
Re: Upgrade 3.9.3+ to 3.10.*
I am back to my original upgrade question. I never did upgrade to 3.10 or 3.11 yet. Too much going on for that till now...
My question is this... I have a script that I use for upgrading that contains a section...
My question is this... I have a script that I use for upgrading that contains a section...
php /path/to/lms/admin/cli/maintenance.php --enable
cd /path/to/lms
git pull
php /path/to/admin/cli/upgrade.php --non-interactive
php /path/to/admin/cli/maintenance.php --disable
If I wanted to edit this to upgrade from 3.9.x to 3.10 (or3.11), would I just add
cd /path/to/lms
git pull
php /path/to/admin/cli/upgrade.php --non-interactive
php /path/to/admin/cli/maintenance.php --disable
If I wanted to edit this to upgrade from 3.9.x to 3.10 (or3.11), would I just add
git branch --track MOODLE_310_STABLE origin/MOODLE_310_STABLE
git checkout MOODLE_310_STABLE
git checkout MOODLE_310_STABLE
before the git pull command or replace it?
Sorry, I am a git noob.
MK
Re: Upgrade 3.9.3+ to 3.10.*
Re: Upgrade 3.9.3+ to 3.10.*
So is git pull only necessary when upgrading the current branch?
Re: Upgrade 3.9.3+ to 3.10.*
Yes. For more, see https://docs.moodle.org/en/Git_for_Administrators.
Re: Upgrade 3.9.3+ to 3.10.*
+1 to Mr. V's post ... in addition ...
why not do the cd to code directory first? makes paths shorter in script.
Better yet ... why not put the script at code root? Setting ownerships/permissions where no web access is possible to the script + when you do the code backup, you also have a backup of your script.
And, as a matter of good practice, why not add lines at beginning of your script to do a site backup? code + db dump + minimal moodledata/filedir
I also echo a comment to myself about current version and list the backups I have then pause. Can cancel at that point.
My 2 cents!
'SoS', Ken
Re: Upgrade 3.9.3+ to 3.10.*
That was only a portion of my script. I do have a variable for the path and do site backups/sql dump etc...
I run all of my scripts from a single directory (so I remember where they all are). Just the way I prefer to do it.
I run all of my scripts from a single directory (so I remember where they all are). Just the way I prefer to do it.
Re: Upgrade 3.9.3+ to 3.10.*
Good. There is always different ways of getting to the same place. Almost never just one way!
'SoS', Ken
Re: Upgrade 3.9.3+ to 3.10.*
Agreed.
Thank you for all of your advice. I'm starting to understand git better as well as the upgrading of moodle.
The more I use it, the more I like it. There is just sooooo much to learn.
MK
Thank you for all of your advice. I'm starting to understand git better as well as the upgrading of moodle.
The more I use it, the more I like it. There is just sooooo much to learn.
MK