Basic Nginx Server's PHP option.

https://github.com/OpenMediaVa…nx.d/90-nginx-server#L158

checkout source code

enable_php option means

set $socket "unix:/var/run/fpm-$php_pool_ref.sock";

php_use_default_config means

{
location ~ \.php$ {
include snippets/fastcgi-php.conf;
fastcgi_pass $socket;
}

$php_pool_ref is pool you selected in PHP-FPM pool option
you can manage your fpm pool in Pools tab

Zitat von tinh_x7

Ok. From what I understand is if I use the php-fpm-pool, then it will set the socket as $socket.
The $socket is then pass as a variable to php_use_default_config.
But the php_use_default_config is also allow me to use my own socket if it's unchecked.

if I use the php-fpm-pool -> if I use `Enable php` option

php_use_default_config option control how nginx handle .php extenstions
for example, if you want to use .ppp extenstions
turn off this option, and write

{
location ~ \.ppp$ {
include snippets/fastcgi-php.conf;
fastcgi_pass $socket;
}

if you set vhost extra options like

fastcgi_pass unix:/var/run/php5-fpm.sock

you don't need to enable both `enable php` and `default config`
By default, openmediavault have /var/run/php5-fpm which is not seen omv-nginx pools tab (hidden)
checkout

vim /etc/php5/fpm/pool.d/www.conf

Generally, seperating socket is recommended for security reason
Also if one socket is blocked then sites using that socket will be also blocked

there are two sockets by default in omv
one is /var/run/php5-fpm-openmediavault-webgui.sock (for openmediavault website)
the other is /var/run/php5-fpm.sock (this is installed by debian php package)
so, if you uses php5-fpm socket, omv site is already seperated

I don't think you don't have to seperate anymore for personal uses