This article describes which packages need to be installed and configured.
The general system requirements apply.
This article refers to RHEL in version 8.x
To determine which version is used, this command can be executed on the console:
As system architecture a x86 in 64bit should be used:
x86_64 stands for 64bit,
i686 only for 32bit.
There are other operating systems that are closely related to RHEL, such as the open replica CentOS and Fedora, which is maintained by Red Hat. However, only RHEL is officially supported.
Installation of the packages
On a system that is up-to-date
- the Apache web server 2.4,
- the script language PHP 7.4,
- the database management system MariaDB 10.4
- the caching server memcached
installed. However, the current version 8.x of RHEL only contains obsolete packages that do not meet the system requirements. It is therefore necessary to install current packages from other repositories. Caution: Third-party repositories can endanger the stability of the operating system.
At first the first packages are installed from the default repositories:
For PHP, the current Extra Packages for Enterprise Linux (EPEL) is included:
After the repository has been included, the possible versions are initialized and then the desired version can be activated (we use PHP 7.3 here):
The PHP packages are then installed:
Furthermore, RHEL only offers outdated distribution packages for MariaDB. Therefore we use the official third party repository of MariaDB:
Die Datei erhält folgenden Inhalt:
After that the packages are installed (Note: MariaDB needs the additional package boost-program-options for a clean installation):
These commands are required to start the Apache web server and MariaDB at boot time:
Both services are then started:
Furthermore, the default port 80 of HTTP is allowed through the firewall. This must be restarted after the adjustment:
The installed packages for Apache Webserver, PHP and MariaDB already come with configuration files. It is recommended to store different settings in separate files instead of adapting the existing configuration files. Each time you upgrade the package, the different settings will be changed or overwritten. The settings of the standard configuration will be supplemented or overwritten by the user-defined ones.
First a new file is created and filled with the necessary settings:
This file receives the following content:
The value (in seconds) of session.gc_maxlifetime should be greater than or equal to the session timeout in the i-doit system settings.
The parameter date.timezone should be adjusted to the local time zone (see list of supported time zones).
The Apache Web server is then restarted:
Apache web server
The default vhost is retained and added. A new file is created and edited:
In this file the supplementary one is stored:
i-doit provides different Apache settings in files named .htaccess. In order for these settings to be taken into account, the setting AllowOverride All is required.
The next step is to restart the Apache web server:
For Apache to have read and write permissions in the future installation directory of i-doit, this must be allowed by SELinux:
In order for MariaDB to perform well and run safely, there are a few steps that need to be done meticulously. This starts with a secure installation. The recommendations should be followed. The root user should be given a secure password:
To allow i-doit to use the root user during setup, call the shell of MariaDB:
The following SQL statements are now executed in the MariaDB shell
MariaDB is then stopped. It is important to move unneeded files (otherwise you risk a significant performance loss):
A new file is created for the different configuration settings:
This file contains the new configuration settings. For optimal performance, these settings should be adapted to the (virtual) hardware:
Finally, MariaDB is started:
The operating system is now prepared so that i-doit can be installed: