Thanks a lot for answering Howard. Yes, I am considering a VM as well, although I would prefer a container to keep it lightweight.
Svar: Re: Moodle + docker (or other local development solution) with existing site
Re: Git upgrade 3.8 to 3.9 failed
About why Git reports some files as being locally changed, because they are locally changed. You are the only person on earth who could investigate - the files are in your custody.
Re: Svar: Re: Moodle + docker (or other local development solution) with existing site
Re: Git upgrade 3.8 to 3.9 failed
'... what went wrong ..' ... if I could do Vulcan Mind Melds with systems, I'd know! Am just a mere mortal, however! :\
Git is 'suitable' for updates and upgrades ... by far much more reliable (it has been for me on multiple servers) and less prone to human error when one looks at the 'old way' ('moving' copying, etc).
The links Visvanath Ratnaweera shared and discussion happened at a time when 3.9 was dev still ... I think. Not a 'stable release' ... and there weren't any rc releases of that version this time ... at least none that I saw ... but wasn't checking every day.
Dunno what you use for a workstation ... I use a Mac and have git installed. I test acquisition of moodle code on this Mac first ... even the setting of branches and checkouts to higher versions of Moodle.
Just tested on this mac:
git clone git://git.moodle.org/moodle.git 38to39test
cd 38to39test
git branch -a - show * master at this point
git branch --track MOODLE_38_STABLE origin/MOODLE_38_STABLE
git checkout MOODLE_38_STABLE
Switched to branch 'MOODLE_38_STABLE'
Your branch is up to date with 'origin/MOODLE_38_STABLE'.
Kens-MBP-2:38to39test kentask$ fgrep '$release' version.php
$release = '3.8.3+ (Build: 20200626)'; // Human-friendly version name
So 3.8.3+ has been acquired.
now the switch to 39
git branch --track MOODLE_39_STABLE origin/MOODLE_39_STABLE
Branch 'MOODLE_39_STABLE' set up to track remote branch 'MOODLE_39_STABLE' from 'origin'.
checkout MOODLE_39_STABLE
Checking out files: 100% (3726/3726), done.
Switched to branch 'MOODLE_39_STABLE'
Your branch is up to date with 'origin/MOODLE_39_STABLE'.
Kens-MBP-2:38to39test kentask$ git branch -a
MOODLE_38_STABLE
* MOODLE_39_STABLE
Kens-MBP-2:38to39test kentask$ git pull
Already up to date.
Kens-MBP-2:38to39test kentask$ fgrep '$release' version.php
$release = '3.9+ (Build: 20200626)'; // Human-friendly version name
Appears to have acquired 3.9 code successfully.
And no issues with 'admin' directory reported.
Fluke/hickup? Maybe!
'SoS', Ken
Svar: Re: Svar: Re: Moodle + docker (or other local development solution) with existing site
Re: Svar: Re: Svar: Re: Moodle + docker (or other local development solution) with existing site
Docker on the other hand, I've never managed to get to work properly. I suppose if you know what you're doing with it, you might have a start on me.
Svar: Re: Svar: Re: Svar: Re: Moodle + docker (or other local development solution) with existing site
Re: How to disable "Forgotten your username or password" link
Re: Svar: Re: Svar: Re: Svar: Re: Moodle + docker (or other local development solution) with existing site
Re: How to disable "Forgotten your username or password" link
Re: How to disable "Forgotten your username or password" link
Odp: SMTP configuration fail
Re: Git upgrade 3.8 to 3.9 failed
I checked with git diff and it told me 644 was the original permission of most files. After fixing this back to 644 I could checkout and upgrade from 3.8 to 3.9.
Migrating existing H5P content when upgrading to Moodle 3.8
Will be upgrading to Moodle 3.8 this summer and as Moodle 3.8 has H5P integrated into the system I was wondering if the existing H5P Moodle plugin was removed would our existing H5P content be able to be migrated and be used after the upgrade?
Re: Migrating existing H5P content when upgrading to Moodle 3.8
Re: Migrating existing H5P content when upgrading to Moodle 3.8
Just to confirm if we were to remove our current H5P plugin with the upgrade it wouldn't affect any of the content in the Moodle libraries that the current mod_hvp plugin points to and therefore all current H5P content could be migrated and used within the new upgrade?
Re: Migrating existing H5P content when upgrading to Moodle 3.8
Moodle cron job
What is the function cron job and where you can set up in moodle?
Re: Moodle
Ref. cloudpit