(08-19-2010 05:08 AM)RatS Wrote: The required changes for the engine must be quite simple:
ispcp-dmn-mngr needs to copy the file to the right directory (/var/www/fcgi/{DMN-NAME}/php5/ I guess). How to do this just check how the php.ini-File for users is created.
Additionally you might change the Makefile inf the config dir and add the template for the php-fpm.ini. If you need to replace variables, you can do this in the ispcp-dmn-mngr, too.
If you succeeded, please create a ticket with as most complete patch.
It looks really interesting for us, too.
Thanks for the suggesting. On questions we will help you!
Unfortunatly it's not that easy, since the domain mgr has to take care of the php5-fpm.conf file (configuration for the fpm deamon), which defines the settings and socket for every single pool (domain in our case).
It looks like this:
Code:
log_level = debug
daemonize = yes
[admin.debian.example.com]
listen = /var/lib/apache2/fastcgi2/admin.debian.example.com
user = vu2000
group = vu2000
pm = dynamic
pm.max_children = 50
pm.start_servers = 1
pm.min_spare_servers = 1
pm.max_spare_servers = 2
pm.max_requests = 500
[test1.example.com]
listen = /var/lib/apache2/fastcgi2/test1.example.com
user = vu2001
group = vu2001
pm = dynamic
pm.max_children = 50
pm.start_servers = 1
pm.min_spare_servers = 1
pm.max_spare_servers = 2
pm.max_requests = 500
[test2.example.com]
listen = /var/lib/apache2/fastcgi2/test2.example.com
user = vu2002
group = vu2002
pm = dynamic
pm.max_children = 50
pm.start_servers = 1
pm.min_spare_servers = 1
pm.max_spare_servers = 2
pm.max_requests = 500
As you can see there is a section for every domain, so the domain manager needs to adjust it on domain changes (add/delete). Quite similar to way ispcp handles vhost "entrys" at the moment.
Further more, fpm isn't capable of handling different php.ini files atm. Though it's possible to override/set ini settings pool wise. Which should be sufficient.
Cheers,
Nikolas
Ticket created:
http://isp-control.net/ispcp/ticket/2426