System Requirements: Apache (or alternative PHP capable) webserver PHP 4.3 PEAR::DB PEAR::Mail Database supported by PEAR::DB (recommend MySQL 4.0 or newer) fping (recommended for use with ChkNet module) Configuration Note: Please see the documentation for further details. Apache must be configured to process pages with a .php extension through the PHP processor. PHP must be set up to auto-start sessions. A working installation of PEAR and PEAR::DB must be installed. Brief installation instructions are: 1) Download the tarball and extract it to a known location. 2) Move the contents of the "includes" directory to the "includes" path set up in the PHP configuration. The path to this folder will depend on how you have configured PHP. Do not keep the "includes" directory, only the directory called "STORM" within it. 3) Move the remaining directories, except the "Documentation" directory, to a directory within Apache's document root. This does not have to be at the top level, as the paths between pages are relative. 4) Edit the STORMsetup script using your favourite text editor to replace the default passwords for the four different usernames that are setup at the end of the script with the passwords you wish to use for your installation. 5) Use the STORMsetup script to create the tables and users. How this is done will vary between SQL servers and is only tested using MySQL. A line like: /path/mysql -h localhost -u root -p < /path/STORMsetup should work under Linux. 6) Change the passwords found in the "includes/STORM/common/db" connect*.inc files to match those set up earlier when you edited the STORMsetup script. 7) Edit the "includes/STORM/common/db/db.inc" file to include the details for your SQL server. The default options supplied should work for a MySQL installation on localhost. 8) Start by pointing your browser to http://server/path/login.php 9) The default username is "admin" with password "admin" 10) ICT Team members must have their login name matching the name in the teamMembers table in order for them to see support requests assigned to them in the SATYR module. 11) Ensure that the common/img/catalogue directory is read-writeable by the user running Apache. (On Debian GNU/Linux this is www-data.) Brief Upgrade instructions (from STORM-0.1.0) 1) Download the tarball and extract it to a known location. 2) Delete the existing "includes" directory from the "includes" path set up in the PHP configuraion. 3) Move the contents of the "includes" directory extracted from the tarball to the "includes" path set up in the PHP configuration. 4) Delete the existing directories containing the software from the documentation root of your Apache installation. 5) Move the remaining directories from the expanded tarball, except the "Documentation" directory, to the now empty directory within the Apache document root. 6) Edit the STORMupgrade script using your favourite text editor to replace the default passwords for the four different usernames that are setup at the end of the script with the passwords you wish to use for your installation. 7) Use the STORMupgrade script to create the tables and users. How this is done will vary between SQL servers and is only tested using MySQL. A line like: /path/mysql -h localhost -u root -p < /path/STORMupgrade should work under Linux. 8) Change the passwords found in the "includes/STORM/common/db" connect*.inc files to match those set up earlier when you edited the STORMsetup script. 9) Edit the "includes/STORM/common/db/db.inc" file to include the details for your SQL server. The default options supplied should work for a MySQL installation on localhost. 10) Start by pointing your browser to http://server/path/login.php 11) ICT Team members must have their login name matching the name in the teamMembers table in order for them to see support requests assigned to them. Distribution This software is distributed under the GNU Public License*. A full copy of the license is included in the file "COPYING" in the download .zip file, but I would remind everyone that this software is distributed "WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE." * An exception to this are some of the functions used in the various "functions.inc" files. These are distributed under terms included in the functions.inc files. Bugs, fixes and feedback Please contribute to the development of this software. If you have fixed a problem, or added a feature, please don't keep it to yourself, but email me with your cleverness. I suspect that e-mail will be the best way of continuing to develop this software, but if there is enough demands, I will investigate other communication methods. Send mail to: STORM@tonywhitmore.co.uk