freshwire
04-06-2010, 01:48
Most distros (or config provided when manually compiling) will have your server reasonably secure as standard so nothing to worry about unless your paranoid or providing hosting to others.
Just make sure you keep the software up to date.
eAccelerator wasn't updated for quite a while but then it seemed to come back to life. The latest version came out just a few days ago.
Not sure about the lighttpd and apache config thing (I may be wrong); as far as I knew it wasn't directly compatable. Lighttpd might have equivilent modules but I don't think they can be swapped in place for apache2. If you want the rewriting etc. then you could consider the nginx (static files) + apache (php) that I suggested before. You could use apache for static too if you wanted and then just have nginx for caching. In terms of raw speed nothing will compare to nginx serving from its cache. Most CMS won't play nice with cache (the content just won't get cached) so you might want to mod the scripts to send out the right headers.
All that said, 150 uniques/day will prove to be no trouble, for any solution you go for.
Just make sure you keep the software up to date.
eAccelerator wasn't updated for quite a while but then it seemed to come back to life. The latest version came out just a few days ago.
Not sure about the lighttpd and apache config thing (I may be wrong); as far as I knew it wasn't directly compatable. Lighttpd might have equivilent modules but I don't think they can be swapped in place for apache2. If you want the rewriting etc. then you could consider the nginx (static files) + apache (php) that I suggested before. You could use apache for static too if you wanted and then just have nginx for caching. In terms of raw speed nothing will compare to nginx serving from its cache. Most CMS won't play nice with cache (the content just won't get cached) so you might want to mod the scripts to send out the right headers.
All that said, 150 uniques/day will prove to be no trouble, for any solution you go for.