Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

i currently run apache 2 with php5.1.6 running as mod_php on a centos 5.6 box,

I use .htaccess for mostly redirection I already have latest APC running apc.so I also have mysql etc

Until recently ive been reading things like; 1) running php as fastcgi benefits on high traffic sites 2) Read something about squid being used as a proxy for static content.

all this time my confusion is increasing.... then i finally landed on lighttpd which seems to encompass all those optmizations.

Problem is, there is no uptodate article covering the complete migration from apache to lighttpd.

Secondly, Ive read a little on lighttpd being used as a proxy for apache serving static content.

Which is better? complete migration or start from scratch using lighttpd or simply setting httpd as a proxy.

Please include relevant references where possible.

share|improve this question
    
What problem are you trying to fix? Low memory? High CPU? Complex config you want simplified? Or just a general interest in moving from Apache to lighttpd? Why you want to migrate makes a difference, also it depends how many sites you've got, etc. –  EightBitTony Aug 2 '11 at 8:20
1  
Subjective opinion: NGINX is better than lighttpd. Also you should probably provide more details, are you using any kind of config/management tool (CPanel, Webmin etc.). Are you running custom applications or standard FOSS software (Wordpress, Joomla PHPBB etc.). –  sam Aug 2 '11 at 8:34
    
ok sorry, low memory was a big factor. anyway. ive installed nginx as a front end for apache serving static content. it was very easi and straight forward jamescacchione.net/featured-articles/… –  Sir Lojik Aug 2 '11 at 9:18

1 Answer 1

There's no up-to-date article on switching from apache to lighttpd because, for all practical purposes, lighttpd has been replaced by nginx. Lighttpd was great for it's day, but I'm afraid it hasn't got anything going for it now.

I'd make a complete migration to nginx; I've not had a need for an Apache-specific feature in years.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.