concurrentmodphp is currently available as a USE flag for dev-lang/php. It enables you to run two versions of PHP in parallel, loaded into your apache's mod_php.With the advent of FastCGI/fpm in PHP-5.3.3 (very soon on a mirror near you), the preferred way to run multiple versions of PHP in parallel is CGI. Not only can you run several PHP versions independently, you also get proper script isolation (running each script as a different user, if you wish so) and thus enhanced security.
This is why I've decided to end support for USE=concurrentmodphp after php-5.3.3 and php-5.2.14. Versions after those will simply stop shipping the patches required to support this USE flag. Please use the time with PHP-5.3.3 to switch to fpm, if you need the functionality currently provided by concurrentmodphp.
This is great! Thank you very much for your work.
ReplyDeleteI currently use mod_itk to implement user seperation. The downside of a FastCGI solution was always it wouldn't parse .htaccess for php settings. What do you plan to do about that? Will it work? Will you include a guide how to set this up?
ReplyDelete@hurikhan77 I'll look into that. Sorry, I've no answer off the top of my head.
ReplyDelete@hurikhan77: With FPM you can set pool-specific settings in the fpm configuration, much like with .htaccess.
ReplyDeleteOne big advantage with configuring site-specific ini values on the pool level is that .htaccess is always apache-specific, while the fpm configuration will work regardless of what webserver you should chose to run.
You can take a look at the php-fpm config that we ship with php-5.3.3 how to configure your php_value and php_admin_value settings.