lighttpd woes…
I’m still having issues with lighttpd on my server. Apache2 is serving pages well, but I don’t have PHP5, nor do I have the increased speed of page generation.
The only thing that is holding me back is the rewrite rules for wordpress. I can bodge them so that the server displays pages to browsers, but the server actually returns a 404 error in the headers. This means that any software that actually acts on those headers, rather than just waiting for the connection to close and displaying the output, is broken. This includes quite a few feed readers.
“Why not just stick with Apache!?”
I can hear the cries now (the force is strong with this one). Well, the main reason is this: Because I don’t have to. I have the power to switch server software and, because I like to take things apart, fiddle around, then wonder why it doesn’t work quite as well as it used to, I’m going to use that power. The real benefits are mainly in page generation time and memory footprint.
Because I’m on a virtual server (multiple servers that act like a single machine on a single piece of hardware) memory constraints are fairly absolute. Using swap is a no-no and the server will simply stop spawning processes. Using lighttpd I can have an extra 10 - 25 mb of RAM free over Apache. Also, the page generation is around 1/3rd that of Apache, even under heavy load.
As soon as I get this rewrite rule thing sorted I’m going to write a Howto document for those who don’t wish to struggle through the issues and hassles as I have.
