Re: syntax of configuration file
| From: | Jérôme Loyet | Date: | Wed, 09 Dec 2009 23:12:03 +0000 |
| Subject: | Re: syntax of configuration file | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-46391@lists.php.net to get a copy of this message | ||
Le 9 décembre 2009 23:25, Tjerk Anne Meesters <datibbaw@php.net> a écrit :
> Hi,
>
> ini files can be split, so it doesn't all have to be inside one
> monolithic php.ini
is there a way to include files ?
include /etc/php-fpm/*.conf ? with one file per worker for example ?
I think adding include to ini should not be a problem if it's not already done.
>
> I agree that repetition doesn't look nice; it would be nice to have
> something like:
>
> [fpm.worker.worker1]
> listen = 127.0.0.1:1900
> uid = webservice
>
> Etc.
>
> Didn't really pay attention to those pool settings, but I guess those
> could be sections as well such as [fpm.pool.pool1]
pool and worker are the same ... it's pool of workers in fact :)
The simpliest way is to have only one level of section
[fpm] ; for global conf
pid = /var/run/php-fpm.conf
[fpm.worker.default]
listen_address = 127.0.0.1:9000
listen_ower = www ; in case of using unix socket instead of inet
pm = static ; or dynamic
max_children = 15
start_servers = 1; only for dynamic
chroot = /var/www/pool1
user = www
...
[fpm.worker.admin]
listen_address = 127.0.0.1:9001
user = www_admin
...
>
>
>
> On 12/10/09, Jérôme Loyet <jerome@loyet.net> wrote:
>> Le 9 décembre 2009 20:56, Michael Shadle <mike503@gmail.com> a écrit :
>>> 2009/12/9 Jérôme Loyet <jerome@loyet.net>:
>>>
>>>> do you mean that it would be included in the global php.ini file ? I
>>>> never imagine that. For me it's an independant conf file
>>>> (/etc/php-fpm.conf for example).
>>>
>>> correct. I don't see any reason for a different configuration file anymore
>>>
>>
>> In my mind, daemon options (php-fpm) and php conf (extensions and
>> global php conf) are différent things. Having all in the same file
>> will be harder to use in a mutualized environment where several
>> instances php-fpm running. And the goals of the two files or not the
>> same. Moreover having a complex array syntax is, as I said before,
>> hard to read and write.
>>
>> what are thoughts from other on this point ?
>>
>> --
>> PHP Internals - PHP Runtime Development Mailing List
>> To unsubscribe, visit: http://www.php.net/unsub.php
>>
>>
>
>
> --
> --
> Tjerk
>