Installing and upgrading help

I don't have a script for installing as I rarely ever install a fresh copy, only duplicate existing Moodle installs. I sanitized some stuff. Use at your own risk. Here you go:

#!/bin/bash
goodtogo=1
issnapshot=0
if [ -z $1 ]; then
	echo 'test or live not specified.'
	goodtogo=0
elif [ $1 == 'live' ]; then
	site='moodle.example.com'
	db='databasename'
	files='moodledatadirectory'
elif [ $1 == 'test' ]; then
	site='testmoodle.example.com'
	db='testdatabasename'
	files='testmoodledatadir'
elif [ -d $1.example.com ]; then
	# For snapshot sites
	site="$1.example.com"
	db="$1database"
	files="moodledata_$1"
	echo "Site: $site"
	echo "DB: $db"
	echo "Data: $files"
	issnapshot=1
else
	echo "$1 is not test or live or a snapshot site name."
	goodtogo=0
fi

if [ $goodtogo -eq 1 ]; then
	if [ -z $2 ]; then
		echo "Updating $site to current release..."
		newbranch=''
	else
		echo "Upgrading $site to MOODLE_$2_STABLE..."
		newbranch="MOODLE_$2_STABLE"
	fi

sqlhost='localhost'
sqluser='databaseuser'
sqlpass='databaseuserspassword'
mydate=$(date +%F)

cd /home/siteuser

echo "Putting site in maintenance mode..."
cd $site
/usr/bin/php5.6 admin/cli/maintenance.php --enable

echo "Purging caches..."
/usr/bin/php5.6 admin/cli/purge_caches.php
cd .. 

if [ "$site" == "moodle.example.com" ]; then
echo "Live site: creating SQL backup of $db..."
mysqldump --add-drop-table -h$sqlhost -u$sqluser -p$sqlpass $db > $db-backup-$mydate.sql

echo "Backing up programs and files..."
tar -cpzf _backup/$site-backup-$mydate.tgz $site $files $db-backup-$mydate.sql
rm $db-backup-$mydate.sql

fi

echo "Backing up modified files in $site..."
cd $site
git config --global user.email "admin@example.com"                                           
git config --global user.name "Admin Name"
git stash

if [ "$newbranch" != "" ]; then
	echo "Switching to $newbranch..."
	git branch --track $newbranch origin/$newbranch
	git checkout $newbranch
fi

echo "Pulling current branch files..."
git pull

echo "Restoring modified $site files..."
git stash apply

echo "Running upgrade..."
/usr/bin/php5.6 admin/cli/upgrade.php --non-interactive

echo "Purging caches again..."
/usr/bin/php5.6 admin/cli/purge_caches.php

echo "Returning site to normal mode..."
/usr/bin/php5.6 admin/cli/maintenance.php --disable

echo "Running cron..."
/usr/bin/php5.6 admin/cli/cron.php
cd ..

echo 'Done.'
echo ''
echo "Don't forget 'git diff' to verify modified files!"

else
	echo ''
	echo 'Use git to update/upgrade Moodle'
	echo ''
	echo 'Syntax: ./upgrade-moodle live|test [upgrade-branch]'
	echo '  upgrade branch like 28 for MOODLE_28_STABLE'
	echo '  no upgrade-branch updates to the current release in the installed branch'
fi

Please see:

https://sos.tcea.org/upbash.txt

That one script can be used for updating as well as upgrading ... depending upon which lines are active and which lines a commented out (# lines are commented out thus no execution).

This one happens to have a pause in it so one can see the backup files before progressing.

The script could be broken into two ... one for updating and one for upgrading ... and could be executed from /usr/local/bin/ ... IF one adding a cd line to the beginning of the script so that one can execute the admin/cli/ scripts.

'good practice' ... backup before updating or upgrading ... test your backups from time to time on a test server.   The issue with good/usable full site backups would center around moodledata/filedir/.   DB tables related to files needs to match what's in filedir.

Since backing up moodledata might actually be more than you need when updating, one could forgo the backup of moodledata ... could do minimal and backup only moodledata/filedir/

2 cents! ;)

'spirit of sharing', Ken

Take a backup, run 'git pull', run the upgrade script.  Why do you need an upgrade script for that?

If you are upgrading between major versions and you have loads of plugins then you need to copy and test the upgrade anyway.

I have some script files that I use at this webpage of mine.

Thanks everybody for your help (especially those that shared their scripts).

I have made an attempt on update (I am still working on an upgrade script). Could you have a look and see if there is any thing that I have missed: update.sh .

It follows the git approach (the code of moodle is installed from git). So, basically it needs just a 'git pull' to get the latest version of the stable branch. In particular, I don't touch any installed plugins at all. I assume that an update does not change any APIs or DB structure, so it cannot break any installed plugins. Is this correct?

Another question: I have made the entire moodle directory owned by www-data (apache user). Is this OK?