+1 from me for nginx... The configuration is pretty straighforward and easy to understand.
Here's the example config from the nginx cookbook. http://wiki.codemongers.com/NginxRubyonRailsMongrel It's got proxying, gzip compression, & sendfile out of the box (very nice if you'd had to configure for apache). - scott On Mon, Mar 31, 2008 at 2:15 PM, Jonathan Rochkind <[EMAIL PROTECTED]> wrote: > I have no experience with nginx, but someone else on this list said it > was common, so that'd probably work. > > If you plan to go that route eventually anyway, I'd just do that now, > because what you need to do to get your mongrel to answer on port 80 > will change completely in the presence of nginx or apache vs. now with a > bare mongrel. So the work you're doing now to figure out how to get > mongrel to run bare on 80 seems kind of unproductive. > > I don't honestly have any specifics in mind as far as problems from > running a bare mongrel on port 80 in production. Maybe others on the > list do. Just that that doesn't seem to be the popular or recommended > way to do it, so you might run into weird problems that others don't. As > you've noticed, one is that you will need to run the mongrel as root, > which is really pretty undesirable. Or come up with some custom solution > to start mongrel as root and attach it to 80 then exec it as another > user. But now you're creating weird solutions just to get mongrel to run > bare on 80, when if you're planning on running it under nginx or apache > anyway you won't ultimately need, so why deal with it unneccesarily? > > Jonathan > > James Testa wrote: > > Jonathan, > > At the moment I am only running mongrel, but we are > > just beta testing. > > > > 1. What sort of headaches do you foresee just running mongrel? Do > > you mean from a load balancing, high traffic point of view? > > 2. I was planning on running nginx as the front end. Do you see any > > issues > > with nginx vs Apache? > > > > > > Jim > > > > Jonathan Rochkind wrote: > > > >> I really do still think you're going down the wrong path running > mongrel > >> directly on 80, instead of sending it through a proxy on your web > >> server. I think it's going to cause you headaches in the long run. Do > >> you have any web server running on that machine? What web server? Is > >> there any reason you are choosing not to go the route of having apache > >> (or other specialized) web server be a front end to your mongrel? > >> > >> Jonathan > >> > >> Kirk Haines wrote: > >> > >>> Kirk Haines > >>> _______________________________________________ > >>> Mongrel-users mailing list > >>> Mongrel-users@rubyforge.org > >>> http://rubyforge.org/mailman/listinfo/mongrel-users > >>> > >>> > >> -- > >> Jonathan Rochkind > >> Digital Services Software Engineer > >> The Sheridan Libraries > >> Johns Hopkins University > >> 410.516.8886 > >> rochkind (at) jhu.edu > >> > > > > > > -- > Jonathan Rochkind > Digital Services Software Engineer > The Sheridan Libraries > Johns Hopkins University > 410.516.8886 > rochkind (at) jhu.edu > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users@rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users >
_______________________________________________ Mongrel-users mailing list Mongrel-users@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-users
