-------------------------------------------------------------------------
now you must install ispconfig, if you didn't have it or you modify it by own
-------------------------------------------------------------------------

-------------------------------------------------------------------------------------------------------
ispconfig copy this to /var/www/web*/ if you activate php for this web, but you must modify ispconfig:
-------------------------------------------------------------------------------------------------------

modify ISPConfig
you must patch the config.lib.php

Code:

cd /root/ispconfig/scripts/lib

then you must patch config.lib.php with the patch file in the attachemend.
Copy the patch file into /root/ispconfig/scripts/lib.

Code:

patch config.lib.php < fcgi_patch.txt

By the first php activate for a web Account, it will be create a .php-fcgi-starter for this user. If you wish to modify php for this user, then you must create a new php.ini for this user or change it for all. And edit the fast-cgi-starter script for this user.
php_admin_flag in the apache config didn't run and the php_sage_mod button in ispconfig didn't act after the patch/ with fastcgi!

I'm pleased to get feedback and better solutions
and I hope that fastcgi find a way into the default installation of ispconfig

Hi!
I build a new suexec, because it is easier to add a new web account in ispconfig. and it make it easier to edit the script as root.
but you can also set the immutable-bit in /root/ispconfig/scripts/lib/config.lib.php. then ISPC. set it automatically after copy the php-fcgi-starter into the user folder.

all web accounts with php have a .php-fcgi-starter script. there can you set some paramaters for fcgi/php (like a php.ini).
in the vhost for this webs ispconfig create a ScriptAlias to the startscript.
like this:

Code:

ScriptAlias /php/ /var/www/web1/

and in the fastcgi config define the php start script with this parameter:

Code:

Action php-fastcgi /php/.php-fcgi-starter

so you start a fcgi-server for the different vhosts.

for example:
fastcgi start it for web1 in /var/www/web1/.php-fcgi-starter
and web2 in /var/www/web2/.php-fcgi-starter

It is great an more secure to use php-fcgi rather than the usual php. That's the reason why I want to use fcgi. I dont realy understand how to use and define
the "FastCgiServer" for different vhosts (That's me second question) because php-fcgi is still working without a defined "FastCgiServer"?

for all those preferring to use FastCgi I want to supply my little tweaked version of this great post (thx Tosser).

Also if you've got problems to execute the outdated patch this could help you.

The following instructions are only about patching ISPConfig to support FastCgi.

I added

- support that every Vhost will automatically gets copied his own php.ini file into webroot directory.
- new var directory to Vhost that contains sessions and uploaded_tmp files

Please note:

- use on own risk
- only apache2 support (you can easily add apache1)
- only FASTCGI-Support (can't be switched)
- You've to controll the config.lib.php and make your custom changes (CHOWN: Webserver-User, CHMOD: your rights!)
- If you want to regenerate the .php.ini // .php-fcgi-starter // var folder - just delete them and run a vhost change.