It's more inertia than preference. I've been running passenger on one of our test servers, but our production environment consists of a pool of servers that run a bunch of low volume rails apps. The life cycle of these apps are managed through custom code that launches them via mongrel_rails (this setup pre-dates passenger). Passenger would be a fine solution (although I wish it provided better control over how many of which app were running), but requires a lot of testing before releasing to production.
One possibility is to install passenger on the production machines but not run it in "auto-detect" mode. That way one app at a time could be moved to passenger. I need to do some more testing of that configuration. Still in the short term the shortest path for me to get a rails 3 app on our production servers is to be able to launch it via mongrel_rails. On 4/29/10 10:00 AM, Jonathan Rochkind wrote: > Awesome, good to know that you're working on mongrel! > > If you're suggesting rack or rails server directly in Rails3... ah, > but still with mongrel, just not wtih mongrel_rails? > Curious what reasons you have to prefer mongrel to passenger? > Jonathan > > Luis Lavena wrote: >> On Thu, Apr 29, 2010 at 11:19 AM, Jonathan Rochkind >> <rochk...@jhu.edu> wrote: >> >>> Luis Lavena wrote: >>> >>>> I haven't played enough with Rails 3 to actually use mongrel with it, >>>> but due the changes in rails 3 bootstrap, I would rather use rack or >>>> rails server directly instead of mongrel_rails. >>>> >>>> >>> Or passenger. I get the feeling that most developers have abandoned >>> mongrel for passenger, and mongrel no longer has very many developers >>> working on improving/maintaining mongrel itself either. >>> >>> >> >> Well, I might be biased on my response. >> >> I've been working on bring new changes to mongrel to ease the >> development of it and set the ground to bring better rack integration >> from Unicorn. >> >> You can see all these changes here: >> >> http://github.com/fauna/mongrel/commits >> >> So is not fair to say that is abandoned. >> >> While I use passenger in some server, I still use mongrel in more than >> 75% of all my production environments, even locally. >> >> I'm cleaning up JRuby support for a new 1.2.0 release and new ones >> will follow. >> >> What I have suggested about using "rails server" instead of >> mongrel_rails is because mongrel_rails needs to be compatible with >> previous version of Rails, and I'm not a 100% Rails user to explore >> that. See this ticket: >> >> http://github.com/fauna/mongrel/issues#issue/2 >> >> That said, if anyone work on that would happily integrate it back. >> >> Thank you. >> > _______________________________________________ > 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
