[Mongrel] Is mongrel stable enough to be used in a production environment?

Kevin Williams kevwil at gmail.com
Sat Apr 8 22:17:52 EDT 2006

I *really* don't mean to be a jerk, but why not call the "production"release 1.0? I'm sure you have your reasons, I guess, but I think ifit's public and production-worthy, it should be at least 1.0. Just athought - getting set in my ways as I get old probably. ;)
On 4/8/06, Zed Shaw <zedshaw at zedshaw.com> wrote:>  I'm currently taking the 0.3.12.x release and making it stable and robust> in the face of malformed protocol requests or giant "moby" requests.  There> is a pre-release available ( from:>>    gem install mongrel> —source=http://mongrel.rubyforge.org/releases/>>  Which you might want to try in order to get a jump on it's stability.  This> release mostly just fixes the Date formatting to be RFC compliant.>>  I'm telling people that the 0.3.13 release will be the "stable for> pre-production release".  This means that you can start putting your> pre-production and staging systems on it for testing and evaluation> purposes.  At Canada on Rails I plan on getting together with as many people> as possible and trying to get their applications to run Mongrel as my main> testing process.>>  After Canada on Rails I'm planning the 0.4 release and will start telling> people it's production ready.>>  Now, before people go crazy and start running their rails applications on> Mongrel expecting google size loads, there's quite a few things that> "Mongrel in production" is really missing:>>    * A monitoring best practice.  I'm looking at monit for this and should> have a doc for people soon.>    * A multi-machine cached cluster best practice.  There's one using> lighttpd that works, but there's some bugs in lighttpd's mod_proxy that> makes it not so great.  I should have a new version of the document which> clears all this up.>    * Management mechanisms.  Monit should take care of things like stray> mongrels (pun!) and bouncing badly behaving servers.  It would be nice to> give people a small handler that lets them hit a mongrel server on a> separate host to see what it's doing and manage it a bit.>>  Hope that answers your question.>>  Zed A. Shaw>  http://www.zedshaw.com/>  http://mongrel.rubyforge.org/>>>>  On 4/7/06 3:50 PM, "Chris Richards" <evilgeenius at gmail.com> wrote:>>>> Is mongrel stable enough to be used in a production environment?   Is it> stable?>  If so, which version is recommended?>  Thanks,>>  Chris>>  ________________________________> _______________________________________________>  Mongrel-users mailing list>  Mongrel-users at rubyforge.org>  http://rubyforge.org/mailman/listinfo/mongrel-users>>> _______________________________________________> Mongrel-users mailing list> Mongrel-users at rubyforge.org> http://rubyforge.org/mailman/listinfo/mongrel-users>>

"Picking fights with people smarter than youis great - you always end up learning something."- jcooney.net

More information about the Mongrel-users mailing list