IF your hosting has Terminal and Git, this little script will make use of git to
put your test site under git versioning for moodle core code.

It is offered as is ... and should first be used on a clone/test site that was
installed via Softac (or similar) or manually using the moodle docs - moodle code is in a directory.

If your site is already broken, this script will not fix it.
You should do the preliminaries ... check environment to assure you have
the version of PHP + php extensions required.  You should check your plugins
to assure they have a compatible version for destination version of core.
See: https://moodle.org/plugins/?q=
If the environment check shows REDS you must address those *before* using
gitify.

Upon unzipping gitify.zip, there will be 3 files:
READMEFIRST.txt - file you should be reading now.
gitify - the bash shell script that creates.
gitifyvars - a text file which defines variables used in gitify script.
*** YOU MUST EDIT gitifyvars FILE FIRST FOR THE SCRIPT TO WORK! **
Let me repeat that ...
*** YOU MUST EDIT gitifyvars FILE FIRST FOR THE SCRIPT TO WORK! **

Most remotely hosted sites have a text editor called 'nano'.
To edit gitify and scripts created by it, use nano.
nano nameofscripttoedit [ENTER]
But, since you have a panel that has a file browser, files can be edited with
those tools as well.

For tutorial on how to use nano,
https://linuxize.com/post/how-to-use-nano-text-editor/

The variables, their current values, (*which you must change*) and an explanation of each:

shortmversion='418'

Version of Moodle you have ... without the 'dots' and point release.
Example: in Notifications of Moodle admin at the the bottom of that screen
it shows something like: 4.1.2 (build: xxxxxxxxxx)
Short version of above would be '412'


pathtobackupdir='/home/ktask/backups'

This is where the bu script that will be create by gitify will save site backups.
Script will not create it for you.  Use your panel to make a backups directory in
your accounts home directory.

codedir='public_html'

This is where your current code for moodle resides.

pathtomoodledatadir='/var/www/moodledata'

In your config.php file of moodle code there is a path to moodledata.
Whatever that shows, use same for this variable.  Do not use a trailing slash.

dbuser='moodledbuser'

In your config.php file, there is a DB user.  Use same for this variable.

dbpass='aswefihqpwedsf/asdfs'

In your config.php file, there is a DB password.   Use same for this variable.

dbname='moodle'

In your config.php file, there is a DB name.   Use same for this variable.

gitversion='401'

Git version of code ...
a 4.1.x is in git versioning a 401
a 4.2.x is in git versioning a 402
a 4.3.x (highest when this was created) is in git versioning 403

In the gitify script you MUST edit 2 lines.
git branch –track MOODLE_401_STABLE origin/MOODLE_401_STABLE
git checkout MOODLE_401_STABLE

And change the git version numbers to match that of the code you have.
See git version of code above.

The scripts are not made executable by default and do not have any filename extensions
on them.   They do not need to be made executable if you use; 'source [nameofscript]'.

Ownerships/permissions should be checked.
For the gitify, bu, and update script, use: chmod go-rwx gitify bu update

** WARNING **
if you run gitify again, the bu and update scripts will be incorrect.
Before you run gitify again, rm bu update upgrade.

You only need to run gitify once.  After successful run, you should check the scripts created 
to assure correct paths and version numbers.
The build directory for gitify (gitcode) to acquire moodle code via git needs to be erased.
No longer needed.   Makes your backup of code directory larger than it needs to be.

Source for gitify can be found via:
https://mg2.sosoftexas.org/scripts/gitify/