BenV's notes

As I love to tinker around with apache/php installations to get them to work as fast as possible while still keeping some security in tact, I found myself messing around with FastCGI today. But why?! Here’s why:
On this machine I previously installed suPhP to get php scripts to run as a normal unix user instead of user apache (so users have the ability to completely lock out their database settings etc for other users on that machine). However, to speed stuff up on a magento webshop I wanted to have a PHP opcode cache running (I tried out APC). (continue reading…)

It seems to be update day today….

I felt like updating my shit today. Somehow I enjoy updates so I do it whenever I see interesting stuff.
So glancing through the slackware changelog I noticed a new Apache2 version (2.2.12 with a bunch of security updates). Meh, not my favorite piece of garbage to upgrade, but local upgrades were easy enough and also the remote (slackware 11, custom builds) ones went without hickups. (continue reading…)

As usual this doesn’t work automagically (unless you’re lazy and put AllowOverride All in your vhost configs).
Wordpress wanted RewriteEngine on, but of course this disabled itself since apache didn’t like it with my default permissions.
So:

To allow Rewrite stuff in the .htaccess file, put ‘FileInfo’ and ‘FollowSymlinks’ (or SymLinksifOwnerMatch) in AllowOverride.

(of course putting the rewrite stuff in the vhost config is faster than the .htaccess stuff, but who cares)