On Jun 10, 2010, at 10:38 AM, Eric Wong wrote: > It'd have to be a time-aware counter, because sometimes slightly broken > _will_ exit/die 10 times over the period of an hour. But the site can > still be making enough money with 99.8% successful service and not > care about spending time/resources fixing the last 0.2% :) > > But even with a proper time-aware counter, the app is still broken at > deploy time. So I don't believe there is much point in adding more code > just to exit the process when the proper solution is for the user to > _fix_ the app. > > And again (I seem to remember saying this months ago), any time you're > deploying, you should be paying extra attention to the app anyways. > That means testing with actual HTTP requests, not just seeing of the > process is up. Just having a running process serving error pages is > equally worthless as not running the server at all.
Hm.. It's makes sense. But much better if it will be writing in the documentation for the future. Thank you! _______________________________________________ Unicorn mailing list - [email protected] http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying
