railsless-deploy 1.0.2 → 1.1.0

data/README.markdown

@@ -18,6 +18,8 @@ Open your application's `Capfile` and make it begins like this:
     require 'railsless-deploy'
     load    'config/deploy'
 
+Taking care to remove the original `require 'deploy'` as this is where all the standard tasks are defined.
+
 You should then be able to proceed as you would usually, you may want to familiarise yourself with the truncated list of tasks, you can get a full list with:
 
     $ cap -T

data/VERSION

@@ -1 +1 @@
-1.0.2
+1.1.0

data/lib/railsless-deploy.rb

@@ -61,10 +61,10 @@ Capistrano::Configuration.instance(:must_exist).load do
 
   _cset(:run_method)        { fetch(:use_sudo, true) ? :sudo : :run }
 
-  # some tasks, like symlink, need to always point at the latest release, but
+  # some tasks, like create_symlink, need to always point at the latest release, but
   # they can also (occassionally) be called standalone. In the standalone case,
   # the timestamped release_path will be inaccurate, since the directory won't
-  # actually exist. This variable lets tasks like symlink work either in the
+  # actually exist. This variable lets tasks like create_symlink work either in the
   # standalone case, or during deployment.
   _cset(:latest_release) { exists?(:deploy_timestamped) ? release_path : current_release }
 
@@ -174,7 +174,7 @@ Capistrano::Configuration.instance(:must_exist).load do
 
     desc <<-DESC
       Copies your project and updates the symlink. It does this in a \
-      transaction, so that if either `update_code' or `symlink' fail, all \
+      transaction, so that if either `update_code' or `create_symlink' fail, all \
       changes made to the remote servers will be rolled back, leaving your \
       system in the same state it was in before `update' was invoked. Usually, \
       you will want to call `deploy' instead of `update', but `update' can be \
@@ -183,7 +183,7 @@ Capistrano::Configuration.instance(:must_exist).load do
     task :update do
       transaction do
         update_code
-        symlink
+        create_symlink
       end
     end
 
@@ -233,7 +233,7 @@ Capistrano::Configuration.instance(:must_exist).load do
       deploy, including `restart') or the 'update' task (which does everything \
       except `restart').
     DESC
-    task :symlink, :except => { :no_release => true } do
+    task :create_symlink, :except => { :no_release => true } do
       on_rollback do
         if previous_release
           run "rm -f #{current_path}; ln -s #{previous_release} #{current_path}; true"
@@ -245,6 +245,16 @@ Capistrano::Configuration.instance(:must_exist).load do
       run "rm -f #{current_path} && ln -s #{latest_release} #{current_path}"
     end
 
+    desc <<-DESC
+      Deprecated. Use `deploy:create_symlink` instead.
+    DESC
+    task :symlink, :except => { :no_release => true } do
+      warn "[Deprecation Warning] This API has changed, please use `deploy:create_symlink` instead of" \
+           " `deploy:symlink`."
+
+      create_symlink
+    end
+
     desc <<-DESC
       Copy files to the currently deployed version. This is useful for updating \
       files piecemeal, such as when you need to quickly deploy only a single \

metadata

@@ -1,69 +1,57 @@
---- !ruby/object:Gem::Specification 
+--- !ruby/object:Gem::Specification
 name: railsless-deploy
-version: !ruby/object:Gem::Version 
-  prerelease: false
-  segments: 
-  - 1
-  - 0
-  - 2
-  version: 1.0.2
+version: !ruby/object:Gem::Version
+  version: 1.1.0
+  prerelease: 
 platform: ruby
-authors: 
+authors:
 - Lee Hambley
 autorequire: 
 bindir: bin
 cert_chain: []
-
-date: 2010-04-22 00:00:00 +02:00
-default_executable: 
+date: 2012-09-21 00:00:00.000000000 Z
 dependencies: []
-
-description: Replacement for the rails deploy strategy which ships with Capistrano, allows you to deploy any platform with ease; some people have had huge success with this deploying rails projects where they needed to customise their deploy strategy beyond the code which ships with the Capistrano gem.
+description: Replacement for the rails deploy strategy which ships with Capistrano,
+  allows you to deploy any platform with ease; some people have had huge success with
+  this deploying rails projects where they needed to customise their deploy strategy
+  beyond the code which ships with the Capistrano gem.
 email: lee.hambley@gmail.com
 executables: []
-
 extensions: []
-
-extra_rdoc_files: 
+extra_rdoc_files:
 - LICENSE.markdown
 - README.markdown
-files: 
-- .gitignore
+files:
 - CHANGELOG.markdown
 - LICENSE.markdown
 - README.markdown
 - Rakefile
 - VERSION
 - lib/railsless-deploy.rb
-has_rdoc: true
 homepage: http://github.com/leehambley/railsless-deploy/
 licenses: []
-
 post_install_message: 
-rdoc_options: 
-- --charset=UTF-8
-require_paths: 
+rdoc_options: []
+require_paths:
 - lib
-required_ruby_version: !ruby/object:Gem::Requirement 
-  requirements: 
-  - - ">="
-    - !ruby/object:Gem::Version 
-      segments: 
-      - 0
-      version: "0"
-required_rubygems_version: !ruby/object:Gem::Requirement 
-  requirements: 
-  - - ">="
-    - !ruby/object:Gem::Version 
-      segments: 
-      - 0
-      version: "0"
+required_ruby_version: !ruby/object:Gem::Requirement
+  none: false
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
+required_rubygems_version: !ruby/object:Gem::Requirement
+  none: false
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
 requirements: []
-
 rubyforge_project: 
-rubygems_version: 1.3.6
+rubygems_version: 1.8.23
 signing_key: 
 specification_version: 3
-summary: Replacement for the default Capistrano tasks, designed to make life easier for PHP/Perl/Python developers
+summary: Replacement for the default Capistrano tasks, designed to make life easier
+  for PHP/Perl/Python developers
 test_files: []
-
+has_rdoc: 

data/.gitignore

@@ -1,3 +0,0 @@
-*.gem
-*.gemspec
-pkg/*