whiskey_disk 0.3.0 → 0.3.1

data/README.markdown

@@ -0,0 +1,281 @@
+## Whiskey Disk -- embarrassingly fast deployments. ##
+
+
+A very opinionated deployment tool, designed to be as fast as technologically possible.  (For more background, read the [WHY.txt](http://github.com/flogic/whiskey_disk/raw/master/WHY.txt) file)  Should work with any project which is git hosted, not just Ruby / Ruby on Rails projects.  Allows for local deploys as well as remote.
+
+Right-arrow through a short whiskey_disk presentation at [http://wd2010.rickbradley.com/](http://wd2010.rickbradley.com) (slide source available [here](http://github.com/rick/whiskey_disk_presentation).)
+
+### Selling points ###
+
+  - If you share the same opinions as we do there's almost no code involved, almost no
+    dependencies, and it uses stock *nix tools (ssh, bash, rsync) to get
+everything done.
+
+  - Written completely spec-first for 100% coverage.  We even did that for the
+    rake tasks, the init.rb and the plugin install.rb (if you swing that way).
+
+  - 1 ssh connection per run -- so everything needed to do a full setup
+    is done in one shot.  Everything needed to do a full deployment is done in
+one shot.  (Having 8 minute deploys failing because I was on CDMA wireless on a
+train in india where the connection won't stay up for more than 2-3 minutes is
+not where I want to be any more.)
+
+  - Deployment configuration is specified as YAML data, not as code.
+    Operations to perform after setup or deployment are specified as rake
+tasks.
+
+  - You can do *local* deployments, by this I mean you can use whiskey\_disk to
+    deploy fully running instances of your application to the same machine
+you're developing on.  This turns out to be surprisingly handy (well, I was
+surprised).  *NOTE*:  be sure to set your deploy_to to a place other than the
+current local checkout.
+
+  - You can do multi-project deployments, specifying deployment data in a single
+    deploy.yml config file, or keep an entire directory of project deployment config files.
+
+  - You can have per-developer configurations for targets (especially
+    useful for "local" or "development" targets).  Use .gitignore, or
+specify a config_branch and everyone can have their own local setup that just
+works.
+
+  - There's no before\_after\_before_after hooks.  You've got plenty of
+    flexibility with just a handful of rake hook points to grab onto.
+ 
+
+#### Dependencies ####
+
+rake, ssh, git, rsync on the deployment target server (affectionately referred to as the "g-node" by vinbarnes), bash-ish shell on deployment server.
+
+#### Assumptions ####
+
+ - you have a Rakefile in the top directory of your project's checkout
+ - you are deploying over ssh
+ - your project is managed via git
+ - you are comfortable defining post-setup and post-deployment actions with rake
+ - you have an optional second git repository for per-application/per-target configuration files
+
+### Installation ###
+
+As a gem:
+
+    % gem install whiskey_disk
+
+As a rails plugin:
+
+    % script/plugin install git://github.com/flogic/whiskey_disk.git
+
+### Configuration ###
+
+ - look in the examples/ directory for sample configuration files
+ - main configuration is in %lt;app_root>/config/deploy.yml
+ - config files are YAML, with a section for each target.
+
+Known config file settings (if you're familiar with capistrano and vlad these should seem eerily familiar):
+ 
+    domain:            host on which to deploy (this is an ssh connect string) 
+    deploy_to:         path to which to deploy main application
+    repository:        git repo path for main application
+    branch:            git branch to deploy from main application git repo (default: master)
+    deploy_config_to:  where to deploy the configuration repository
+    config_repository: git repository for configuration files
+    config_branch:     git branch to deploy from configuration git repo (default: master)
+    project:           project name (used to compute path in configuration checkout)
+    rake_env:          hash of environment variables to set when running post_setup and post_deploy rake tasks
+
+
+A simple config/deploy.yml might look like:
+  
+    qa:
+      domain: "ogc@www.ogtastic.com"
+      deploy_to: "/var/www/www.ogtastic.com"
+      repository: "git@ogtastic.com:www.ogtastic.com.git"
+      branch: "stable"
+      rake_env:
+        RAILS_ENV: 'production'
+
+ - defining a deploy:<target>:post_setup rake task (e.g., in lib/tasks/
+   or in your project's Rakefile) will cause that task to be run at the end
+of deploy:setup
+
+ - defining a deploy:<target>:post_deploy rake task (e.g., in
+   lib/tasks/ or in your project's Rakefile) will cause that task to be run
+at the end of deploy:now
+
+
+
+### Running via rake ###
+
+In your Rakefile:
+
+    require 'whiskey_disk/rake'
+
+  Then, from the command-line:
+
+    % rake deploy:setup to=<target>   (e.g., "qa", "staging", "production", etc.)
+    % rake deploy:now   to=<target>
+
+  or, specifying the project name:
+
+    % rake deploy:setup to=<project>:<target>   (e.g., "foo:qa", "bar:production", etc.)
+    % rake deploy:now   to=<project>:<target>
+
+
+### Running from the command-line ###
+  
+    % wd setup --to=<target>
+    % wd setup --to=<project>:<target>
+    % wd setup --to=foo:qa --path=/etc/whiskey_disk/deploy.yml
+    
+    % wd deploy --to=<target>
+    % wd deploy --to=<project>:<target>
+    % wd deploy --to=foo:qa --path=/etc/whiskey_disk/deploy.yml
+
+
+Note that the wd command (unlike rake, which requires a Rakefile in the current directory) can be run from anywhere, so you can deploy any project, working from any path, and can even specify where to find the deployment YAML configuration file.
+  
+The --path argument can take either a file or a directory.  When given a file it will use that file as the configuration file.  When given a directory it will look in that directory for deploy/&lt;project&gt;/&lt;target&gt;.yml, then deploy/&lt;project&gt;.yml, then deploy/&lt;target&gt;.yml, then &lt;target&gt;.yml, and finally, deploy.yml.
+  
+All this means you can manage a large number of project deployments (local or remote) and have a single scripted deployment manager that keeps them up to date.  Configurations can live in a centralized location, and developers don't have to be actively involved in ensuring code gets shipped up to a server.  Win.
+
+
+### Configuration Repository ###
+
+#### What's all this about a second repository for configuration stuff? ####
+
+This is completely optional, but we really are digging this, so maybe 
+you should try it.  Basically it goes like this...
+
+We have a number of web applications that we manage.  Usually there's a
+customer, there might be third-party developers, or the customer might have
+access to the git repo, or their designer might, etc.  We also tend to run a
+few instances of any given app, for any given customer.  So, we'll run a
+"production" site, which is the public- facing, world-accessible main site.
+We'll usually also run a "staging" site, which is roughly the same code, maybe
+the same data, running on a different URL, which the customer can look at to
+see if the functionality there is suitable for deploying out to production.  We
+sometimes run a "development" site which is even less likely to be the same
+code as production, etc., but gives visibility into what might end up in
+production one day soon.
+
+So we'll store the code for all of these versions of a site in the same git
+repo, typically using a different remote branch for each target
+("qa", "production", "staging", "development").
+
+One thing that comes up pretty quickly is that there are various files
+associated with the application which have more to do with configuration of a
+running instance than they have to do with the application in general.  In the
+rails world these files are probably in config, or config/initializers/.  Think
+database connection information, search engine settings, exception notification
+plugin data, email configuration, Amazon S3 credentials, e-commerce back-end
+configuration, etc.
+
+We don't want the production site using the same database as the
+development site.  We don't want staging using (and re-indexing, re-starting,
+etc.) production's search engine server.  We don't want any site other than
+production to send account reset emails, or to push orders out to fulfillment,
+etc.
+
+For some reason, the answer to this with cap and/or vlad has been to have
+recipes which reference various files up in a shared area on the server, do
+copying or symlinking, etc.  Where did those files come from?  How did they get
+there?  How are they managed over time?  If they got there via a configuration
+tool, why (a) are they not in the right place, or (b) do we have to do work to
+get them into the right place?
+
+So, we decided that we'd change how we deal with the issue.  Instead of
+moving files around or symlinking every time we deploy, we will manage the
+configuration data just like we manage other files required by our projects --
+with git.
+
+So, each project we deploy is associated with a config repo in our git
+repository.  Usually many projects are in the same repo, because we're the only
+people to see the data and there's no confidentiality issue.  But, if a
+customer has access to their git information then we'll make a separate config
+repo for all that customers' projects.  (This is easier to manage than it
+sounds if you're using gitosis, btw.)
+
+Anyway, a config repo is just a git repo.  In it are directories for every
+project whose configuration information is managed in that repo.  For example,
+there's a "larry" directory in our main config repo, because we're deploying
+the [larry project](http://github.com/rick/larry) to manage our high-level
+configuration data.
+
+Note, if you set the 'project' setting in deploy.yml, that determines the
+name of the top-level project directory whiskey\_disk will hunt for in your
+config repo.  If you don't it uses the 'repository' setting (i.e., the git URL)
+to try to guess what the project name might be.  So if the URL ends in
+foo/bar.git, or foo:bar.git, or /bar, or :bar, whiskey\_disk is going to guess
+"bar".  If it's all bitched up, just set 'project' manually in deploy.yml.
+
+Inside the project directory is a directory named for each target we
+might deploy to.  Frankly, we've been using "production", "staging",
+"development", and "local" on just about everything.
+
+Inside the target directory is a tree of files.  So, e.g., there's
+config/, which has initializers/ and database.yml in it.
+
+Long story short, load up whatever configuration files you're using into
+the repo as described, and come deployment time exactly those files will be
+overlaid on top of the most recent checkout of the project.  Snap.
+
+    project-config/
+      |
+      +---larry/
+            |
+            +---production/
+            |     |
+            |     +---config/
+            |           |
+            |           +---initializers/
+            |           |
+            |           +---database.yml
+            |
+            +---staging/
+            |     |
+            |     |
+            |     +---config/
+            |           |
+            |           ....
+            |
+            +---development/
+            |     |
+            |     +---config/
+            |           |
+            |           ....
+            |
+            +---local/
+                  |
+                  +---config/
+                        |
+                        ....
+
+ 
+
+  More Examples:
+
+  - We are using this to manage larry.  See [http://github.com/rick/larry/blob/master/config/deploy.yml](http://github.com/rick/larry/blob/master/config/deploy.yml) and 
+    [http://github.com/rick/larry/blob/master/lib/tasks/deploy.rake](http://github.com/rick/larry/blob/master/lib/tasks/deploy.rake)
+
+ - We are using whiskey\_disk on a private project with lots of config files, but here's
+    a gist showing a bit more interesting deploy.rake file for post_setup and
+post_deploy work:  [https://gist.github.com/47e23f2980943531beeb](https://gist.github.com/47e23f2980943531beeb)
+
+On the radar for an upcoming release are:
+
+ - common post_* recipes being specifiable by symbol names in deploy.yml ?
+ - bringing in a very simplified version of mislav/git-deploy post-{receive,reset} hooks, and a little sugar so you can say:
+
+        task :post_deploy do
+          if has_changes?('db/migrate') or has_changes?('config/database.yml')
+            Rake::Task['db:migrate'].invoke
+          end
+        end
+
+
+### Resources ###
+
+ - [http://github.com/blog/470-deployment-script-spring-cleaning](http://github.com/blog/470-deployment-script-spring-cleaning)
+ - [http://github.com/mislav/git-deploy](http://github.com/mislav/git-deploy)
+ - [http://toroid.org/ams/git-website-howto](http://toroid.org/ams/git-website-howto)
+
+

data/TODO.txt

@@ -1,5 +1,14 @@
  - would be nice to have the ability to say if a project is out of date (meaning that, based upon this config file, either the checked out project repo or the checked out config repo is older than the upstream) so we can do some sort of automated / conditional deployments.  We could implement this as a config file option (check for out of date before deploying), but questions about how to "force" if necessary.  Could also be done as a flag.
- 
+   by default, the behavior should be *not* to check if in-sync, make it so that ENV['check'] =~ /^(?:t(?:rue)?|1|y(?:es))/i will trigger the check
+   similarly wd --check will set the variable
+   
+   - the thinking is that a metadata file for multiple projects would specify values for this, with a meta-app using check=true by default
+
+   ml=`cat .git/refs/heads/master`; mr=`git ls-remote git@ogtastic.com:whiskey_disk.git refs/heads/master`; if [[ $ml != ${mr%%       *} ]]; then { echo "out-of-date"; } else { echo "up-to-date"; } fi  
+   
+   - note that we actually want to check both the main repository and the configuration repository for changes 
+   - this is only relevant for deploy:now, obviously
+   
  - do git-deploy style change detection:  get the current branch ref, then do the fetch/reset, get the current branch ref; find the differences, make them available to the rake task(s)
    - some sort of simple API to access the detected changes
      require 'whiskey_disk/rake'

data/VERSION

@@ -1 +1 @@
-0.3.0
+0.3.1

data/install.rb

@@ -1,5 +1,5 @@
 def readme_contents
-  IO.read(File.expand_path(File.join(File.dirname(__FILE__), 'README')))
+  IO.read(File.expand_path(File.join(File.dirname(__FILE__), 'README.markdown')))
 end
 
 puts readme_contents

data/lib/whiskey_disk/config.rb

@@ -18,16 +18,23 @@ class WhiskeyDisk
         (ENV['path'] && ENV['path'] != '') ? ENV['path'] : false
       end
       
+      def check_staleness?
+        !!(ENV['check'] && ENV['check'] =~ /^(?:t(?:rue)?|y(?:es)?|1)$/)
+      end
+      
       def contains_rakefile?(path)
         File.exists?(File.expand_path(File.join(path, 'Rakefile')))
       end
       
       def find_rakefile_from_current_path
+        original_path = Dir.pwd
         while (!contains_rakefile?(Dir.pwd))
-          raise "Could not find Rakefile in the current directory tree!" if Dir.pwd == '/'
+          return File.join(original_path, 'config') if Dir.pwd == '/'
           Dir.chdir('..')
         end
         File.join(Dir.pwd, 'config')
+      ensure
+        Dir.chdir(original_path)
       end
       
       def base_path

data/lib/whiskey_disk.rb

@@ -75,6 +75,10 @@ class WhiskeyDisk
       remote? ? run(bundle) : system(bundle)
     end
     
+    def if_file_present(path, cmd)
+      "if [ -e #{path} ]; then #{cmd}; fi"
+    end
+
     def ensure_main_parent_path_is_present
       needs(:deploy_to)
       enqueue "mkdir -p #{parent_path(self[:deploy_to])}"
@@ -120,13 +124,15 @@ class WhiskeyDisk
     def run_post_setup_hooks
       needs(:deploy_to)
       enqueue "cd #{self[:deploy_to]}"
-      enqueue "#{env_vars} rake --trace deploy:post_setup to=#{self[:environment]}"
+      enqueue(if_file_present("#{self[:deploy_to]}/Rakefile", 
+                               "#{env_vars} rake --trace deploy:post_setup to=#{self[:environment]}"))
     end
 
     def run_post_deploy_hooks
       needs(:deploy_to)
       enqueue "cd #{self[:deploy_to]}"
-      enqueue "#{env_vars} rake --trace deploy:post_deploy to=#{self[:environment]}"
+      enqueue(if_file_present("#{self[:deploy_to]}/Rakefile", 
+                               "#{env_vars} rake --trace deploy:post_deploy to=#{self[:environment]}"))
     end
   end
 end

data/spec/whiskey_disk/config_spec.rb

@@ -28,6 +28,43 @@ describe WhiskeyDisk::Config do
     end
   end
   
+  describe 'when determining whether to do a staleness check before updating' do
+    it 'should return false when there is no ENV["check"] setting' do
+      ENV['check'] = nil
+      WhiskeyDisk::Config.check_staleness?.should == false
+    end
+    
+    it 'should return false when the ENV["check"] setting is blank' do
+      ENV['check'] = ''
+      WhiskeyDisk::Config.check_staleness?.should == false      
+    end
+    
+    it 'should return true if the ENV["check"] setting is "t"' do
+      ENV['check'] = 't'
+      WhiskeyDisk::Config.check_staleness?.should == true      
+    end
+
+    it 'should return true if the ENV["check"] setting is "true"' do
+      ENV['check'] = 'true'
+      WhiskeyDisk::Config.check_staleness?.should == true
+    end
+
+    it 'should return true if the ENV["check"] setting is "y"' do
+      ENV['check'] = 'y'
+      WhiskeyDisk::Config.check_staleness?.should == true      
+    end
+
+    it 'should return true if the ENV["check"] setting is "yes"' do
+      ENV['check'] = 'yes'
+      WhiskeyDisk::Config.check_staleness?.should == true      
+    end
+
+    it 'should return true if the ENV["check"] setting is "1"' do
+      ENV['check'] = '1'
+      WhiskeyDisk::Config.check_staleness?.should == true      
+    end
+  end
+  
   describe 'when fetching configuration' do
     before do
       ENV['to'] = @env = 'foo:staging'
@@ -398,22 +435,54 @@ describe WhiskeyDisk::Config do
       ENV['path'] = @path = nil
     end
     
-    it 'should return the path set in the "path" environment variable when one is set' do
-      ENV['path'] = @path = CURRENT
-      WhiskeyDisk::Config.base_path.should == @path      
+    describe 'and a "path" environment variable is set' do
+      before do
+        ENV['path'] = @path = CURRENT
+        Dir.chdir(CURRENT)
+      end
+      
+      it 'should return the path set in the "path" environment variable' do
+        WhiskeyDisk::Config.base_path.should == @path      
+      end
+      
+      it 'should leave the current working path the same as when the base path lookup started' do
+        WhiskeyDisk::Config.base_path
+        Dir.pwd.should == CURRENT
+      end
     end
     
-    it 'should fail if there is no Rakefile along the root path to the current directory'  do
-      WhiskeyDisk::Config.stub!(:contains_rakefile?).and_return(false)
-      lambda { WhiskeyDisk::Config.base_path }.should.raise
-    end
+    describe 'and there is no Rakefile in the root path to the current directory' do
+      before do
+        Dir.chdir(CURRENT)
+        WhiskeyDisk::Config.stub!(:contains_rakefile?).and_return(false)
+      end
+      
+      it 'should return the config directory under the current directory if there is no Rakefile along the root path to the current directory' do
+        WhiskeyDisk::Config.base_path.should == File.join(CURRENT, 'config')
+      end
+      
+      it 'should leave the current working path the same as when the base path lookup started' do
+        WhiskeyDisk::Config.base_path
+        Dir.pwd.should == CURRENT
+      end
+    end    
     
-    it 'return the config directory in the nearest enclosing path with a Rakefile along the root path to the current directory' do
-      top = ::File.expand_path(File.join(CURRENT, '..', '..'))
-      WhiskeyDisk::Config.stub!(:contains_rakefile?).and_return(false)
-      WhiskeyDisk::Config.stub!(:contains_rakefile?).with(top).and_return(true)
-      Dir.chdir(CURRENT)
-      WhiskeyDisk::Config.base_path.should == File.join(top, 'config')
+    describe 'and there is a Rakefile in the root path to the current directory' do
+      before do
+        @top = ::File.expand_path(File.join(CURRENT, '..', '..'))
+        WhiskeyDisk::Config.stub!(:contains_rakefile?).and_return(false)
+        WhiskeyDisk::Config.stub!(:contains_rakefile?).with(@top).and_return(true)
+        Dir.chdir(CURRENT)
+      end
+      
+      it 'return the config directory in the nearest enclosing path with a Rakefile along the root path to the current directory' do
+        WhiskeyDisk::Config.base_path.should == File.join(@top, 'config')
+      end
+      
+      it 'should leave the current working path the same as when the base path lookup started' do
+        WhiskeyDisk::Config.base_path
+        Dir.pwd.should == CURRENT
+      end
     end
   end
 end

data/spec/whiskey_disk_spec.rb

@@ -334,6 +334,11 @@ describe 'WhiskeyDisk' do
       WhiskeyDisk.buffer.join(' ').should.match(%r{cd /path/to/main/repo})
     end
     
+    it 'should make the post setup rake tasks conditional on the presence of a Rakefile in the deployment path' do      
+      WhiskeyDisk.run_post_setup_hooks
+      WhiskeyDisk.buffer.join(' ').should.match(%r{if \[ -e /path/to/main/repo/Rakefile \]; then .*; fi})
+    end
+    
     it 'should attempt to run the post setup rake tasks' do
       WhiskeyDisk.run_post_setup_hooks
       WhiskeyDisk.buffer.join(' ').should.match(%r{rake.*deploy:post_setup})
@@ -373,6 +378,11 @@ describe 'WhiskeyDisk' do
       WhiskeyDisk.buffer.join(' ').should.match(%r{cd /path/to/main/repo})
     end
     
+    it 'should make the post deployment rake tasks conditional on the presence of a Rakefile in the deployment path' do      
+      WhiskeyDisk.run_post_deploy_hooks
+      WhiskeyDisk.buffer.join(' ').should.match(%r{if \[ -e /path/to/main/repo/Rakefile \]; then .*; fi})
+    end
+    
     it 'should attempt to run the post deployment rake tasks' do
       WhiskeyDisk.run_post_deploy_hooks
       WhiskeyDisk.buffer.join(' ').should.match(%r{rake.*deploy:post_deploy})

data/whiskey_disk.gemspec

@@ -5,22 +5,22 @@
 
 Gem::Specification.new do |s|
   s.name = %q{whiskey_disk}
-  s.version = "0.3.0"
+  s.version = "0.3.1"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["Rick Bradley"]
-  s.date = %q{2010-06-17}
+  s.date = %q{2010-07-08}
   s.default_executable = %q{wd}
   s.description = %q{Opinionated gem for doing fast git-based server deployments.}
   s.email = %q{rick@rickbradley.com}
   s.executables = ["wd"]
   s.extra_rdoc_files = [
-    "README"
+    "README.markdown"
   ]
   s.files = [
     ".gitignore",
      "MIT-LICENSE",
-     "README",
+     "README.markdown",
      "Rakefile",
      "TODO.txt",
      "VERSION",

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: whiskey_disk
 version: !ruby/object:Gem::Version 
-  hash: 19
+  hash: 17
   prerelease: false
   segments: 
   - 0
   - 3
-  - 0
-  version: 0.3.0
+  - 1
+  version: 0.3.1
 platform: ruby
 authors: 
 - Rick Bradley
@@ -15,7 +15,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2010-06-17 00:00:00 -05:00
+date: 2010-07-08 00:00:00 -05:00
 default_executable: wd
 dependencies: 
 - !ruby/object:Gem::Dependency 
@@ -39,11 +39,11 @@ executables:
 extensions: []
 
 extra_rdoc_files: 
-- README
+- README.markdown
 files: 
 - .gitignore
 - MIT-LICENSE
-- README
+- README.markdown
 - Rakefile
 - TODO.txt
 - VERSION

data/README

@@ -1,283 +0,0 @@
-Whiskey Disk -- embarrassingly fast deployments.
-
-  A very opinionated deployment tool, designed to be as fast as technologically possible.  (For more background, read the WHY.txt file)
-
-  Should work with any project which is git hosted, not just Ruby / Ruby on
-Rails projects.  Allows for local deploys as well as remote.
-
-  Selling points:
-
-  - If you share the same opinions there's almost no code involved, almost no
-    dependencies, and it uses stock *nix tools (ssh, bash, rsync) to get
-everything done.
-
-  - Written completely spec-first for 100% coverage.  We even did that for the
-    rake tasks, the init.rb and the plugin install.rb if you swing that way.
-
-  - 1 ssh connection per rake task -- so everything needed to do a full setup
-    is done in one shot.  Everything needed to do a full deployment is done in
-one shot.  Having 8 minute deploys failing because I was on cdma wireless on a
-train in india where the connection won't stay up for more than 2-3 minutes is
-not where I want to be.
-
-  - You can do *local* deployments, by this I mean you can use whiskey_disk to
-    deploy fully running instances of your application to the same machine
-you're developing on.  This turns out to be surprisingly handy (well, I was
-surprised).  *NOTE*:  be sure to set your deploy_to to a place other than the
-current local checkout.
-
-  - You can have per-developer configurations for environments (especially
-    useful for "local" or "development" enviroments).  Use .gitignore, or
-specify a config_branch and everyone can have their own local setup that just
-works.
-
-  - Deployment configuration is specified as YAML data, not as code.
-    Operations to perform after setup or deployment are specified as rake
-tasks.
-
-  - There's no before_after_before_after hooks.  You've got plenty of
-    flexibility with just a handful of rake hook points to grab onto.
- 
-  - rake deploy:setup and rake deploy:now are really all that are needed, best
-    I can tell.
-
-
-
-  Dependencies:  rake, ssh, git, rsync on the deployment target server (affectionately
-                 referred to as the "g-node" by vinbarnes), bash-ish shell on deployment
-                 server.
-
-  Assumptions:
-
-    - you have a Rakefile in the top directory of your project's checkout
-    - you are deploying over ssh
-    - your project is managed via git
-    - you have a second git repository for per-application/per-environment configuration files
-    - you are comfortable defining post-setup and post-deployment actions with rake
-
-  Installation:
-
-    As a gem:
-
-    % gem install whiskey_disk
-
-    As a rails plugin:
-
-    % script/plugin install git://github.com/flogic/whiskey_disk.git
-
-  Configuration:
-
-    - look in the examples/ directory for sample configuration files
-    - main configuration is in <app_root>/config/deploy.yml
-    - config files are YAML, with a section for each environment.
-
-      Known config file settings (if you're familiar with capistrano and vlad these
-      should seem eerily familiar)::
- 
-      - domain:            host on which to deploy (this is an ssh connect string) 
-      - deploy_to:         path to which to deploy main application
-      - repository:        git repo path for main application
-      - branch:            git branch to deploy from main application git repo (default: master)
-      - deploy_config_to:  where to deploy the configuration repository
-      - config_repository: git repository for configuration files
-      - config_branch:     git branch to deploy from configuration git repo (default: master)
-      - project:           project name (used to compute path in configuration checkout)
-      - rake_env:          hash of environment variables to set when running post_setup and post_deploy rake tasks
-
-    - defining a deploy:<environment>:post_setup rake task (e.g., in lib/tasks/
-      or in your project's Rakefile) will cause that task to be run at the end
-of deploy:setup
-
-    - defining a deploy:<environment>:post_deploy rake task (e.g., in
-      lib/tasks/ or in your project's Rakefile) will cause that task to be run
-at the end of deploy:now
-
-
-  Running via rake:
-
-  ... in your Rakefile:
-
-  require 'whiskey_disk/rake'
-
-  Then, from the command-line:
-
-  % rake deploy:setup to=<target>   (e.g., "staging", "production", etc.)
-  % rake deploy:now   to=<target>
-
-  or, specifying the project name:
-
-  % rake deploy:setup to=<project>:<target>   (e.g., "foo:staging", "bar:production", etc.)
-  % rake deploy:now   to=<project>:<target>
-
-
-  Running from the command-line:
-  
-  % wd setup --to=<target>
-  % wd setup --to=<project>:<target>
-  % wd setup --to=foo:staging --path=/etc/whiskey_disk/deploy.yml
-
-  % wd deploy --to=<target>
-  % wd deploy --to=<project>:<target>
-  % wd deploy --to=foo:staging --path=/etc/whiskey_disk/deploy.yml
-
-
-  Note that the wd command (unlike rake, which requires a Rakefile in the current directory) can be run from anywhere, so you can deploy any project, working from any path, and can even specify where to find the deployment YAML configuration file.
-  
-  The --path argument can take either a file or a directory.  When given a file it will use that file as the configuration file.  When given a directory it will look in that directory for deploy/<project>/<target>.yml, then deploy/<project>.yml, then deploy/<target>.yml, then <target>.yml, and finally, deploy.yml.
-  
-  All this means you can manage a large number of project deployments (local or remote) and have a single scripted deployment manager that keeps them up to date.  Configurations can live in a centralized location, and developers don't have to be actively involved in ensuring code gets shipped up to a server.  Win.
-
-
-  Configuration Repository
-
-    What's all this about a second repository for configuration stuff?
-
-    This is completely optional, but we really are digging this, so maybe 
-you should try it.  Basically it goes like this...
-
-    We have a number of web applications that we manage.  Usually there's a
-customer, there might be third-party developers, or the customer might have
-access to the git repo, or their designer might, etc.  We also tend to run a
-few instances of any given app, for any given customer.  So, we'll run a
-"production" site, which is the public- facing, world-accessible main site.
-We'll usually also run a "staging" site, which is roughly the same code, maybe
-the same data, running on a different URL, which the customer can look at to
-see if the functionality there is suitable for deploying out to production.  We
-sometimes run a "development" site which is even less likely to be the same
-code as production, etc., but gives visibility into what might end up in
-production one day soon.
-
-    So we'll store the code for all of these versions of a site in the same git
-repo, typically using a different remote branch for each environment
-("production", "staging", "development").
-
-    One thing that comes up pretty quickly is that there are various files
-associated with the application which have more to do with configuration of a
-running instance than they have to do with the application in general.  In the
-rails world these files are probably in config, or config/initializers/.  Think
-database connection information, search engine settings, exception notification
-plugin data, email configuration, Amazon S3 credentials, e-commerce back-end
-configuration, etc.
-
-    We don't want the production site using the same database as the
-development site.  We don't want staging using (and re-indexing, re-starting,
-etc.) production's search engine server.  We don't want any site other than
-production to send account reset emails, or to push orders out to fulfillment,
-etc.
-
-    For some reason, the answer to this with cap and/or vlad has been to have
-recipes which reference various files up in a shared area on the server, do
-copying or symlinking, etc.  Where did those files come from?  How did they get
-there?  How are they managed over time?  If they got there via a configuration
-tool, why (a) are they not in the right place, or (b) do we have to do work to
-get them into the right place?
-
-    So, we decided that we'd change how we deal with the issue.  Instead of
-moving files around or symlinking every time we deploy, we will manage the
-configuration data just like we manage other files required by our projects --
-with git.
-
-    So, each project we deploy is associated with a config repo in our git
-repository.  Usually many projects are in the same repo, because we're the only
-people to see the data and there's no confidentiality issue.  But, if a
-customer has access to their git information then we'll make a separate config
-repo for all that customers' projects.  (This is easier to manage than it
-sounds if you're using gitosis, btw.)
-
-    Anyway, a config repo is just a git repo.  In it are directories for every
-project whose configuration information is managed in that repo.  For example,
-there's a "larry" directory in our main config repo, because we're deploying
-the larry project (http://github.com/rick/larry) to manage our high-level
-configuration data.
-
-    Note, if you set the 'project' setting in deploy.yml, that determines the
-name of the top-level project directory whiskey_disk will hunt for in your
-config repo.  If you don't it uses the 'repository' setting (i.e., the git URL)
-to try to guess what the project name might be.  So if the URL ends in
-foo/bar.git, or foo:bar.git, or /bar, or :bar, whiskey_disk is going to guess
-"bar".  If it's all bitched up, just set 'project' manually in deploy.yml.
-
-    Inside the project directory is a directory named for each environment we
-might deploy to.  Frankly, we've been using "production", "staging",
-"development", and "local" on just about everything.
-
-    Inside the environment directory is a tree of files.  So, e.g., there's
-config/, which has initializers/ and database.yml in it.
-
-    Long story short, load up whatever configuration files you're using into
-the repo as described, and come deployment time exactly those files will be
-overlaid on top of the most recent checkout of the project.  Snap.
-
-    project-config/
-      |
-      +---larry/
-            |
-            +---production/
-            |     |
-            |     +---config/
-            |           |
-            |           +---initializers/
-            |           |
-            |           +---database.yml
-            |
-            +---staging/
-            |     |
-            |     |
-            |     +---config/
-            |           |
-            |           ....
-            |
-            +---development/
-            |     |
-            |     +---config/
-            |           |
-            |           ....
-            |
-            +---local/
-                  |
-                  +---config/
-                        |
-                        ....
-
- 
-
-  More Examples:
-
-  - We are using this to manage larry.  See:
-
-    http://github.com/rick/larry/blob/master/config/deploy.yml
-    http://github.com/rick/larry/blob/master/lib/tasks/deploy.rake
-
-    Note that you can also provide per-environment config settings, outside of
-deploy.yml.  This is most useful for handling per-developer local deployments,
-though you could use it to override some settings if that makes sense in some
-context.  Here's a simple example of that:
-
-    http://github.com/rick/larry/blob/master/config/deploy-local.yml.example
-
-
-  - We are using it on a private project with lots of config files, but here's
-    a gist showing a bit more interesting deploy.rake file for post_setup and
-post_deploy work:
-
-    https://gist.github.com/47e23f2980943531beeb
-
-  On the radar for an upcoming release are:
-
-  - common post_* recipes being specifiable by symbol names in deploy.yml ?
-  - bringing in a very simplified version of mislav/git-deploy
-    post-{receive,reset} hooks, and a little sugar so you can say:
-
-    task :post_deploy do
-      if has_changes?('db/migrate') or has_changes?('config/database.yml')
-        Rake::Task['db:migrate'].invoke
-      end
-    end
-
-
-  Resources:
-    - http://github.com/blog/470-deployment-script-spring-cleaning
-    - http://github.com/mislav/git-deploy
-    - http://toroid.org/ams/git-website-howto
-
-