PHP - Revision history

Johnno: /* Keep your PHP custom settings and tweaks separate */

2025-05-07T00:52:36Z

Keep your PHP custom settings and tweaks separate

Johnno: Update to 24.04 LTS and PHP 8.3

2025-05-07T00:38:03Z

Update to 24.04 LTS and PHP 8.3

Johnno: /* Deny access to git repositories */

2023-05-19T21:27:09Z

Deny access to git repositories

Johnno: /* Deny access to git repositories */

2023-05-19T21:17:31Z

Deny access to git repositories

Johnno: /* Set up Apache */

2021-09-01T11:08:51Z

Set up Apache

Johnno: /* Prerequisites */

2021-08-20T01:38:43Z

Prerequisites

Johnno at 01:21, 20 August 2021

2021-08-20T01:21:16Z

Johnno: /* Prerequisites */

2021-08-15T22:19:38Z

Prerequisites

Johnno at 22:14, 15 August 2021

2021-08-15T22:14:55Z

Johnno: /* Prerequisites */

2021-08-13T12:47:29Z

Prerequisites

@@ Line 87: / Line 87: @@
   opcache.enable=1
-Then we add a symbolic link in the {{code|conf.d}} directory where you need it, for example:
+Then we add a symbolic link in the {{code|conf.d}} directory where it is needed, for example when new versions of PHP are released.
   ln -s /etc/php/local/php.ini /etc/php/8.3/fpm/conf.d/99-local.ini

@@ Line 1: / Line 1: @@
-: ''These instructions assume Ubuntu LTS (currently 20.04, c. August 2021) and are easily adapted to a Docker or other container definition, Ansible playbook, etc.''
+: ''These instructions assume Ubuntu LTS (24.04, c. May 2025) but are easily adapted to Debian, a Docker or other container definition, Ansible playbook, etc.''
-There's a lot of talk about using Nginx instead of Apache, and for some things it's probably easier to configure or maintain, especially if you're writing IaC, but some things still assume or prefer Apache, particularly in PHP land. WordPress and NextCloud are example PHP applications that want to modify their {{code|.htaccess}} files in-place, for example to keep up with security developments.
+There's a lot of talk about using Nginx instead of Apache, and for some things it's probably easier to configure or maintain, especially if you're writing IaC, but some things still assume or prefer Apache, particularly in PHP land. [[WordPress]] and [[NextCloud]] are example PHP applications that want to modify their {{code|.htaccess}} files in-place, for example to keep up with security developments.
 Perhaps part of the reason for the currently fashionable dim view of Apache's performance is that PHP is often run in production using mod-php, which ''at best'' should only be used on a development workstation, if at all. Apart from being incompatible with HTTP/2, it is a CPU and memory hog, since it can only run using Apache's horribly inefficient prefork multi-process management (MPM). Apache has several modules for dealing with MPM, but can only have one MPM module enabled at a time. Other much better, multithreaded, more efficient and fast MPM modules have been around for nearly two decades, and since version 5.4 of PHP (late 2011) we can use Apache's Event MPM and FastCGI modules with PHP-FPM. More information is available on the Apache [https://cwiki.apache.org/confluence/display/httpd/PHP-FPM httpd wiki].
@@ Line 11: / Line 11: @@
 Install at least the following packages:
-  sudo apt install apache2 libapache2-mod-fcgid php-fpm php7.4-{fpm,opcache}
+  sudo apt install apache2 libapache2-mod-fcgid php-fpm php8.3-{fpm,opcache}
 You'll need various PHP extensions to host a real PHP application; for example [[NextCloud]] requires PHP composer, [[PostgreSQL]], Redis, and Dehydrated is useful for managing [[Letsencrypt]] SSL certificates.
   sudo apt install php-{imagick,redis} \
-      php7.4-{bcmath,bz2,curl,gd,gmp,intl,json,mbstring,pgsql,soap,tidy,xmlrpc,xsl,zip} \
+      php8.3-{bcmath,bz2,curl,gd,gmp,intl,json,mbstring,pgsql,soap,tidy,xmlrpc,xsl,zip} \
       composer postgresql redis-server dehydrated
@@ Line 23: / Line 23: @@
 Enable the required Apache configurations and modules:
-  a2enconf php7.4-fpm
+  a2enconf php8.3-fpm
   a2enmod dir env headers http2 mpm_event proxy_fcgi rewrite setenvif ssl
   systemctl restart apache2
@@ Line 68: / Line 68: @@
 == Configure PHP ==
-The configuration for PHP code hosted by Apache using PHP-FPM is located under {{code|/etc/php/7.4/fpm}}.
+The configuration for PHP code hosted by Apache using PHP-FPM is located under {{code|/etc/php/8.3/fpm}}.
 You will not be able to use mod-php {{code|php_value}} directives in Apache configuration; either try and do without, or set environment variables instead.
@@ Line 76: / Line 76: @@
 === Keep your PHP custom settings and tweaks separate ===
-Since Debian now moves files around with each new version of PHP, you can keep your customisations to the {{code|php.ini}} file in a local configuration. For example, instead of editing {{code|/etc/php/7.4/fpm/php.ini}}, put these settings in {{code|/etc/php/local/php.ini}}:
+Since Debian/Ubuntu now moves files around with each new version of PHP, you can keep your customisations to the {{code|php.ini}} file in a local configuration. For example, instead of editing {{code|/etc/php/8.3/fpm/php.ini}}, put these settings in {{code|/etc/php/local/php.ini}}:
   ; /etc/php/local/php.ini
@@ Line 89: / Line 89: @@
 Then we add a symbolic link in the {{code|conf.d}} directory where you need it, for example:
-  ln -s /etc/php/local/php.ini /etc/php/7.4/fpm/conf.d/99-local.ini
+  ln -s /etc/php/local/php.ini /etc/php/8.3/fpm/conf.d/99-local.ini

@@ Line 35: / Line 35: @@
   ''# /etc/apache2/conf-available/deny-git.conf''
   <LocationMatch "/\.(git|hg|bzr|svn|cvs|tag|ht)">
-    Order deny,allow
+    # Old apache:
-    deny from all
+   # Order deny,allow
   </LocationMatch>

@@ Line 34: / Line 34: @@
   ''# /etc/apache2/conf-available/deny-git.conf''
-  RedirectMatch 404 "/\.(git|hg|bzr|svn|cvs|tag|ht)"
+  <LocationMatch "/\.(git|hg|bzr|svn|cvs|tag|ht)">
 Then enable it with:

@@ Line 24: / Line 24: @@
   a2enconf php7.4-fpm
-  a2enmod dir env headers mpm_event proxy_fcgi rewrite setenvif ssl
+  a2enmod dir env headers http2 mpm_event proxy_fcgi rewrite setenvif ssl
   systemctl restart apache2

@@ Line 9: / Line 9: @@
 == Prerequisites ==
-Install some stuff first. To support [[NextCloud]] for example, this Apache PHP recipe also uses [[PostgreSQL]], Redis, FastCGI with PHP FPM, and Dehydrated for managing [[Letsencrypt]] SSL certificates.
+Install at least the following packages:
-  sudo apt install apache2 libapache2-mod-fcgid \
+  sudo apt install apache2 libapache2-mod-fcgid php-fpm php7.4-{fpm,opcache}
-    php7.4-{bcmath,bz2,curl,gd,fpm,gmp,intl,json,mbstring,opcache,pgsql,soap,tidy,xmlrpc,xsl,zip} \
-    php-{fpm,imagick,redis} composer dehydrated postgresql redis-server
+You'll need various PHP extensions to host a real PHP application; for example [[NextCloud]] requires PHP composer, [[PostgreSQL]], Redis, and Dehydrated is useful for managing [[Letsencrypt]] SSL certificates.
 == Set up Apache ==

@@ Line 3: / Line 3: @@
 There's a lot of talk about using Nginx instead of Apache, and for some things it's probably easier to configure or maintain, especially if you're writing IaC, but some things still assume or prefer Apache, particularly in PHP land. WordPress and NextCloud are example PHP applications that want to modify their {{code|.htaccess}} files in-place, for example to keep up with security developments.
-Perhaps part of the reason for the currently fashionable dim view of Apache's performance is that PHP is often run in production using mod-php, which ''at best'' should only be used on a development workstation, if at all. Apart from being incompatible with HTTP/2, it is a CPU and memory hog, since it can only run using Apache's horribly inefficient prefork multi-process management (MPM). Apache has several modules for dealing with MPM, but can only have one MPM module enabled at a time. Other much better, multithreaded, more efficient and fast MPM modules have been around for nearly two decades, and since version 5.4 of PHP we can use Apache's Event MPM and FastCGI modules with PHP-FPM.
+Perhaps part of the reason for the currently fashionable dim view of Apache's performance is that PHP is often run in production using mod-php, which ''at best'' should only be used on a development workstation, if at all. Apart from being incompatible with HTTP/2, it is a CPU and memory hog, since it can only run using Apache's horribly inefficient prefork multi-process management (MPM). Apache has several modules for dealing with MPM, but can only have one MPM module enabled at a time. Other much better, multithreaded, more efficient and fast MPM modules have been around for nearly two decades, and since version 5.4 of PHP (late 2011) we can use Apache's Event MPM and FastCGI modules with PHP-FPM. More information is available on the Apache [https://cwiki.apache.org/confluence/display/httpd/PHP-FPM httpd wiki].
 With PHP processes being handled much more efficiently, and by being able to finally enable HTTP/2 in Apache, it all actually goes like the clappers.

@@ Line 35: / Line 35: @@
   a2enconf deny-git
-  systemctl restart apache2
+  systemctl reload apache2
 === Add a virtual host ===