pulsar 0.3.0 → 0.3.1

data/README.md

@@ -38,7 +38,7 @@ $ pulsar-utils init ~/Desktop/pulsar-conf
 This will create a basic start point for building your configuration repository. As soon as you're done configuring
 you should consider storing this folder as an actual git repository.
 
-Here it is possible to see how this configuration repository will look like: [Pulsar Conf Demo](http://github.com/nebulab/pulsar-conf-demo) 
+Here it is possible to see how this configuration repository will look like: [Pulsar Conf Demo](http://github.com/nebulab/pulsar-conf-demo)
 
 **NOTE**: Pulsar only supports git and *nix systems.
 
@@ -133,7 +133,7 @@ end
 
 You can specify some recipes to be loaded only when you run Pulsar from inside a Rack application directory.
 This is useful with recipes that require something inside that directory (like retrieving the database/assets
-from a staging environment). 
+from a staging environment).
 
 You can do that like this:
 
@@ -143,7 +143,7 @@ You can do that like this:
 #
 
 #
-# These recipes will be available only if you're running 
+# These recipes will be available only if you're running
 # Pulsar inside a Rack application (like Rails) directory
 #
 load_recipes(app_only: true) do
@@ -156,8 +156,9 @@ end
 Once the repository is ready, you'll need to tell Pulsar where it is. The repository location can be specified either
 as a full git path or a github repository path (`gh-user/pulsar-conf`).
 
-Since Pulsar requires the repository for everything, there are multiple ways to store this information so that 
-you don't have to type it everytime.
+Since Pulsar requires the repository for everything, there are multiple ways to store this information so that
+you don't have to type it everytime. You can also use local repository, which is useful while developing your
+deployment.
 
 You have three possibilities:
 
@@ -171,7 +172,12 @@ The fastest way is probably the `.pulsar` hidden file inside your home directory
 #
 # Inside ~/.pulsar
 #
-PULSAR_CONF_REPO="gh-user/pulsar-conf" 
+PULSAR_CONF_REPO="gh-user/pulsar-conf"
+
+#
+# You can use local repository for development so you don't need to push changes every time
+#
+# PULSAR_CONF_REPO="/full/path/to/repository"
 
 #
 # Also supported
@@ -189,7 +195,7 @@ If you don't want to add another file to your home directory you can export the
 #
 # Inside ~/.bash_profile or ~/.zshrc
 #
-export PULSAR_CONF_REPO="gh-user/pulsar-conf" 
+export PULSAR_CONF_REPO="gh-user/pulsar-conf"
 ```
 
 ## Usage
@@ -210,7 +216,7 @@ $ pulsar my_application staging deploy:migrations
 $ pulsar my_application staging shell
 
 #
-# Deploy multiple apps by using commas 
+# Deploy multiple apps by using commas
 #
 $ pulsar my_app1,my_app2,my_app3 production
 ```

data/lib/pulsar.rb

@@ -4,6 +4,7 @@ module Pulsar
   require "clamp"
   require "bundler"
   require "colored"
+  require "shellwords"
   require "pulsar/helpers/all"
   require "pulsar/options/all"
   require "pulsar/commands/all"

data/lib/pulsar/commands/main.rb

@@ -31,7 +31,7 @@ module Pulsar
             build_capfile(app, stage)
 
             unless skip_cap_run?
-              cap_args = [ tasks_list ].flatten.join(" ")
+              cap_args = [ tasks_list ].flatten.shelljoin
               run_capistrano(cap_args)
             end
           ensure

data/lib/pulsar/helpers/clamp.rb

@@ -61,11 +61,7 @@ module Pulsar
         end
 
         def fetch_directory_repo(repo)
-          if File.directory?("#{repo}/.git")
-            fetch_git_repo(repo, true)
-          else
-            run_cmd("cp -rp #{repo} #{config_path}", :verbose => verbose?)
-          end
+          run_cmd("cp -rp #{repo} #{config_path}", :verbose => verbose?)
         end
 
         def fetch_git_repo(repo, local=false)

data/lib/pulsar/version.rb

@@ -1,3 +1,3 @@
 module Pulsar
-  VERSION = "0.3.0"
+  VERSION = "0.3.1"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: pulsar
 version: !ruby/object:Gem::Version
-  version: 0.3.0
+  version: 0.3.1
   prerelease: 
 platform: ruby
 authors:
@@ -10,7 +10,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-07-23 00:00:00.000000000 Z
+date: 2013-07-26 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: clamp
@@ -210,21 +210,15 @@ required_ruby_version: !ruby/object:Gem::Requirement
   - - ! '>='
     - !ruby/object:Gem::Version
       version: '0'
-      segments:
-      - 0
-      hash: 2226446731285894531
 required_rubygems_version: !ruby/object:Gem::Requirement
   none: false
   requirements:
   - - ! '>='
     - !ruby/object:Gem::Version
       version: '0'
-      segments:
-      - 0
-      hash: 2226446731285894531
 requirements: []
 rubyforge_project: 
-rubygems_version: 1.8.25
+rubygems_version: 1.8.23
 signing_key: 
 specification_version: 3
 summary: Pulsar helps with Capistrano configuration management. It uses a repository