minicap 0.0.1

data/LICENCE

@@ -0,0 +1 @@
+BSD

data/README.md

@@ -0,0 +1,23 @@
+# Minicap
+
+Minicap replaces the stock [capistrano](http://capify.org) recipes with a small, git-centric deployment strategy that eschews the power and flexibility of capistrano's (excellent, btw) default recipes, and replaces them with something smaller, faster and easier to grok.
+
+Minicap is formalization of some work we've been doing with side project deployments at [well.ca](http://well.ca), originally inspired by Chris Wanstrath's [take](http://github.com/blog/470-deployment-script-spring-cleaning) on the subject. I got tired of maintaining separate yet nearly identical `deploy.rb` files in every side project, and realized where there was commonality, there was an opportunity to factor some behaviour up into stock recipes. Now the project `deploy.rb` files just contain a bunch of `set` statements, and a few (very minor) amendments to the minicap recipes.
+
+Minicap requires that you use git as a repository, and that `git` is present
+on the server. Deployments are not atomic (but since they're based on `git reset --hard`, they're pretty damn close). 
+
+Minicap also has two features that the stock deployment recipes lack;
+
+ 1. Better (or at least more transparent) support for shared files. Since your deployment is just a git repo, files that need to persist between deployments can just live right in your server's working copy. Minicap has an optional task (enabled by enabling `look_for_orphans`) which scans for untracked files on your remote repo. Since any shared files should probably be in your `.gitignore` anyway, this really just reinforces a best practice. 
+
+ 2. Checking for unpushed changes. If you enable `pedantic_remote`, deployments will fail if your local HEAD is newer than the branch pulled down on the remote server. This is usually indicative of your forgetting to do a `git push` before a `cap deploy`, and helps prevent those 'why didn't my deployment change anything?' moments.
+
+## Using Minicap
+
+The easiest way to start using minicap is to change the first line of your project's `Capfile` to `load 'minicap'`. Copy the contents of minicap's `examples/deploy.rb` as a jumping off point for your project's `deploy.rb`.
+
+## Coming soon
+
+ * Better multistage support. This will probably just lean on cap's multistage support, but I may make it a little cleaner
+ * Transparent support for templated files. No more jumping through hoops to get a `database.yml` file up to production

data/lib/minicap.rb

@@ -0,0 +1,71 @@
+require 'capistrano/recipes/deploy/scm'
+
+default_run_options[:pty] = true # Needed for debian based servers
+set :ssh_options, {:forward_agent => true}
+ 
+namespace :deploy do
+  desc "Set up the deployment structure"
+  task :setup, :except => { :no_release => true } do
+    run "mkdir -p #{deploy_to}"
+    run_gregarious "[ -d #{deploy_to}/.git ] || git clone -q #{repository} #{deploy_to}"
+    unversioned_dirs.each { |d| run "mkdir -p #{deploy_to + '/' + d}" } if exists? :unversioned_dirs
+  end
+ 
+  desc "Update the deployed code"
+  task :default, :except => { :no_release => true } do
+    fetch
+    deploy.check_yr_head if fetch(:pedantic_remote, false) && branch !~ /HEAD/
+    update_code
+    orphans if fetch(:look_for_orphans, false)
+  end
+  
+  desc "Fetches the latest from the repo"
+  task :fetch do
+    run_gregarious "cd #{deploy_to} ; git fetch -q origin"
+  end
+  
+  desc "Aborts if remote's HEAD is different than ours"
+  task :check_yr_head do
+    remote = capture("cd #{deploy_to} ; git show-ref origin/#{branch}").split[0]
+    local = `git show-ref #{branch}`.split[0]
+    abort "It looks like you haven't pushed your changes yet. Aborting
+    Your  HEAD is #{local[0,7]}
+    Their HEAD is #{remote[0,7]}" if local != remote
+  end  
+  
+  desc "Does a git reset to get the repo looking like branch"
+  task :update_code do
+    run "cd #{deploy_to} ; git reset --hard origin/#{branch}"
+  end
+  
+  desc "Reports back on remote files that didn't come from git, or aren't ignored by git"
+  task :orphans do
+    orphans = capture "cd #{deploy_to} ; git ls-files -o"
+    unless orphans.empty?
+      logger.important <<-EOF 
+        The following files are present in the deployment, and are unaccounted for
+        You may want to manually slay them, or else add them to .gitignore
+        
+        #{orphans} 
+      EOF
+    end
+  end
+  
+  desc "Rollback a single commit"
+  task :rollback, :except => { :no_release => true } do
+    set :branch, "HEAD^"
+    default
+  end
+end
+
+#
+# Runs the given command via cap's wrapper, which handles things like ssh host
+# key messages, passphrase prompts, and the like
+#
+def run_gregarious(cmd)
+  run cmd do |ch,stream,text|
+    ch[:state] ||= { :channel => ch }
+    output = Capistrano::Deploy::SCM.new(:git, self).handle_data(ch[:state], stream, text)
+    ch.send_data(output) if output
+  end
+end

metadata

@@ -0,0 +1,72 @@
+--- !ruby/object:Gem::Specification 
+name: minicap
+version: !ruby/object:Gem::Version 
+  hash: 29
+  prerelease: false
+  segments: 
+  - 0
+  - 0
+  - 1
+  version: 0.0.1
+platform: ruby
+authors: 
+- Mat Trudel
+autorequire: 
+bindir: bin
+cert_chain: []
+
+date: 2010-07-15 00:00:00 -04:00
+default_executable: 
+dependencies: []
+
+description: |-
+  Minicap provides a minimal yet functional set of git specific cap recipes. 
+      Minicap's recipes roughly mimic those in the standard capistrano distribution, but are 
+      much smaller and faster to understand'
+email: mat@well.ca
+executables: []
+
+extensions: []
+
+extra_rdoc_files: []
+
+files: 
+- README.md
+- LICENCE
+- lib/minicap.rb
+has_rdoc: true
+homepage: 
+licenses: []
+
+post_install_message: 
+rdoc_options: []
+
+require_paths: 
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement 
+  none: false
+  requirements: 
+  - - ">="
+    - !ruby/object:Gem::Version 
+      hash: 3
+      segments: 
+      - 0
+      version: "0"
+required_rubygems_version: !ruby/object:Gem::Requirement 
+  none: false
+  requirements: 
+  - - ">="
+    - !ruby/object:Gem::Version 
+      hash: 3
+      segments: 
+      - 0
+      version: "0"
+requirements: []
+
+rubyforge_project: 
+rubygems_version: 1.3.7
+signing_key: 
+specification_version: 3
+summary: Minicap provides a minimal yet functional set of git specific cap recipes
+test_files: []
+