<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Sun, 19 May 2013 23:08:24 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[ServerGrove Blog: How to setup multiple PHP versions on Apache]]></title>
      <guid>http://www.phpdeveloper.org/news/16758</guid>
      <link>http://www.phpdeveloper.org/news/16758</link>
      <description><![CDATA[<p>
On the ServerGrove blog today there's a new post from <i>Ishmael</i> about setting up <a href="http://blog.servergrove.com/2011/08/22/how-to-setup-multiple-php-versions-on-apache/">multiple versions of PHP on one Apache instance</a> with the help of FastCGI.
</p>
<blockquote>
There are several reasons you might need to run multiple versions of PHP on the same server. Maybe you have a PHP 5.2 application running on your server and you need to start working on another application based on a new framework like Symfony2 or Lithium? Perhaps you haver a client with a legacy site that runs PHP 5.2, or maybe you simply want to test some of the new functionality? This post is going to explain how to setup a server to run multiple versions of PHP.
</blockquote>
<p>
Normally, Apache can only be compiled with one version of PHP, but FastCGI gets around that by letting you define it in a configuration file instead. They also include support for defining the user the process runs as (suexec) that helps to make permissions issues lesser. Included are all of the command-line calls and config settings you'll need to make to get things set up.
</p>]]></description>
      <pubDate>Tue, 23 Aug 2011 11:07:38 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Stuart Herbert's Blog: Using suexec To Secure A Shared Server]]></title>
      <guid>http://www.phpdeveloper.org/news/9267</guid>
      <link>http://www.phpdeveloper.org/news/9267</link>
      <description><![CDATA[<p>
One of the more frustrating things about working on a shared server is trying to keep it secure while still giving users some flexibility in their environments. <i>Stuart Herbert</i> has continued his series looking at combating issues like this with <A href="http://blog.stuartherbert.com/php/2007/12/18/using-suexec-to-secure-a-shared-server/">this look</a> at installing suexec to secure a shared server.
</p>
<blockquote>
<a href="http://blog.stuartherbert.com/php/2007/11/21/the-challenge-with-securing-shared-hosting/">The challenge with securing a shared hosting server</a> is how to secure the website from attack both from the outside and from the inside. PHP has built-in features to help, but ultimately it's the wrong place to address the problem.
</blockquote>
<p>
<a href="http://blog.stuartherbert.com/php/2007/12/18/using-suexec-to-secure-a-shared-server/">His guide</a> steps through the entire process - getting the software, configuring Apache (with the PHP/CGI installation) and configuring suexec, both for the default install and then for the shared server settings. There's even a few brief benchmarks showing the speed of execution for scripts with and without the suexec environment. 
</p>]]></description>
      <pubDate>Tue, 18 Dec 2007 12:09:00 -0600</pubDate>
    </item>
  </channel>
</rss>
