I'm trying to install moodle_32 from git. Following the instructions on:
https://docs.moodle.org/32/en/Git_for_Administrators
I end up with a Moodle 3.3dev version ?
I don't wont to sit in a devellopment branche,
what am I doing wrong ?
I'm trying to install moodle_32 from git. Following the instructions on:
https://docs.moodle.org/32/en/Git_for_Administrators
I end up with a Moodle 3.3dev version ?
I don't wont to sit in a devellopment branche,
what am I doing wrong ?
Change into directory where moodle code resides
Then issue these two commands:
git branch --track MOODLE_32_STABLE origin/MOODLE_32_STABLE
git checkout MOODLE_32_STABLE
Then check the version.php file:
fgrep '$release' version.php
That check should show:
$release = '3.2.2+ (Build: 20170412)'; // Human-friendly version name
The Build is the date of your setup.
'spirit of sharing', Ken
Thanks Ken for thinking with me ...
git branch --track MOODLE_32_STABLE origin/MOODLE_32_STABLE
returns
fatal: A branch named 'MOODLE_32_STABLE' already exists.
fgrep '$release' version.php
returns
$release = '3.3dev (Build: 20161222)'; // Human-friendly version name
So i am a little bit stuck here ...
Never switched branch to devellopment version by my knowlegdge,
I am not a git expert , I wonder if I can "downgrade" a Moodle version ?
Am not a git expert either. But I will use the most efficient way to install, update, and upgrade ... and that's git.
There were two commands in previous post.
Have you executed this one:
git checkout MOODLE_32_STABLE
Then to check to see which branch is checked out:
git branch -a
*'d should be the 32 branch.
Verify:
fgrep '$release' version.php
If you need to review what commands you previously issued, use the history command:
history |grep git
or just
history
As far as 'rolling back a moodle' ... nope, only way is to restore the backup one took just prior to upgrading. Why is that? it's not only the code, it's the database.
'spirit of sharing', Ken
Hi Hurbert,
Assuming you are using GIT Bash just do a
git checkout MOODLE_32_STABLE
This should reset the files to Moodle 3.2 ready for you to set the instalation going.
Once you have it all working just go back into your GIT Bash and remove Moodle master using
git branch -D master
This will just leave you with MOODLE_32_STABLE branch.
Here is a good tutorial its a bit old but principals are the same.
https://docs.moodle.org/dev/User:Sam_Hemelryk/My_Moodle_Git_workflow
I've just spent two days after my Windows10 crashed and fortunatly my son managed to retrive all my files and do a complete restore. So have been adding Moodle to my Wampserver via my github.
Its great when you get it going as you can update so fast.
You can add themes too via git providing they are written correctly.
Cheers
Mary
It's quite annoying when a system crashes and you have to start over again ...
GIT seems indeed doing a great job, if one knows how it works
I still do not understand why I end up with a devellopment version of Moodle when I tought I was on a STABLE branch.
After reading a little bit more about git i tried following:
(Still not quite fully understand what exactly I have done ... )
$git stash save
$git checkout MOODLE_32_STABLE
made the switch from the master branch (alfa channel) to the stable one.
I like the new navigation on Moodle32.
Thanks Mary and Ken for thinking with me