[BlueOnyx:18489] YUM updates 2015-10-12 (php.d related updates)

[Michael Stauber]

Hi all,

I just published a batch of YUM updates for all BlueOnyx versions:

base-apache & base-vsite:
===========================

We do have a few new web applications for BlueOnyx in the pipe that soon
will be available in the BlueOnyx shop. However, some of these required
some fine tuning of the handlers that set up the document root of Vsites
and the PHP handling in particular.

So the really new feature is that from now on all Vsites will have a
"php.d" directory.

Example:

/home/sites/<site>/php.d/

This directory will automatically be added for all Vsites. Either during
Vsite creation, CCEd constructor or CCEd handler runs. Normally this
directory will be empty and the permissions of it will prevent that a
siteAdmin can upload or create files in it. This directory is reserved
for applications or serverAdmin induced changes.

Purpose of the php.d directory:
--------------------------------

On 5209R we do have 4 different PHP implementations (DSO, mod_ruid2,
suPHP, PHP-FPM) which store their PHP related configuration in three to
eight different places. No kidding on that one, as it depends on how
many PHP versions you have installed on a 5209R.

Not all PHP related config options are stored in CODB. There are some
config options that are inherited through the php.ini and which were
(before this update) not all changeable in a per Vsite fashion.

The php.d directory of Vsites intends to allow easy changes to this. If
you (or a web application) put a <name>.ini file into a Vsite's php.d
directory, then the contends will be parsed and will be incorporated
into the PHP configuration of the Vsite in question.

Example:

You have a /home/sites/<site>/php.d/roundcube.ini with the following
contends in it:

php_flag display_errors Off
php_flag log_errors On
php_value upload_max_filesize 5M
php_value post_max_size 6M
php_value memory_limit 64M

In that case after a cced.init restart the PHP configuration of this
Vsite will inherit these changes. Regardless of the method or
implementation of PHP you use:

DSO or DSO + mod_ruid2:
-------------------------

The Apache <VirtualHost> container of this Vsite will inherit these
modifications.

suPHP:
-------

The custom php.ini of the Vsite will inherit the settings from the php.d
ini file(s) of this Vsite.

PHP-FPM:
---------

The PHP-FPM pool config of the Vsite will inherit the changes and
PHP-FPM is restarted.


This change allows us to seamlessly adapt the PHP settings of virtual
sites with all options that any third party web application might have.
And it allows us (and you) to do so without any dirty hacks. In the past
we used the siteX.include files of Apache for this, which isn't really
the best way to do it. This here should work a lot better as it also
functions with suPHP and/or PHP-FPM enabled.


base-email (5207R, 5208R, 5209R)
=================================

Small bugfix to Email Server Alias handling. Which threw an error if
Auto-DNS was enabled and the entered alias was the same as the FQDN
minus the hostname.


-- 
With best regards

Michael Stauber