por Ken Task.
Future of MySQL - version 8 (has been released).
From:
https://dev.mysql.com/doc/refman/8.0/en/charset-unicode-sets.html
utf8: An alias for utf8mb3.
Note
The utf8mb3 character set is deprecated and will be removed in a future MySQL release. Please use utf8mb4 instead. Although utf8 is currently an alias for utf8mb3, at that point utf8 will become a reference to utf8mb4. To avoid ambiguity about the meaning of utf8, consider specifying utf8mb4 explicitly for character set references instead of utf8.
The way I read that ... if staying with MySQL ... and eventually upgrading it to 8 ...
the moodle db will have to be utf8mb4.
Before updating/upgrading, check server environment.
Extra ... way more ...
The 'old way' ... keep config.php (archived) and any plugin not part of core.
Acquire new code. Unzip or whatver, copy back into new code config.php and any plugins
not part of core. Run the upgrade.
It's always been advised to check the config-dist.php file with the new code for
changes/additions not present before.
Git - no files move. Git acquires newer version of 5.5.4+ -> 5.5.5+ core code in place.
Less prone to human error in archiving all tha needs to be archived prior to upgdate/upgrade ... op forgot to copy back an addon plugin - get missing from disk.
Checking plugins is also a good idea prior to updating/upgrading.
(* if one has customized code, one could stash or run their own git repo)
I do this and it's served me well to avoid issues on updates and espcially upgrades.
(Don't have any sites with major customizations/hacks to core code)
Create a directory in moodle code called 'addons'.
In 'addons', create a addons.txt file which is nohing more than the 'shortname' of
all the addons in the site.
Looks like:
mod_hvp
mod_questionnaire
mod_customcert
Create an executable script that uses moosh to check addon versions.
'checkaddons'
#!/bin/bash
#
echo 'Add-on listing: ';
cat ./addons.txt;
echo '---------------------';
for i in `cat ./addons.txt`
do
echo "Addon in que: $i";
moosh -n plugin-list |grep $i
done
When run, looks like:
Add-on listing:
mod_hvp
mod_questionnaire
mod_customcert
---------------------
Addon in que: mod_hvp
mod_hvp,2.7,2.8,2.9,3.0,3.1,3.2,3.3,3.4,3.5,3.6,https://moodle.org/plugins/download.php/19174/mod_hvp_moodle36_2019031301.zip
Addon in que: mod_questionnaire
mod_questionnaire,1.9,2.0,2.2,2.3,2.4,2.5,2.6,2.7,2.8,2.9,3.0,3.1,3.2,3.3,3.4,3.5,3.6,https://moodle.org/plugins/download.php/19206/mod_questionnaire_moodle36_2018050109.zip
Addon in que: mod_customcert
mod_customcert,2.9,3.0,3.1,3.4,3.5,3.6,https://moodle.org/plugins/download.php/18626/mod_customcert_moodle36_2018120301.zip
I then use the above url's to build a 'getlist' file which looks like:
https://moodle.org/plugins/download.php/19174/mod_hvp_moodle36_2019031301.zip
https://moodle.org/plugins/download.php/19206/mod_questionnaire_moodle36_2018050109.zip
https://moodle.org/plugins/download.php/18626/mod_customcert_moodle36_2018120301.zip
And then use wget to get them:
wget -i getlist
Using the acquired zips:
mod_hvp_moodle36_2019031301.zip
mod_questionnaire_moodle36_2018050107.zip
report_questionnairestats_moodle34_2018060700.zip
I upgrade manually. I hide the original plugin directory first for easier recovery
from a plugin compat issue
Put site in maintenance mode via CLI - that stops cron from running and any 'normal' access by students/teachers.
cd mod
mv hvp .hvp
Then copy the zip for hvp into mod.
Unzip
change owneerships/permissions.
After I get all those in place, use:
cd moodleoode/admin/cli/
php upgrade.php
I've now gotten into habit of purging caches from CLI
Then take the site out of maintenance mode:
php maintenance.php --disable
And check the running of cron via CLI.
Then check Notifications and Plugins via browser.
Yeah, I like getting my hands 'dirty' a little. Makes me feel like
I've 'accomplished' something ... or 'earned my pay' ... so to speak.
'spirit of sharing', Ken