Initial commit of Linux Mass Updater script

Script to update multiple xTuple systems (with multiple packages)
To be honest had not thought of that - and the script was originally
aimed at updating multiple systems with a package rather than multiple
packages.   The only simple solution I can see to that is to read a
packagelist file and have the order maintained in that file.  But that
would make the script more complex to set up ??


On 11/06/14 00:57, Gil Moskowitz wrote:
>
> In utilities/AutoUpdate/xtuple_autoupdater:
>
> > +# Initialise Log file
> > +cat > xtuple_update.log << EOF
> > +xTuple Multi-System Updater Script
> > +===========================================
> > +Applying xTuple Packages:
> > +
> > +EOF
> > +
> > +   
> > +# Read in the password from the STDIN
> > +read -s -p "Please enter the Admin database password:" PASSWORD
> > +echo 
> > +echo "Loading xTuple packages from ${LOCATION}"
> > +
> > +if [ ${LOCATION: -1} -eq "/" ]; then 
> > +  PACKAGELIST=`ls -L ${LOCATION}*.gz`
>
> This requires package file renaming to enforce load order when order
> matters. Is that a workable & supportable restriction?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/xtuple/updater/pull/5/files#r13591328>.
>