rasanya gak pernah deh, blm pernah pake mongrel untuk deploy aplikasi rails atau mungkin cuma sekedar forward info aja ya he he, udah lupa :p
On Sun, 09 Sep 2007 02:52:03 +0700, Hendy Irawan <[EMAIL PROTECTED]> wrote: > dulu Pak Rofik kah yg membahas ttg ini? > > > ToolTipping: Rails, High Availability and Restarting Mongrel With > Seesaw > > <http://blog.spacemonkeylabs.com/articles/2007/08/26/tooltipping-rails-high-availability-and-restarting-mongrel-with-seesaw> > > from spacemonkey(b)labs > <http://www.google.com/reader/view/feed/http%3A%2F%2Fblog.spacemonkeylabs.com%2Fxml%2Fatom%2Ffeed.xml> > by Spacemonkey > > In a blog post by Peter Cooper <http://www.rubyinside.com/> titled > Seesaw: An Improved Restart System for Mongrel > <http://www.rubyinside.com/seesaw-an-improved-restart-system-for-mongrel-589.html/trackback/> > Peter points out a great system for managing Rails applications with > high-traffic or high-availability requirements. > > Seesaw <http://synaphy.com.au/2007/8/20/seesaw> was created to make it > easier to deploy updates and patches (and more) to clusters of Mongrel > servers. > > Perhaps the best quote from the Synaphy post: > > “Matt runs a pretty busy Rails site, at peak periods he’s serving a > few hundred requests a second. With traffic like that, you cannot > afford downtime. Any downtime. Even if you’ve just fixed the bug > from hell and you desperately need to redeploy your application > code.” > > Ultimately this makes a fantastic point regarding the deployment of > Rails applications versus other platforms and languages – I’ve learned > that the more time I spend working and playing with Rails, the more > convinced I am that it has the most optimal facilities for deployment, > change management and load balancing. These are all critical factors for > applications that might have reasonable success. All in all an excellent > read, and also provides some really nice examples of deployment > scenarios. > > -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
