whiskey_disk 0.6.3 → 0.6.4

data/CHANGELOG

@@ -1,4 +1,11 @@
 
+0.6.4 / 2011-01-26 
+==================
+
+  * bugfix: cd to deploy_to path before running post_{setup,deploy}_script
+  * update gemspec
+  * Version bump to 0.6.4
+
 0.6.3 / 2011-01-13 
 ==================
 

data/VERSION

@@ -1 +1 @@
-0.6.3
+0.6.4

data/lib/whiskey_disk.rb

@@ -194,7 +194,7 @@ class WhiskeyDisk
     def run_script(script)
       return unless script
       path = build_path(script)
-      enqueue("if [ -e #{path} ]; then sh -x #{path}; fi ")
+      enqueue("if [ -e #{path} ]; then cd #{self[:deploy_to]}; sh -x #{path}; fi ")
     end
 
     def ensure_main_parent_path_is_present

data/spec/whiskey_disk_spec.rb

@@ -357,6 +357,11 @@ describe 'WhiskeyDisk' do
           WhiskeyDisk.buffer.join(' ').should.match(%r{sh -x .*/path/to/setup/script})
         end
       
+        it 'should cd to the deploy_to path prior to running the script' do
+          WhiskeyDisk.run_post_setup_hooks
+          WhiskeyDisk.buffer.join(' ').should.match(%r{cd /path/to/main/repo; sh -x /path/to/setup/script})
+        end
+            
         it 'should use an absolute path to run the post setup script when the script path starts with a "/"' do
           WhiskeyDisk.run_post_setup_hooks
           WhiskeyDisk.buffer.join(' ').should.match(%r{sh -x /path/to/setup/script})         
@@ -378,7 +383,12 @@ describe 'WhiskeyDisk' do
           WhiskeyDisk.buffer.join(' ').should.match(%r{sh -x .*/path/to/setup/script})
         end
       
-        it 'should use a path relative to the setupment path to run the post setup script' do
+        it 'should cd to the deploy_to path prior to running the script' do
+          WhiskeyDisk.run_post_setup_hooks
+          WhiskeyDisk.buffer.join(' ').should.match(%r{cd /path/to/main/repo; sh -x /path/to/main/repo/path/to/setup/script})
+        end
+      
+        it 'should use a path relative to the setup path to run the post setup script' do
           WhiskeyDisk.run_post_setup_hooks
           WhiskeyDisk.buffer.join(' ').should.match(%r{sh -x /path/to/main/repo/path/to/setup/script})
         end
@@ -454,7 +464,12 @@ describe 'WhiskeyDisk' do
           WhiskeyDisk.run_post_deploy_hooks
           WhiskeyDisk.buffer.join(' ').should.match(%r{sh -x .*/path/to/deployment/script})
         end
-      
+        
+        it 'should cd to the deploy_to path prior to running the script' do
+          WhiskeyDisk.run_post_deploy_hooks
+          WhiskeyDisk.buffer.join(' ').should.match(%r{cd /path/to/main/repo; sh -x /path/to/deployment/script})
+        end
+        
         it 'should use an absolute path to run the post deployment script when the script path starts with a "/"' do
           WhiskeyDisk.run_post_deploy_hooks
           WhiskeyDisk.buffer.join(' ').should.match(%r{sh -x /path/to/deployment/script})         
@@ -476,6 +491,11 @@ describe 'WhiskeyDisk' do
           WhiskeyDisk.buffer.join(' ').should.match(%r{sh -x .*/path/to/deployment/script})
         end
       
+        it 'should cd to the deploy_to path prior to running the script' do
+          WhiskeyDisk.run_post_deploy_hooks
+          WhiskeyDisk.buffer.join(' ').should.match(%r{cd /path/to/main/repo; sh -x /path/to/main/repo/path/to/deployment/script})
+        end
+        
         it 'should use a path relative to the deployment path to run the post deployment script' do
           WhiskeyDisk.run_post_deploy_hooks
           WhiskeyDisk.buffer.join(' ').should.match(%r{sh -x /path/to/main/repo/path/to/deployment/script})

data/whiskey_disk.gemspec

@@ -5,11 +5,11 @@
 
 Gem::Specification.new do |s|
   s.name = %q{whiskey_disk}
-  s.version = "0.6.3"
+  s.version = "0.6.4"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["Rick Bradley"]
-  s.date = %q{2011-01-13}
+  s.date = %q{2011-01-26}
   s.description = %q{Opinionated gem for doing fast git-based server deployments.}
   s.email = %q{rick@rickbradley.com}
   s.executables = ["wd_role", "wd"]
@@ -21,7 +21,6 @@ Gem::Specification.new do |s|
     "MIT-LICENSE",
     "README.markdown",
     "Rakefile",
-    "TODO.txt",
     "VERSION",
     "WHY.txt",
     "bin/wd",

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: whiskey_disk
 version: !ruby/object:Gem::Version 
-  hash: 1
+  hash: 15
   prerelease: false
   segments: 
   - 0
   - 6
-  - 3
-  version: 0.6.3
+  - 4
+  version: 0.6.4
 platform: ruby
 authors: 
 - Rick Bradley
@@ -15,7 +15,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2011-01-13 00:00:00 -06:00
+date: 2011-01-26 00:00:00 -08:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency 
@@ -46,7 +46,6 @@ files:
 - MIT-LICENSE
 - README.markdown
 - Rakefile
-- TODO.txt
 - VERSION
 - WHY.txt
 - bin/wd

data/TODO.txt

@@ -1,36 +0,0 @@
- - if someone specifies :project in a config repo block in a localized config (say a RAILS app), then use that for determining which project to use when loading the config repo
-
- - batch deployments (--batch=/etc/deploy/hourly.yml)
-   - could have this simply pointing to a single yaml file with project name, target name, check value (default = true) (business value:  only need one command, or one cron, to manage all of these)
-   - could be a directory of individual yaml files with that information in each of them (representing one project, one target) (business value:  puppet/chef could more easily manage directories of files)
-   - trying to avoid re-using the deploy.yml because we may want to not auto-deploy all things that we have configurations for, or we may want to auto-deploy them at different frequencies
-   - do we want the config path to be in the meta file, or do we want that to come as part of the arguments to the deployment?
-
-     wd deploy --batch=/etc/deploy/hourly.yml --path=/etc/deploy/projects/
-     wd deploy --batch=/etc/deploy/hourly/ --path=/etc/deploy/projects/
-     wd deploy --batch=/etc/deploy/hourly.yml --path=/etc/deploy/deploy.yml
-     wd deploy --batch=/etc/deploy/hourly --path=/etc/deploy/projects/deploy.yml
-
- - allow whiskey_disk to pull configuration file from an url (which would be based on project, environment)
-
- - 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)
-     we can use the ml/cl part of staleness checking to get the "before" versions of the main and config repos (i.e., leave that part in always, just not the conditional stuff), and have the main run a script which dumps the relative paths of changed files as a .whiskey_disk-paths-changed in the main checkout
-     
-   - some sort of simple API to access the detected changes:
-     require 'whiskey_disk/rake'
-   
-     namespace :deploy do
-       task :post_deploy do 
-         if changed_in?('db/migrate') or changed?('config/database.yml')
-           Rake::Task['db:migrate'].invoke
-         end
-         # etc. ...
-       end
-     end
-
- - [Q] what about maintenance pages(?) (i.e., do we need a pre-deploy hook?; also are these per-target config stuffs?; fun managing changes to a maintenance page ;-)
- - [Q] do we want a mechanism to manage the config repo?  (add a repo, add a project, add an environment, put a file into the config repo for an environment?)
- - [Q] what about per-target rake tasks, do we just store these in the config repo?  does this work?
- - [Q] do we need actual support for "rollbacks"?
- - [Q] do we want to support multi-system deployments (i.e., deploy and rollback on 4 simultaneous app servers, other bullshit running on the db server, etc.)?  If we get into this, we have the original :role problem that cap faced -- i.e., we only want to run the database operations on certain hosts.