It's not really an either/or thing - it is quite feasible to have nginx handling all incoming requests, and maybe serving static pages itself, while passing rails requests to upstream mongrels, and other requests - php, or whatever - to apache.
I've not done any tests, but it just 'feels right' to have something fast at the front end, and so far this setup works for me ;) Tony On 20/01/2008, Bbq Plate <[EMAIL PROTECTED]> wrote: > > ive been reading many blogs about a different setups. most blogs that i > have read, nginx seems very recommended. however, apache has many > documentation to help handle non rails stuff. > > Ayyanar Aswathaman wrote: > > Hi, > > > > Lighttpd or Ngnix. Which one is best for production env? > > Kindly throw some reasons for the best one, and also for the > > worst one. > > > > Ayyanar > > -- > Posted via http://www.ruby-forum.com/. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
