My current preference is Nginx + Passenger + Rails + MySQL as well. Deciding between Apache or Nginx is fairly simple in my book. If you're an Apache guru already, or if you need to run something else on the box that is easier in Apache (like a PHP blog, CMS, etc) choose Apache, otherwise choose Nginx. Nginx is simpler to configure and uses less memory, but it does not do as many tricks and Apache does.
Best, Rob On Mon, May 11, 2009 at 12:25, Matt Aimonetti <mattaimone...@gmail.com> wrote: > Most of the official Rails sites and 37signals use: Apache + Passenger + > Rails + MySQL > It's the easiest deployment solution and it works very well. My only problem > with Passenger is that if you don't get much traffic, all the workers get > killed and the next request coming up will take a little while. (workarounds > exist and the Phusion team is working on adding a min amount of workers) > > Also, if you want to play with passenger on your local machine, you can find > a really useful Passenger Panel Preference. > (If you are comfortable using Postres, I'd probably suggest you use it > instead of MySQL) > > - Matt > > On Mon, May 11, 2009 at 12:20 PM, liquid_rails <cheri.anacle...@gmail.com> > wrote: >> >> There are several options for setting up a Rails app, e.g. >> >> - Nginx, Rails and Thin; PostgreSQL; >> - Nginx, Rails and Thin; MySQL >> - Nginx, Rails and mongrels; MySQL >> - Apache, Rails and Mongrels; PostgreSQL >> >> etc., you get the idea. (See http://articles.slicehost.com/sitemap) >> >> Is there a general consensus as to which is the best setup in terms of >> weight and efficiency to go with? >> >> Thanks, >> >> Cheri >> > > > > > --~--~---------~--~----~------------~-------~--~----~ SD Ruby mailing list sdruby@googlegroups.com http://groups.google.com/group/sdruby -~----------~----~----~----~------~----~------~--~---
