* Update guac-upgrade.sh
Adjusted version from 0.9.14 to 1.0.0
* Update guac-install.sh
Updated version from 0.9.14 to 1.0.0 and commented out patching that is specific to 0.9.14
* Update README.md
Adjusted version from 0.9.14 to 1.0.0
* Update guac-install-server.sh
Adjusted version from 0.9.14 to 1.0.0
* Update docker-install.sh
Adjusted the version from 0.9.14 to 1.0.0
Thanks to @bigredthelogger for providing the initial code
* Add Non-Interactive Option to Installer
* Update README for Non-Interactive Options
* Add Non-Interactive Option to Upgrade
* Support Upgrade From Older Versions
First I've added a MySQL Root Password Prompt, it will verify that the user is entering the correct password and will not continue until the MySQL Root Password is entered correctly.
Second, I'm just getting the tomcat version number from /etc/ folder name...This seems to work well enough (instead of making the user edit the script manually)...Maybe someone can come up with a better solution?
Third, I'm using the Version.js file to get the currently installed versions number. This allows for supporting multiple version number upgrades (E.G going from 0.8.2 to 0.9.14). The script will now loop through all of the SQL Upgrade files, and apply any that are newer than the OLDVERSION...
I.E. Going from 0.9.9 to 0.9.13 should automatically install `upgrade-pre-0.9.10.sql` & `upgrade-pre-0.9.11.sql` & `upgrade-pre-0.9.13.sql`
* Remove GUACAMOLE_HOME
According to the documentation this is now a default search path, so this isn't required anymore
* Version Control for Ubuntu and Debian
This might need more work but it should install the proper packages for both Ubuntu and Debian and account for Tomcat 8.0.x and 8.5.x differences...
http://tomcat.apache.org/whichversion.html
7.x does not say end of life... but 8.0.x does. The distro maintainers have different versions of Tomcat8 so we can check for 8.5.x or newer options and install, otherwise go the safer route and install Tomcat7
* Remove rm and ln of tomcat/.guacamole
According to the documentation this is not required (it may not have been required to begin with?)
* No Longer Incubating!
* Tomcat Variable
I don't know a good way to know which tomcat version is already running, and of course someone could theoretically run more than one...so the upgrade script is just a variable but the install script will check apt-cache and try to install tomcat8, then tomcat7, then tomcat6...
* Optional commented line
Added a commented out line in case someone wants to force an older/specific tomcat install
If the schema upgrade needs to happen then the file name would exist with the current version's name so it's easy enough to check for and run if necessary.
