seesaw 0.2.4 → 0.2.5

data/History.txt

@@ -1,3 +1,9 @@
+== 0.2.5 / 2007-08-20
+* renamed "ripple" command to "bounce"
+
+== 0.2.4 / 2007-08-19
+* documentation is complete
+
 == 0.2.3 / 2007-08-19
 
 * Now hands in the path to the mongrel config file into the mongrel_rails commands

data/README.txt

@@ -12,7 +12,7 @@ Let's say you have a mongrel cluster setup with 7 individual mongrels on your se
 
 When you execute:
 
-  mongrel_rails seesaw::ripple
+  mongrel_rails seesaw::bounce
 
 This will happen:
 
@@ -29,7 +29,7 @@ Halfway through the process, your site is only running on half of the mongrels,
 
 == SYNOPSIS:
 
-* mongrel_rails::ripple
+* mongrel_rails::bounce
   perform a rippling restart of the mongrel cluster
   
 * mongrel_rails::switch --cluster CLUSTER

data/Rakefile

@@ -9,7 +9,7 @@ Hoe.new('seesaw', Seesaw::VERSION) do |p|
   p.author = 'Matt Allen, Max Muermann'
   p.email = 'max@muermann.org'
   p.summary = 'Ripple-restart a mongrel cluster with no downtime'
-  p.description = p.paragraphs_of('README.txt', 2..5).join("\n\n")
+  p.description = p.paragraphs_of('README.txt', 1..5).join("\n\n")
   p.url = p.paragraphs_of('README.txt', 0).first.split(/\n/)[1..-1]
   p.changes = p.paragraphs_of('History.txt', 0..1).join("\n\n")
   p.extra_deps << ['gem_plugin', '>= 0.2.2'] << ['mongrel', '>= 1.0.1'] << ['mongrel_cluster', '>= 1.0.2']

data/lib/seesaw/init.rb

@@ -6,7 +6,7 @@ require 'seesaw/mongrel_cluster_patch'
 require "erb"
 
 module Seesaw
-  VERSION = '0.2.4'
+  VERSION = '0.2.5'
   
   module CommandBase
 
@@ -94,7 +94,7 @@ module Seesaw
     
   end
   
-  class Ripple < GemPlugin::Plugin "/commands"
+  class Bounce < GemPlugin::Plugin "/commands"
     include Mongrel::Command::Base
     include CommandBase
     

metadata

@@ -3,15 +3,15 @@ rubygems_version: 0.9.4
 specification_version: 1
 name: seesaw
 version: !ruby/object:Gem::Version 
-  version: 0.2.4
-date: 2007-08-19 00:00:00 +10:00
+  version: 0.2.5
+date: 2007-08-20 00:00:00 +10:00
 summary: Ripple-restart a mongrel cluster with no downtime
 require_paths: 
 - lib
 email: max@muermann.org
 homepage: "    by Matt Allen and Max Muermann"
 rubyforge_project: seesaw
-description: "When you execute:  mongrel_rails seesaw::ripple  This will happen:  1. your webserver configuration is switched to only use the front half of your mongrel pack (mongrels 1-4) 2. the webserver (apache or nginx) is gracefully restarted 3. the back half of your mongrel pack (mongrels 5-7) is restarted 4. your webserver configuration is switched to only use the back half of the pack 5. the webserver is gracefully restarted 6. front half mongrels are restared 7. webserver configuration switched back to full cluster configuration 8. webserver restarted one last time"
+description: "== DESCRIPTION:  seesaw: [verb] to change rapidly from one state or condition to another and back again.  Seesaw is a replacement/addition to the mongrel_cluster gem and allows you to perform a safe rippling restart of your mongrel cluster without dropping any requests.  Let's say you have a mongrel cluster setup with 7 individual mongrels on your server. Let's also say that you have to deploy a code update and restart all of your mongrels but your site is really busy and you cannot afford any downtime whatsoever.  When you execute:  mongrel_rails seesaw::bounce  This will happen:  1. your webserver configuration is switched to only use the front half of your mongrel pack (mongrels 1-4) 2. the webserver (apache or nginx) is gracefully restarted 3. the back half of your mongrel pack (mongrels 5-7) is restarted 4. your webserver configuration is switched to only use the back half of the pack 5. the webserver is gracefully restarted 6. front half mongrels are restared 7. webserver configuration switched back to full cluster configuration 8. webserver restarted one last time"
 autorequire: seesaw/init.rb
 default_executable: 
 bindir: bin