IIS 7 - FastCGI Module

Re: Separate PHP.ini for each website?

v-edsojo — Thu, 11 Jun 2009 18:53:00 GMT

Hi, here is an article that explains how to work with differents php.ini in IIS7:
http://eng.eduardosojo.com/differents-phpini-config-file-for-each-websit

Regards,

Re: Separate PHP.ini for each website?

v-edsojo — Wed, 22 Apr 2009 16:44:43 GMT

You´re right Kanwal...

Part of the explanation on iis.net (http://rurl.me/ws85):

Specifying php.ini location

When the PHP process starts it determines the location of the configuration php.ini file by using various settings. The PHP documentation provides detailed description of the PHP start up process. Note that one of the places where PHP process searches for php.ini location is the PHPRC environment variable. If PHP process finds a php.ini file in the path specified in this environment variable then it will use it, otherwise it will revert to default location of php.ini. This environment variable can be used to allow hosting customers to use their own versions of php.ini files.

For example if there are two websites: website1 and website2; located at the following file paths: C:\WebSites\website1 and C:\WebSites\website2 then the php-cgi.exe process pools in the <fastCgi> section of applicationHost.config can be configured as below:

This way website1 can have its own version of php.ini in the C:\WebSites\website1, while website2 can have its own version of php.ini located in C:\WebSites\website2. This configuration also ensures that if there is no php.ini found in location specified by PHPRC environment variable then PHP will fall back to using the default php.ini file located in the same folder where php-cgi.exe is located.

--------------------------------------------------------------------------------------------------------------------------------------

Re: Separate PHP.ini for each website?

ksingla — Tue, 21 Apr 2009 21:51:38 GMT

Instead of using -c switch, you can use PHPRC environment variable to specify the path from where ini file should be picked. Read how to set per site ini file here. Search for PHPRC.

Thanks,
Kanwal

Re: Separate PHP.ini for each website?

v-edsojo — Tue, 21 Apr 2009 20:11:08 GMT

Hi.

The problem is that for php compiler you have to use is -c <php.ini_file_path> but it only works for php.exe not for php-cgi.exe

I had to use php.exe instead of php-cgi.exe and in my website´s handler mapping i configured php extension using "C:\<php_root>\php.exe"|-c <new_php.ini_file_path>

You can also test php-cgi by console putting the following command:

C:\<php_root>\php-cgi -c <php.new_ini_file_path>

If it works, it will works on IIS.

Re: Separate PHP.ini for each website?

ksingla — Tue, 21 Apr 2009 17:34:58 GMT

Hi,

FastCGI section has fullPath and arguments as key. Both values combined but separated by '|' (pipe character) is treated as key. You need to specify this key in handlers section. In you case, you will give "c:\php\php-cgi.exe|-cd:\website2" as the scriptProcessor in handler mapping.

Thanks,
Kanwal

Separate PHP.ini for each website?

brianlewis — Tue, 21 Apr 2009 15:35:03 GMT

I'm trying to setup a website to use a different php.ini from the default that most websites use on the server. I can go to Internet Service Manager, SERVERNAME, FastCGI Settings, click Add Application, I use

Full Path : c:\php\php-cgi.exe

Arguments : -cd:\website2\

This is telling php-cgi to find the ini file in d:\websites2

The problem I'm having is I then go to the website, go to mappings, add the ModuleMapping of FastCGIModule but how do I tell it to use the unique configuration I gave it above?

Only idea I can come up with is to copy php-cgi.exe to a unique folder or name it something else like php-website2.exe, but then I would have to remember to update that file each time I updated php to the latest version unless I used mklink to create a symbolic link.

Is that the only way to differentiate the mappings between the website and the applicationhost.config fastcgi mappings, thru using a unique filename or path?