zorros-deploy 0.0.2 → 0.0.3

data/History.md

@@ -1,4 +1,11 @@
 
+v.0.0.3 / 2011-09-29 
+==================
+
+  * Push the tag once it is created
+  * Tag after deploy:migrations.
+  * Added some doc and MIT license
+
 v.0.0.2 / 2011-09-28
 ==================
 

data/LICENSE.md

@@ -0,0 +1,21 @@
+The MIT License
+
+Copyright (c) 2011 Zorros
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,26 @@
+# Zorros-deploy gem
+
+
+That's only a sample gem done to show the Zorros people how to create a small
+gem.
+
+It's only purpose is to add a tag to the git repository of a project each time
+it's deployed with capistrano. It heavily follows our way of working so it will
+probably **not fit for you**. But if it does, please, feel free to give us a
+hand with it!
+
+## How to use it
+
+The gem supposes you've a multistage environment set up. You'll need to include
+it on your `config/deploy/production.rb` file, like that.
+
+```ruby
+require 'zorros-deploy/capistrano'
+```
+
+Once you've done it, you'll have a small task on capistrano wich will
+automatically create a git tag with the format `dd-mm-yyyy` each time you
+deploy to production.
+
+The tag will be created in your working copy's current branch, so make sure
+you're in the branch/commit you're deploying to tag the right thing.

data/lib/zorros-deploy/capistrano.rb

@@ -1,8 +1,9 @@
 require 'git'
 Capistrano::Configuration.instance(:must_exist).load do
 
-  # Create a task after updating the code
+  # Create a tag after updating the code
   after "deploy:update_code", "zorros:tag_release"
+  after "deploy:migrations", "zorros:tag_release"
 
   namespace :zorros do
     desc "Create a GIT tag on each deploy"
@@ -18,7 +19,7 @@ Capistrano::Configuration.instance(:must_exist).load do
                  end
 
       git.add_tag tag_name
-      git.push
+      git.push "origin", "master", true
     end
   end
 end

data/lib/zorros-deploy/version.rb

@@ -1,5 +1,5 @@
 module Zorros
   module Deploy
-    VERSION = "0.0.2"
+    VERSION = "0.0.3"
   end
 end

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: zorros-deploy
 version: !ruby/object:Gem::Version 
-  hash: 27
+  hash: 25
   prerelease: 
   segments: 
   - 0
   - 0
-  - 2
-  version: 0.0.2
+  - 3
+  version: 0.0.3
 platform: ruby
 authors: 
 - Francisco J. Casas, Zorros
@@ -15,7 +15,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2011-09-28 00:00:00 +02:00
+date: 2011-09-29 00:00:00 +02:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency 
@@ -73,6 +73,8 @@ files:
 - .gitignore
 - Gemfile
 - History.md
+- LICENSE.md
+- README.md
 - Rakefile
 - lib/zorros-deploy.rb
 - lib/zorros-deploy/capistrano.rb