Some concerns about these instructions...
- In most low-memory VPS situations, the 64-bit architecture is a disadvantage and should be avoided in favor of 32-bit, for memory efficiency reasons.
- There is absolutely no need to compile from source in this day and age, and bypassing your distribution's package management in this way puts you at serious risk of missing critical security updates (or having things break when applying security updates). If a feature is missing in your distribution's packaging, ask around to see if it might be in another package, or consider a different distribution. In short, do NOT compile any system software unless you are fully aware of the security implications of doing so! There's a lighttpd package in CentOS, and the php-cgi package works for FastCGI.
- This is Unix, we use forward slashes here.
- There is no need to specifically specify
server.bindin the lighttpd.conf. There's also no need for the
$SERVER["socket"] == "blah:80"in the virtual hosting configuration. In fact, using these instructions as written, it will not work because you'll be trying to bind to yourip:80 twice. Best to let it bind to all interfaces so you can refer to it as "localhost" on the local machine.
That's just from my reading of a couple parts of the lighttpd and php instructions. Who knows about the rest of it? I don't. So, proceed with caution... Rtucker 14:53, 4 July 2009 (EDT)
 Postfix with MySQL support
- There is a Postfix package with mysql support in Centosplus, the page Centosplus Repository page on the Centos Wiki has information on how to use this, with a specific example on how to install the postfix version with mysql/pgsql support.
- If you need php 5.2, it's available in the Centos testing Repository . DISCLAIMER -This repository is a proving ground for packages on their way to CentOSPlus and CentOS Extras. They may or may not replace core CentOS packages and are not guaranteed to function properly. These packages install but are waiting for feedback from testers as to their functionality and stability. Packages in this repository will come and go during the development period, so it should not be left enabled or used on production systems to obtain ongoing updates. This repository is intentionally not shipped with CentOS by default. Feedback should be directed to the Centos-Devel list  stevewalsh 15:45, 28 October 2009 (EDT)
 Couple of things, or why I went the way I did...
- The choice to go 64bit over 32bit is purely for future compatibility. I think that software will become more and more optimized for the 64bit arch. That said if you are hosting high traffic sites then go with the 32bit versions as you may need the memory.
- When I first wrote this tutorial I installed everything with yum and nothing from source.
That worked fine for about two weeks until I did a yum update without thinking about it. The update killed postfix because the version in the repository was compiled without the mysql options.
Since then I decided to take a more active roll in the management of my Linode. I compile only the software where I need or want specific settings and the rest I install with yum. I rely on yum to keep the binaries up-to-date while I monitor the mailing lists for the source installed software. I have been running this way for just under a year now without any major upgrade problems.
- Did I miss some? I am a Windows programmer by day and tweak on my Linode at night. Sometimes my fingers forget what I am working on. Please, feel free to fix them!
- This is needed to get https and virtual hosting working.
Themike 21:21, 29 July 2009 (PST)