<?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>Tue, 21 May 2013 14:51:51 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Brian Moon's Blog: Apache Worker and PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/9641</guid>
      <link>http://www.phpdeveloper.org/news/9641</link>
      <description><![CDATA[<p>
In a <a href="http://doughboy.wordpress.com/2008/02/13/apache-worker-and-php/">recent post</a> to his blog, <i>Brian Moon</i> talks about the experience he's had with using PHP on Apache 2 with a <a href="http://www.php.net/manual/en/faq.installation.php#faq.installation.apache2">threaded MPM</a> at Dealnews.com.
</p>
<blockquote>
Well, first, what is an MPM? It stands for Multi-Processing Module. [...] The most commonly used threaded MPM is the Worker MPM. In this MPM, you have several processes that run multiple threads within it. This is the one I will be talking about.
</blockquote>
<p>
He <a href="http://doughboy.wordpress.com/2008/02/13/apache-worker-and-php/">goes on</a> to describe the "huge memory savings" that using the module got them - using the worker process to increase the child capacity of the Apache instance. He recommends keeping it simple when compiling a server to work with the worker functionality and mentions  how it can also help with serving static pages right along side the dynamic ones (without a second server!).
</p>
<p>
Check out <a href="http://doughboy.wordpress.com/2008/02/13/apache-worker-and-php/">the post</a> for a few more tips.
</p>]]></description>
      <pubDate>Fri, 15 Feb 2008 08:43:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Robert Swarthout's Blog: PHP frontend to Subversion (SVN)]]></title>
      <guid>http://www.phpdeveloper.org/news/7206</guid>
      <link>http://www.phpdeveloper.org/news/7206</link>
      <description><![CDATA[<p>
In a <a href="http://www.robertswarthout.com/?p=13">new post</a> to his blog, <i>Robert Swarthout</i> about a PHP frontend he's been developing for working with Subversion repositories:
</p>
<blockquote>
The frontend needed to be designed in such a way that each developer could access their working copies and make the full range of actions against them. I decided to also use an AJAX setup so that pages would be quickly loaded and updated by a single toggle of a folder.
</blockquote>
<p>
A few issues <a href="http://www.robertswarthout.com/?p=13">popped up</a>, including tracking edits correctly through the interface. His solution revolved around an Apache MPM that could serve different pages to different users and groups. With this solution in place, the functionality could be built up, a list of which he provides including:
<ul>
<li>create working copy from repository (svn checkout)
<li>svn blame
<li>svn delete
<li>search files (via a grep/find combination, omitting .svn folders)
<li>svn rename
</ul>
</p>]]></description>
      <pubDate>Thu, 01 Feb 2007 10:33:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Ben Ramsey's Blog: Peruser MPM for Apache]]></title>
      <guid>http://www.phpdeveloper.org/news/4407</guid>
      <link>http://www.phpdeveloper.org/news/4407</link>
      <description><![CDATA[In his quest for a secure method of server-side security in addition to PHP, <i>Ben Ramsey</i> stumbled across <a href="http://www.telana.com/peruser.php">Peruser MPM</a>, an Apache security module, seemingly with PHP in mind. In <a href="http://benramsey.com/archives/peruser-mpm-for-apache/">this latest blog post</a> he details what lead him there.
<p>
<quote>
<i>
A while back, when I was doing some research for a talk on server-side security for PHP, I looked into various "secure" methods for setting up a server for multiple users. Despite my search, I couldn't find a simple and effective solution for managing a server with a large (and untrusted) user base (as is the case with many virtual hosting companies).
<p>
Sure, there's PHP's safe_mode, but its "safety" is misleading at best. There's also open_basedir, which helps a little, but it's not quite enough. For my research, I also looked at and tested <a href="http://www.modsecurity.org/">mod_security</a>, and the <a href="http://www.hardened-php.net/">Hardened PHP Project's Hardening Patch</a>.
</i>
</quote>
<p>
Eventually, through <a href="http://www.christopher-kunz.de/serendipity/archives/74-guid.html#c533">this comment</a>, he found <a href="http://www.telana.com/peruser.php">Peruser MPM</a>, a module that runs each Apache process with its own user/group combination. He <a href="http://benramsey.com/archives/peruser-mpm-for-apache/">notes a few issues</a> that it still has (breaking mod_ssl and making Apache less scalable), but overall, it does sound pretty cool... ]]></description>
      <pubDate>Thu, 01 Dec 2005 07:12:35 -0600</pubDate>
    </item>
  </channel>
</rss>
