MacPorts Leopard + Apache 2.2.17 + PHP 5.3.5 + WordPress 3.0.4 + 1 million or so users per month issue

[Ryan Schmidt]

On Jan 27, 2011, at 14:53, Betty Bronner wrote:

> Running with the combination in the subject line causes, every once in a while, to have random RSS feeds from the WordPress install show up instead of the page that the user requested.  This problem is exasperated as the number of users hitting the system increases.  The only critical variant being used is:
> 
> php5 +apache2 +pear
> 
> Everything in MacPorts built just fine.  The command I used was 'sudo port install php5 +apache2 +pear'.

Hmmmm. Sorry to hear that.


> This box also has the Entropy PHP 5.3.0 build running on it but that is/was tied to the Apple built Apache server.  It didn't seem to cause problems with the MacPorts build process but maybe it did?  I also tried to mirror the httpd.conf in the Apple Apache as closely as possible.

You're right, MacPorts Apache/PHP should be separate from and not interfere with (or be interfered with) by Apple Apache/PHP or Entropy PHP.


> I'm also interested in nginx.  Anyone have any instructions on how to set up nginx with MacPorts - specifically migrating a WordPress install?  If I can get nginx working with WordPress, it will allow me to determine if PHP or Apache is the issue.  I've also read that nginx works better with PHP-FPM, but I have no idea what PHP-FPM is or how to set it up - MacPorts-specific instructions are very much desired for this too.  PHP-FPM is voodoo because no one can explain what it is or does or how to actually use it but everyone says it is awesome.

nginx is interesting, but I haven't looked into it. I used to be interested in lighttpd, but its development seems to have stagnated; nginx seems to be the new hotness.

There is an open request to add FPM support to MacPorts PHP:

http://trac.macports.org/ticket/26039

I was hesitant to add yet another variant to MacPorts PHP after expending so much effort removing the existing variants; I really wanted to go a different way and have separate ports for each PHP SAPI, as discussed here:

http://trac.macports.org/ticket/19091

Partly due to this, I haven't looked into PHP-FPM yet.