Using PHP-FPM (FastCGI Process Manager) to run web pages and web applications has many advantages, especially when compared to older techniques such as PHP running as an Apache module. One of the most important benefits is that PHP-FPM significantly improves performance and scalability by allowing finer-grained management and optimization of PHP processes. In this way, we can use the server's resources more efficiently, reduce the response time, and our system can remain stable even in the event of heavy traffic. However, over time, the PHP versions of our web applications may become outdated, which the various control panels do not update. In this description, we will see in a few steps how we can easily modify our manual settings so that our websites and web applications also work with the correct PHP version.

In this description, we will install the PHP 8.2 version on a Debian system, set the default PHP versions, set it as an optional PHP version in the ISPConfig control panel, set it in the required storage locations and finally check the PHP operation on a Drupal and a WordPress site.

Monit is a free and open source process and resource monitoring tool that can be used to monitor system processes and resources using a web browser and command line. Monit automatically stops or restarts processes or services if, for example, they use too many resources or behave abnormally. It also sends email alerts about various events.
On this page, we install the Monit system monitor program on a Debian 10 (Buster) perfect server version 1.1, where it was not used before, and then set it up.

Our ISPConfig server handles our websites nicely, however, if we refer to the server's IP address or full hostname in the browser, we do not get the expected result, because in this case the Apache2 Debian Default Page is loaded, which is essentially Apache's "welcome" page. Of course, this is not a tragic mistake, but a beauty mistake. In this description, we will see how we can configure our Apache web server so that the website we want is loaded.

With the help of LAMP systems, we can run dynamic websites on our server or even on our home computer. In this description, we will create a LAMP server on the Debian 11 (Bullseye) operating system, on which the following components will be installed: Apache 2.4.54, MariaDB 10.5.15, PHP 7.4 and phpMyAdmin 5.0.4, UFW firewall.

PHP sessions are global variables that transmit data stored during web visits across multiple pages, i.e., they are not lost when moving from one page to another. PHP accomplishes this by assigning unique IDs to visits (sessions) and creating files in the server-side file structure associated with those IDs in which it stores the data required for the session. The system places these files in a specific directory, usually tmp, which is normally deleted by the garbage collector after a specified time. However, the situation is sometimes not so obvious. This is because if the PHP environment on the server changes, the garbage collector may not be able to delete these obsolete, unnecessary session files. In this description, we will look at how we can use our own solution to ensure that these session files are deleted when the default cleaning system cannot remove them.

PHP is one of the most common server-side scripting languages ​​for building dynamic web pages, making it an essential part of our web server. The latest major version of this, PHP 2020, was released on November 26, 8. In this tutorial, we will look at how to install PHP 8 on an Ubuntu 20.04 (Focal Fossa) LAMP server and a Debian 10 (Stretch) perfect server, and how to you can configure it to work in both systems in the Apache environment.