How do I create custom php.ini files for each virtual host?

Question

I've installed EasyPHP WAMP for local development only (I'm not hosting any websites).

Is there a way to set custom php settings for separate virtual hosts?

Currently and out-of-the-box, the php.ini file is loaded from: C:\Program Files (x86)\EasyPHP-DevServer-14.1VC11\binaries\php\php_runningversion\php.ini It would be nice if, say, I could drop in a custom php.ini file into the virtual host directory to override settings in the original php.ini This way, I could better emulate a production server's environment on a per-site basis.

I've seen this work with online hosting accounts. But I can't figure out how to make this work on my machine.

Jessiejessika

Honestly, the best way I've found for emulating production environments is to use Vagrant. You're probably not using EasyPHP WAMP in production, are you? Or Windows for that matter. In these cases, it is best to use a VM with the same OS as your production servers. To manage these VMs, Vagrant makes this very easy. – Kareenkarel

Are we talking about PHP as Apache module? Or PHP as CGI or FastCGI? – Anaemia

I have to agree with @Kareenkarel that using a VM to emulate your target environment is best practice. However, if you really want custom settings, try using the .htaccess. It may need some tweaking on Windows boxes, because usually you need to do some odd settings in order to get it working (And don't forget to set: AllowOverride All in your (default) vhost config). – Turbellarian

@ÁlvaroG.Vicario I'm not sure how to tell? I don't think it's fastCGI... – Jessiejessika

How to tell? phpinfo() is one way. I suspect you are running it as Apache module and you are simply not aware that you can use .htaccess files. – Anaemia

Thanks, I didn't know that! If you want to make it an answer I'll mark it as accepted. – Jessiejessika

My answer is late, but could be useful. – Studnia

Answer 1

Using custom php.ini files is pretty straighforward for CGI/FastCGI based PHP installations but it isn't feasible when running PHP as Apache module (mod_php) because the whole server runs a single instance of the PHP interpreter.

My advice:

• Set from PHP itself as many settings as you can:

  ini_set('memory_limit', '16M');
  date_default_timezone_set('Europe/Madrid')
  ...
  

  In other words, directives that can be changed at runtime.

• Set the rest of stuff from per-directory Apache setting files (aka .htaccess):

  php_flag short_open_tag off
  php_value post_max_size 50M
  php_value upload_max_filesize 50M
  

  i.e., settings that need to be defined before the script starts running

Please have a look at the Runtime Configuration for further details.

Sometimes, you'll actually need different settings in development and production. There're endless ways to solve that with PHP code (from creating a boolean constant from the $_SERVER['HTTP_HOST'] variable to just having a config.php file with different values) but it's trickier with .htaccess. I normally use the <IfDefine> directive:

<IfDefine DEV-BOX>
    #
    # Local server directives
    #
    SetEnv DEVELOPMENT "1"

    php_flag display_startup_errors on
    php_flag display_errors on
    php_flag log_errors off
    #php_value error_log ...
</IfDefine>
<IfDefine !DEV-BOX>
    #
    # Internet server directives
    #
    php_flag display_startup_errors off
    php_flag display_errors off
    php_flag log_errors on
    php_value error_log "/home/foo/log/php-error.log"
</IfDefine>

... where DEV-BOX is a string I pass to the local Apache command-line:

C:\Apache24\bin\httpd.exe -D DEV-BOX

If you run Apache as service, the -D DEV-BOX bit can be added in the Windows registry, e.g.:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Apache2.4\Parameters\ConfigArgs

---

Related: Find out how PHP is running on server (CGI OR fastCGI OR mod_php)

Trowbridge

Answer 2

Developing Multiple Domains on One Machine?

Embedding php.ini settings in the httpd-vhost.conf, typically found in your server root under conf/extra/, is a great way to solve this common problem. If you never knew you could do this, see the PHP.net Manual under How To Change Configuration Settings. This will solve the pesky include_path problem, without adding configuration code to your bootstrapping code or anything else.

Of course, to use this effectively as localhost, you would need to make copies of a <VirualHost> block and configure each accordingly. Then, comment out all virtual host blocks except the one that you want to use!

Alternatively, one could start Apache with the -f option to point the server daemon to a different httpd.conf upon starting. Each httpd.conf would require an "if module block," such as and <IfModule phpx_module> block. Be sure to remember to account for Apache logging!

httpd -f /usr/local/apache2/conf/domains/fooDomain.conf

httpd -f /usr/local/apache2/conf/domains/barDomain.conf

Virtual Host Block With php.ini statements.

<VirtualHost 127.0.0.1:80>
    UseCanonicalName On
    ServerName localhost:80
    ServerAdmin you@localhost        
    CustomLog "/var/www/someDomain.com/data/logs/httpd_access_log" common
    ErrorLog "/var/www/someDomain.com/data/logs/httpd_error_log"
    LogLevel warn
    DocumentRoot "/var/www/someDomain.com/public"

    <Directory "/var/www/someDomain.com/public">
        # disable directory listing
        Options -Indexes +FollowSymLinks
        AllowOverride FileInfo
        Require all granted
    </Directory>

    <IfModule alias_module>
        # Alias /webpath /full/filesystem/path
        ScriptAlias /cgi-bin/ "/var/www/someDomain.com/scripts/cgi-bin/"
    </IfModule>

    <IfModule php7_module>
        # Use php7_module in opening statement above if on PHP 7+

        # Domain specific PHP configuration options.
        # The Apache process user must own any of the following directories.

        php_admin_value include_path "/var/www/someDomain.com/application/controllers:/var/www/someDomain.com/application/models:/var/www/someDomain.com/application/views"

        # Errors and Logging
        php_admin_flag display_startup_errors off
        php_admin_flag display_errors off
        php_admin_flag html_errors off
        php_admin_flag log_errors on
        php_admin_value error_log "/var/www/someDomain.com/data/logs/php_error_log"

        # File Related
        php_admin_flag file_uploads on
        php_admin_value upload_tmp_dir "/var/www/someDomain.com/data/uploads"
        php_admin_value upload_max_filesize 10M
        php_admin_value max_file_uploads 5

        # Sessions
        php_value session.save_handler "files"
        php_value session.save_path "/var/www/someDomain.com/data/sessions"

        # Caching
        php_value soap.wsdl_cache_dir "/var/www/someDomain.com/data/cache/sopa.wsdl"
    </IfModule>
</VirtualHost>

If you could use the %{SERVER_NAME} variable in conjunction with the <IfModule phpx_module> blocks to form a compound conditional, you could have just one httpd.conf`, or include a extra/php.conf with all the domain specific PHP.ini settings (in blocks, also). However, as long as "localhost" is the domain target, it will not do what you want. Thus, my answer in the virtual host block above.

Studnia

Answer 3

Simple way to use custom php.ini file for vhost using Fast CGI is to copy the php.ini into a folder in the host like "customini".

After that to your vhost directive and add this simple line :

FcgidInitialEnv PHPRC "/path_to_your_custom_ini_dir_for_this_vhost/"

BE SURE TO HAVE / to your path no \, (it won't work with \)

Restart Apache.

That's all!

Full sample (on Windows Server here) :

 <VirtualHost *:80>
    DocumentRoot "C:/APACHE/htdocs/vhost/myvhost"
    ServerName www.vhost.com
    FcgidInitialEnv PHPRC "C:/APACHE/customini/myvhost/"
 </VirtualHost>

Aegis

Answer 4

Several commentors have mention Vagrant which is an excellent solution.

If you're not interested in using Vagrant, you can investigate using FastCGI as your interface to Apache and using the SetEnv PHPRC... suggestion proposed on this blog:

Apache & PHP: Multiple PHP.ini Configuration Files (Sunday, February 8, 2009)

Source: http://hyponiq.blogspot.com/2009/02/apache-php-multiple-phpini.html

The second work-around is to use the PHPRC environment variable configurable in Apache using the SetEnv directive. This directive allows you to set an environment variable that is then passed to any CGI script and/or Server Side Include (SSI) set in any static (x)HTML page (or other document type). In this instance, you'd be telling each PHP-CGI instance where to find its configuration settings. The example would be (coinciding with the previous one):

# vhosts.conf
NameVirtualHost *:81
<VirtualHost *:81>
  ServerAdmin [email protected]
  ServerName vhost.example.com
  DocumentRoot "C:/path/to/doc/root"
  ErrorLog "logs/vhost.example.com-errors.log"

  # Set the PHPRC environment variable
  SetEnv PHPRC "C:/path/to/doc/root/php.ini"

  <Directory "C:/path/to/doc/root">
    # ... yadda, yadda, yadda ...
    # you get the point!
  </Directory>
</VirtualHost>

However, the PHP documentation changing the runtime configuration suggests that you can use certain values like php_value to try loaalong with, possibly the SetEnv directive.

He suggests another option not using FastCGI, instead leveraging the php_value, php_flag etc. configuration options.

Other's seem to have had some success with executing scripts through FastCGI though, see: Separate php.ini for different virtual hosts

Other suggestions involve the PHPINI directive, which may be pertinent for your needs, see: How do I limit PHP apps to their own directories and their own php.ini?

Unattended

SetEnv PHPRC does not work at least on Ubuntu. It still loads the one from /etc only. However, using PHPINIDir <path-to-root> works (ex. PHPINIDir "/some/directory/public_html"). – Jaimeejaimes

The comments in the documentation say that PHPRC should also contain the directory where php.ini is located and not the full path to the config file: php.net/manual/en/configuration.php – Hispanic