Suse Linux Enterprise Server (SLES)#
In this article we explain in just a few steps which packages need to be installed and configured.
System Requirements#
The general system requirements apply.
This article refers to Suse Linux Enterprise Server 15. In order to find out which version is used you can carry out the following command:
1 |
|
As system architecture you should use a x86 in 64bit:
1 |
|
x86_64 means 64bit, i386 or i686 only 32bit.
Installation of the Packages#
The default package repositories of Suse Linux Enterprise Server (SLES) already supply the necessary packages to install:
- he Apache web server 2.4
- the script language PHP 7.2 (as of SLES 15 SP 2: PHP 7.4)
- the database management system MariaDB 10.2 (as of SLES 15 SP 2: MariaDB 10.4) and
- the caching server memcached
First of all, you have to activate additional add-ons in Yast:
- Web and Scripting Module
You can check with the following command if both add-ons are activated:
1 |
|
Afterwards the required packages are installed with zypper:
1 2 3 4 5 6 7 8 9 10 |
|
In order to start Apache Webserver and MariaDB during the boot process, the following commands are necessary:
1 2 3 |
|
Then both services are started:
1 2 3 |
|
The HTTP default port 80 is authorized via the firewall. The firewall has to be restarted after the adjustments have been carried out:
1 |
|
Configuration#
The installed packages for Apache web server, PHP and MariaDB already supply configuration files. It is recommended to save changed settings in separate files instead of adjusting the already existing configuration files. Otherwise, any differences to the existing files would be pointed out or even overwritten during each package upgrade. The settings of the default configuration are supplemented or overwritten by user-defined settings.
PHP#
First of all, a new file is created and filled with the required settings:
1 |
|
This file has the following contents:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 |
|
The value (in seconds) of session.gc_maxlifetime
should be the same or greater than the Session Timeout
in the system settings of i-doit.
The date.timezone
parameter should be adjusted to the local time zone (see List of supported time zones).
Afterwards, the Apache web server is restarted:
1 |
|
Apache Webserver#
A new VHost configuration is created from the existing template vhost.template:
1 |
|
In this file the VHost configuration is modified and saved:
1 2 3 4 5 6 7 8 9 10 11 12 13 |
|
i-doit includes differing Apache settings in files with the name .htaccess. The setting AllowOverride All is required so that these settings are taken into account.
With the next step you activate the necessary Apache modules php7, rewrite and mod_access_compat and the Apache web server is restarted:
1 2 3 4 |
|
MariaDB#
Only a few steps are necessary to guarantee that MariaDB provides a good performance and safe operation. However, you should pay meticulous attention to details and carry out these steps precisely. This starts with a secure installation and you should follow the recommendations accordingly. The root user should receive a secure password:
1 |
|
Activate the MariaDB shell so that i-doit is enabled to apply the root user during setup:
1 |
|
The following SQL statements are now carried out in the MariaDB shell:
1 2 3 |
|
Afterwards, MariaDB is stopped. Now it is important to move files which are not required, otherwise the result would be a significant loss of performance:
1 2 3 |
|
A new file is created for the deviating configuration settings:
1 |
|
This file contains the new configuration settings. For an optimal performance you should adapt these settings to the (virtual) hardware:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 |
|
Finally, MariaDB is started with:
1 |
|
Next Step#
Now the operating system is prepared and i-doit can be installed.
Proceed with Setup …