minicap 1.0.4 → 1.0.5

data/README.md

@@ -15,7 +15,11 @@ Minicap also has two features that the stock deployment recipes lack;
 
 ## Using Minicap
 
-To use minicap, your project's `Capfile` should look like 
+First, install minicap
+
+    gem install minicap
+
+Then set up your project to use minicap, by making your project's `Capfile` look like 
  
     require 'rubygems'
     require 'minicap'
@@ -25,5 +29,5 @@ Copy the contents of minicap's `examples/deploy.rb` as a jumping off point for y
 
 ## 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
+ * Transparent support for templated files. No more jumping through hoops to get a `database.yml` file up to production
+ * Built-in notification emails, ala cap-gun

metadata

@@ -5,8 +5,8 @@ version: !ruby/object:Gem::Version
   segments: 
   - 1
   - 0
-  - 4
-  version: 1.0.4
+  - 5
+  version: 1.0.5
 platform: ruby
 authors: 
 - Mat Trudel
@@ -14,10 +14,22 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2010-10-03 00:00:00 -04:00
+date: 2010-11-09 00:00:00 -05:00
 default_executable: 
-dependencies: []
-
+dependencies: 
+- !ruby/object:Gem::Dependency 
+  name: capistrano
+  prerelease: false
+  requirement: &id001 !ruby/object:Gem::Requirement 
+    none: false
+    requirements: 
+    - - ">="
+      - !ruby/object:Gem::Version 
+        segments: 
+        - 0
+        version: "0"
+  type: :runtime
+  version_requirements: *id001
 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