--**** README/index --***-- wiki/documentation ****--
Fork from osTicket 1.9 and 1.10 version series, widely-used open source support ticket system integrates inquiries created via email, phone or web-based simple easy-to-use multi-user interface.
This forks try to commit and merge great feature improvements rejected by original developers.
This guide will use 1.9 release with a Debian or Devuan operating system as example setup, for any other cases, please see the wiki-install2-109-debian-apache.md or the wiki-install2-alpine-hiawatta.md documents.
Any Devuan or Debian release and normal osticket requirements as your read in the wiki-install1.en.md document, but those specific will be used:
- webserver will be lighttpd
- php version will be php 5 series
- mysql/mariadb will be 5.X series
Recent versions of the Debian or Devuan use only php 7 series and mariadb 10 series, those only applies to 1.10 release of simpleticket, for that cases please see wiki-install2-110.en.md
We will use the Lighttpd and MySQL equivalent MariaDB software as http server and database engine, also we will need the mysql module and apart of PHP, the json, imap and GDlib extensions:
apt-get install lighttpd mariadb-server php5 php5-cgi php5-mysql php5-gd php5-json php5-imap
After run that command the mysql/mariadb will ask for a root administration password, please do not forgot!
We need enable the web server modules for php working environment, runs in a console as root:
lighty-enable-mod accesslog cgi dir-listing fastcgi fastcgi-php status
In the extra section (at the end) we will optimize the webserver and php setting depending on some usage.
We need enable the database access for a osticket user and scheme environment so connect to te database engine:
mysql -u root -h localhost -p
By default Devuan/Debian do not allow remote access to database, only localhost
Now we create and perform access to the installation and usage of system software, so in the connection runs:
CREATE USER 'osticket'@'localhost' IDENTIFIED BY '***';
GRANT USAGE ON *.* TO 'osticket'@'localhost' IDENTIFIED BY '***' WITH MAX_QUERIES_PER_HOUR 0 MAX_CONNECTIONS_PER_HOUR 0 MAX_UPDATES_PER_HOUR 0 MAX_USER_CONNECTIONS 0 ;
Create the database and performs usage and privilegies on:
CREATE DATABASE IF NOT EXISTS osticketdb ;GRANT ALL PRIVILEGES ON osticket . * TO 'osticket'@'localhost';
The default htdoc web root directory will be at /var/www/html but as professional install we
not put directly the files here, avoid provide easy cracking for alienate users, due our osticket
are good patched we will use the aliasing technique. Runs in a console as root:
cd /opt/; wget https://gitlab.com/venenux/simpleticket109/repository/master/archive.tar.bz2
and then uncompress and rename to proper isntall:
tar -xvvzf osticket.tar.gz;mv simpleticket* osticket
Also if prefer lasted can directly download all files extracted from git as:
cd /opt/; git clone https://gitlab.com/venenux/simpleticket109.git osticket
Now files must be prepared the ost-config and file permission:
cp /opt/osticket/include/ost-sampleconfig.php /opt/osticket/include/ost-config.php
chown -R www-data:www-data /opt/osticket/
Remenber that we perform a professional install, so we configure an alias in /opt/osticket so
runs as root the following command to perfomr the required configuration alias in web server:
cat <<EOF > /opt/osticket/99-osticket.conf
alias.url += ( "/osticket/" => "/opt/osticket/" ),
$HTTP["url"] =~ "^/osticket($|/)" {
dir-listing.activate = "disable"
}
EOF
then we must protect the file from alienate visitors:
chmod 640 /opt/osticket/99-osticket.conf
Now at this point we can call the setup install process in the web browser.
Now open your browser and input the server ip address and subpath osticket by example:
and the software will redirect to the setup process to finish the installation:
- If the setup script spots any configuration errors then it will not allow you to continue until the errors are corrected.
- If everything checks out, you will be presented with a form to fill in the required information.
Here all the checks must be provided as marcked, but for something there the commands that must run as root to solve:
- IMAP: with
apt-get install php5-imap - Gdlib extension:
apt-get install php5-gd - PHP XML extension:
apt-get install php5-common php5-cgi - PHP XML-DOM extension:
apt-get install php5-common php5-cgi - Mbstring extension:
apt-get install php5-mcrypt - PHP JSON extension:
apt-get install php5-common php5-json - Phar extension:
apt-get install php5-common php5-cgi
The package php5-common refers and means that the module/extension are provided as built-in.
System setting section
Here the firts section need a name for the heldesk site, and the system main email, if do not have an email system, dont worry, can give a false email but must be valid type.
Admin user section
The most important fields here are admin username and admin password, rest of fields are for misc information. All the fileds are mandatory. Do not forgoet the admin username and admin passowrd, will be used for accesss.
Database settings section
Please fill the database user, name and address, already defined in the preconfigurated steps,
- Fill database username and password, we previously configured as "osticket" the username
- The database name must be entered, we previously configured as "osticketdb" the sheme
- The prefix must be remain same, due as we previously configured as "ost" the prefix
Note that the installer performs basic configuration required to get osTicket up and running. Further configuration is required, post-install, to make the system fully functional.
Config file permission:
Now at isntall change permission of ost-config.php to remove write access as root runs:
chmod 0640 /opt/osticket/include/ost-config.php
also the setup install directory must be denied from outside with this command as root:
chmod 0600 /opt/osticket/setup
Now with last command, your osTicket installation has been completed successfully.
Your next step is to fully configure your new support ticket system by the web interface. for that please read the wiki-configure-index.md and then finally the wiki-usage-index.md.