deployer 0.1.1 → 0.1.2

data/setup/deploy.rb

@@ -5,98 +5,83 @@
 #   http://github.com/meskyanichi/deployer 
 #
 #   Create Local and Remote Repository:
+#   This will create a git repository on the deployment server
+#   Will not work when using a remote location such as github.com, trunksapp.com
 #     git init
 #     cap deploy:repository:create
 # 
 #   Initial Deployment:
 #     git add .
-#     git commit -am "Initial commit for deployment"
-#     git push origin master
+#     git commit -m "Initial commit for deployment"
+#     git push origin [:branch]
 #     cap deploy:initial
 #     
 #   Then For Every Update Just Do:
 #     git add .
 #     git commit -am "some other commit"
-#     git push origin master
+#     git push origin [:branch]
 #     cap deploy
 #
-#   For Apache2 Users
-#     cap deploy:apache:create
-#     cap deploy:apache:destroy
-#     cap deploy:apache:restart
-#     cap deploy:apache:destroy_all
-#
-#   For NginX Users
-#     cap deploy:nginx:create
-#     cap deploy:nginx:destroy
-#     cap deploy:nginx:restart
-#     cap deploy:nginx:destroy_all
-#
 #   For a Full List of Commands
 #     cap -T
 
 
+##
 # Essential Configuration
 # Assumes Application and Git Repository are located on the same server
-set :ip,          "123.45.678.90" # the ip address that points to your production server
-set :user,        "root"          # the user that will connect to the production server
-set :remote,      "origin"        # the remote that should be deployed
-set :branch,      "master"        # the branch that should be deployed
-set :domain,      "example.com"   # (or   set :domain,    "subdomain.example.com"
-set :subdomain,   false           # and   set :subdomain, true)
+set :appname,   "example.com"     # the name of your application
+set :ip,        "123.45.678.90"   # the ip address of the production server
+set :user,      "deployer"        # the user that will deploy to the production server
+set :remote,    "origin"          # the remote that should be deployed
+set :branch,    "production"      # the branch that should be deployed
+
 
+##
 # Optional
-# If the Git Repository resides/should reside on a different server than where the application deploys,
-# then uncomment the following line and specify the repository_url/user
-# NOTE: The Tasks "cap deploy:repository:create/destroy/reset" won't work if you use this!
-# You will have to manually create the repository yourself on the specified server.
-#
-# set :repository_url,  "root@example.com:/path/to/repository.git"
+# If you want to use a repository from a different location (github.com, trunksapp.com, etc)
+# Then you can specify the URL here. When using this, the "cap deploy:repository" tasks won't work.
+# set :repository_url, "deployer@example.com:/path/to/repository.git"
 
 
+##
 # Set up additional shared folders
 set :additional_shared_folders,
-  %w(public/assets db)
+  %w(public/system db)
+
 
+##
 # Set up additional shared symlinks
 # These are mirrored to the Rails Applications' structure
-# public/assets         = RAILS_ROOT/public/assets          => SHARED_PATH/public/assets
+# public/system         = RAILS_ROOT/public/system          => SHARED_PATH/public/system
 # db/production.sqlite3 = RAILS_ROOT/db/production.sqlite3  => SHARED_PATH/db/production.sqlite3
 set :additional_shared_symlinks,
-  %w(public/assets db/production.sqlite3)
+  %w(public/system db/production.sqlite3)
 
 
+##
 # Additional Application Specific Tasks and Callbacks
-# In here you can specify which Application Specific tasks you would like to run right before the application
-# re-sets permissions and restarts passenger. You invoke the by simply calling "run_custom_task".
-#
+# In here you can specify which Application Specific tasks you would like to run right before
+# Passenger restarts the application. You invoke the by simply calling "run_custom_task"
+# For a list of all the available tasks that you could add to this "after_deploy" method, run: cap -T
 def after_deploy
-  run_custom_task "my_custom_task"
-  run_custom_task "nested:my_custom_task"
+  # run_custom_task "my_custom_task"
+  # run_custom_task "nested:my_custom_task"
 end
 
+##
 # Application Specific Deployment Tasks
 # In here you may specify any application specific and/or other tasks that are not handled by Deployer
+# These can be invoked by creating a "run_custom_task" method in the "after_deploy" method above
 namespace :deploy do  
-  desc "This is my custom task."
+  desc "Invoke this task manually by running: 'cap deploy:my_custom_task'"
   task :my_custom_task do
-    run "ls -la #{shared_path}"
+    # run "some command"
   end
   
   namespace :nested do
-    desc "This is my nested custom task."
+    desc "Invoke this task manually by running: 'cap deploy:nested:my_custom_task'"
     task :my_custom_task do
-      system "ls -la"
+      # system "some command"
     end
   end
-end
-
-
-# Default Configuration Apache/NginX
-# The settings below are default, you do not need to set these, unless you want to specify other parameters.
-# If you find that the settings below are fine, then you can leave them commented out or just remove them.
-# 
-# set :apache_initialize_utility_path,  '/etc/init.d/apache2'             # Only applies if running Apache and using the Apache Tasks
-# set :apache_sites_available_path,     '/etc/apache2/sites-available'    # Only applies if running Apache and using the Apache Tasks
-# set :nginx_initialize_utility_path,   '/etc/init.d/nginx'               # Only applies if running NginX and using the NginX Tasks
-# set :nginx_sites_enabled_path,        '/opt/nginx/conf/sites-enabled'   # Only applies if running NginX and using the NginX Tasks
+end

metadata

@@ -1,7 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: deployer
 version: !ruby/object:Gem::Version 
-  version: 0.1.1
+  hash: 31
+  prerelease: false
+  segments: 
+  - 0
+  - 1
+  - 2
+  version: 0.1.2
 platform: ruby
 authors: 
 - Michael van Rooijen
@@ -9,79 +15,98 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2010-01-12 00:00:00 +01:00
-default_executable: enhancify
+date: 2010-06-13 00:00:00 +02:00
+default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency 
   name: capistrano
-  type: :runtime
-  version_requirement: 
-  version_requirements: !ruby/object:Gem::Requirement 
+  prerelease: false
+  requirement: &id001 !ruby/object:Gem::Requirement 
+    none: false
     requirements: 
     - - ">="
       - !ruby/object:Gem::Version 
+        hash: 1
+        segments: 
+        - 2
+        - 5
+        - 13
         version: 2.5.13
-    version: 
-description: Deployer is a deployment engine (Ruby Gem) that enhances Capistrano with a set of useful automated deployment tasks. It favors convention over configuration, and it simplifies Rails Application Deployment with Capistrano.
+  type: :runtime
+  version_requirements: *id001
+- !ruby/object:Gem::Dependency 
+  name: OptionParser
+  prerelease: false
+  requirement: &id002 !ruby/object:Gem::Requirement 
+    none: false
+    requirements: 
+    - - ">="
+      - !ruby/object:Gem::Version 
+        hash: 9
+        segments: 
+        - 0
+        - 5
+        - 1
+        version: 0.5.1
+  type: :runtime
+  version_requirements: *id002
+description: Deployer is gem that enhances Capistrano to simplify the deployment of Ruby on Rails applications.
 email: meskyanichi@gmail.com
 executables: 
 - enhancify
 extensions: []
 
-extra_rdoc_files: 
-- LICENSE
-- README.textile
+extra_rdoc_files: []
+
 files: 
-- .document
-- .gitignore
-- LICENSE
-- README.textile
-- Rakefile
-- VERSION
 - bin/enhancify
-- deployer.gemspec
-- lib/deployer.rb
 - lib/deployer/helpers.rb
 - lib/deployer/initializer.rb
-- lib/deployer/tasks/deployer.rake
-- lib/tasks/apache.rb
+- lib/deployer.rb
 - lib/tasks/commands.rb
 - lib/tasks/db.rb
 - lib/tasks/environment.rb
 - lib/tasks/gems.rb
 - lib/tasks/global.rb
-- lib/tasks/nginx.rb
 - lib/tasks/passenger.rb
 - lib/tasks/plugin.rb
 - lib/tasks/repository.rb
 - setup/deploy.rb
+- README.md
+- LICENSE
 has_rdoc: true
-homepage: 
+homepage: http://github.com/meskyanichi/deployer
 licenses: []
 
 post_install_message: 
-rdoc_options: 
-- --charset=UTF-8
+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"
-  version: 
 required_rubygems_version: !ruby/object:Gem::Requirement 
+  none: false
   requirements: 
   - - ">="
     - !ruby/object:Gem::Version 
+      hash: 3
+      segments: 
+      - 0
       version: "0"
-  version: 
 requirements: []
 
 rubyforge_project: 
-rubygems_version: 1.3.5
+rubygems_version: 1.3.7
 signing_key: 
 specification_version: 3
-summary: Deployer is a deployment engine (Ruby Gem) that enhances Capistrano with a set of useful automated deployment tasks. It favors convention over configuration, and it simplifies Rails Application Deployment with Capistrano.
+summary: Deployer is gem that enhances Capistrano to simplify the deployment of Ruby on Rails applications.
 test_files: []
 

data/.document

@@ -1,4 +0,0 @@
-README.textile
-lib/**/*.rb
-bin/*
-LICENSE

data/.gitignore

@@ -1,21 +0,0 @@
-## MAC OS
-.DS_Store
-
-## TEXTMATE
-*.tmproj
-tmtags
-
-## EMACS
-*~
-\#*
-.\#*
-
-## VIM
-*.swp
-
-## PROJECT::GENERAL
-coverage
-rdoc
-pkg
-
-## PROJECT::SPECIFIC

data/README.textile

@@ -1,290 +0,0 @@
-h1. Deployer
-
-p. Deployer is a deployment engine (Ruby Gem) that enhances Capistrano with a set of useful automated deployment tasks and a base structure. It favors convention over configuration, and it simplifies Rails Application Deployment with Capistrano.
-
-p. It assumes you are using Passenger to serve your Rails applications.
-
-h2. Why?
-
-p. I wanted a tool that'd enhance Capistrano's default setup, and I wanted it to cause me a minimal amount of hassle and time consumption to set up as well for every time I want to deploy a new application.
-
-
-h2. Getting Started
-
-p. install the gem
-
-bc. sudo gem install deployer
-
-p. create a new Rails app
-
-bc. rails my_application
-
-p. move into the Rails app and execute the "capify" and "enhancify" commands
-
-bc. cd my_application
-capify .
-enhancify .
-
-p. enhancify is a command, provided by deployer that will inject some code into the Capfile and replace the config/deploy.rb with the one used for *Deployer*.
-If the deploy.rb file already exists, it will simply rename it to "deploy.old.1.rb", and if that also exists it will rename it to deploy.old.2.rb, etc. etc. So you will never accidentally overwrite your initial deploy.rb file.
-
-p. This is what the deploy.rb looks like: "config/deploy.rb":http://github.com/meskyanichi/deployer/blob/master/setup/deploy.rb
-
-p. *Next, open the config/deploy.rb file and edit the following variables.*
-
-bc. set :ip,          "123.45.678.90" # the ip address that points to your production server
-set :user,        "root"          # the user that will connect to the production server
-set :remote,      "origin"        # the remote that should be deployed
-set :branch,      "master"        # the branch that should be deployed
-set :domain,      "example.com"   # (or   set :domain,    "subdomain.example.com"
-set :subdomain,   false           # and   set :subdomain, true)
-
-p. For the sake of *testing*, be sure to *NOT* test this out on your main domain, unless you don't have an application running there that is. In the above example you can see how you set this up for a subdomain for your application to deploy a sample Rails Application to try out *Deployer*.
-
-bc. set :domain, "test.mydomain.com"
-set :subdomain, true
-
-p. _This is what you must do if you wish to try it out on a subdomain. In this case: test.mydomain.com_
-
-p. And *that's it!* You are now ready to do the following through *Deployer*:
-
-* Create a remote git repository
-* Push your initial commit to the remote repository
-* Create the production environment to where you will deploy your application to
-* Let *Deployer* create a simple Apache2 or NginX virtual-host file, transfer it to your remote server and restart the web-server
-* And, of course, deploy and run your Rails application!
-
-p. Here is are the quick-reference comments of the config/deploy.rb file
-
-bc. # Quick Reference
-# Configure the essential configurations below and do the following:
-# 
-#   Create Local and Remote Repository:
-#     git init
-#     cap deploy:repository:create
-# 
-#   Initial Deployment:
-#     git add .
-#     git commit -am "Initial commit for deployment"
-#     git push origin master
-#     cap deploy:initial
-#     
-#   Then For Every Update Just Do:
-#     git add .
-#     git commit -am "some other commit"
-#     git push origin master
-#     cap deploy
-#
-#   For Apache2 Users
-#     cap deploy:apache:create
-#     cap deploy:apache:destroy
-#     cap deploy:apache:restart
-#     cap deploy:apache:destroy_all
-#
-#   For NginX Users
-#     cap deploy:nginx:create
-#     cap deploy:nginx:destroy
-#     cap deploy:nginx:restart
-#     cap deploy:nginx:destroy_all
-#
-#   For a Full List of Commands
-#     cap -T
-
-p. *NOTE*
-
-p. The Apache2 and NginX tasks are totally OPTIONAL. Before you use these, please scroll down this page and see what it's all about. It essentially parses an initial *apache* or *nginx* virtual host file. Once parsed, it will transfer this inside the sites-available / sites-enabled folders. Afterwards *Apache* or *Nginx* will automatically get restarted. So basically you COULD deploy a web application without ever manually *SSH*'ing into the production box. I use this, but again, please read more about this before attempting it just so you know whats going on if it doesn't work for you. It depends on various things. It's optional so you don't have to use these methods since we're talking about *deployment* and not *server management*, it's just a simple little extra that *Deployer* provides, nothing really fancy.
-
-p. There are more tasks, but these will be your main commands. It's pretty straightforward.
-
-p. To list all commands:
-
-bc. cap -T
-
-
-h3. Automated Tasks
-
-p. *Deployer* will invoke various built-in tasks to try and deploy your application successfully.
-
-p. On the initial deployment *cap deploy:initial*. This procedure only has to be performed once.
-
-* It will setup the production environment, releases and shared folder
-* It will populate the shared folder with the folders you specified in the deploy.rb file
-* It will sync your applications *database.yml* file to the shared/db folder
-* It will sync the *deployer.rake* task from the to the shared/lib/tasks folder
-* It will deploy your application
-
-p. And the deployment procedure that follows (*cap deploy*), does the following:
-
-* It will create a new folder in the releases folder and deploy your application to it
-* It will ensure that the shared folder has all the folders you specified in the *deploy.rb*
-* It will setup built-in symlink setups for your database.yml, production log and deployer.rake
-* It will also setup any additional symlinks you may have specified inside the *deploy.rb* from the release folder to the shared folder
-* It will ensure all gems that are specified inside the *config/environment.rb* are installed. Will attempt to ignore exceptions
-* It will ensure the database is present and migrated to the latest version
-* It will then perform any *custom* tasks you might have specified inside the *deploy.rb* file within the *after_deploy* method definition
-* It will then set the correct passenger permissions
-* It will then restart passenger
-
-p. The *cap deploy:initial* will call *cap deploy* at the end. So an initial version will be released. After that, just do the following to released a new version as you normally would:
-
-bc. git add .
-git commit -am "next version commit"
-git push origin master
-cap deploy
-
-
-h2. Additional Configuration
-
-*Shared Folders and Symlinks*
-
-p. I wanted to keep this as simple as possible as well. By default, *Deployer* will create folders for storing the production.log in and other necessary stuff.
-It will properly symlink it from the shared folder to the Rails application. However! You will most likely have some other things you must keep in a shared folder, such as assets
-or other files. This can be done easily with *Deployer*.
-
-p. Again, inside of config/deploy.rb
-
-bc. set :additional_shared_folders,
-  %w(public/assets db)
-
-p. In this example two paths will be created.
-
-* /var/rails/:domain/shared/public/assets
-* /var/rails/:domain/shared/db
-
-p. *Deployer* will ensure these are available after every deployment. And will append any folders if you change the values here and re-deploy.
-
-p. Now, what use are these folders if you do not have the ability to add symlinks from these folders to the application.
-
-bc. set :additional_shared_symlinks,
-  %w(public/assets db/production.sqlite3)
-  
-p. In this example two symlinks will be created from the shared_path to the current Rails application release.
-As you can see the first symlink is a "path" symlink, which does not point to a direct file, but rather a folder.
-
-p. The second symlink will be a link from the shared/db/production.sqlite3 to the current rails applications' db/production.sqlite3 file.
-
-*NOTE*
-
-p. One important thing to note here is that notice how the symlinks are mirrored to the Rails applications folder structure. This will always be the case. If you have some crazy architecture inside your Rails application: *rails_root/my/awesome/folder/structure/is/very/long* then you MUST create the following folder structure for the shared path: *shared/my/awesome/folder/structure/is/very/long*. This is a convention and it saves a lot of overhead in your configuration file by just defining a path once and using that same path for both the current and shared path.
-
-p. *Additional (Optional) (Server) Configuration*
-
-p. Here you can specify that you want to pull/push from/to a git repository that's located on a DIFFERENT server. Leave this commented out or remove it if your git repository resides on the same server as your Rails application. If you choose to store your git repository on a separate server by uncommenting the following line, then you lose the ability to create/reset/destroy/reinitialize it through *Deployer*. This is no big deal though. All you have to do is create the git repository manually on that specific server and then issue the *git remote add origin repository_url* and it will work fine with the rest of *Deployer*.
-
-bc. set :repository_url,  "root@example.com:/path/to/repository.git"
-
-p. And then here is the last bit of server configuration you can specify.
-
-bc. # Default Configuration (Git/Repository Apache/NginX)
-# The settings below are default, you do not need to set these, unless you want to specify other parameters.
-# If you find that the settings below are fine, then you can leave them commented out or just remove them.
-# 
-# set :apache_initialize_utility_path,  '/etc/init.d/apache2'             # Only applies if running Apache and using the Apache Tasks
-# set :apache_sites_available_path,     '/etc/apache2/sites-available'    # Only applies if running Apache and using the Apache Tasks
-# set :nginx_initialize_utility_path,   '/etc/init.d/nginx'               # Only applies if running NginX and using the NginX Tasks
-# set :nginx_sites_enabled_path,        '/opt/nginx/conf/sites-enabled'   # Only applies if running NginX and using the NginX Tasks
-
-p. Again, very straightforward. I even added comments. One thing to note here is that these are commented out by default and you don't have to "uncomment" them to get the defaults. If you like the default settings you can leave it commented out, or just remove the lines. Or of course, uncomment them and leave them unchanged. Whatever you want.
-
-
-h3. *Adding Application Specific Deployment Tasks*
-
-p. Inside the *namespace :deploy do* block you can define your own deployment tasks that are specific to your application.
-
-bc.. # Application Specific Deployment Tasks
-namespace :deploy do
-  
-  desc "This is my custom task."
-  task :my_custom_task do
-    run "ls #{shared_path}"
-  end
-  
-  namespace :nested do
-    desc "This is my nested custom task."
-    task :my_custom_task do
-      puts "ls #{shared_path}"
-    end
-  end
-
-end
-
-
-
-p. Again, very straightforward. Just define your tasks as you normally would with Capistrano.
-Then, to invoke them during each deployment you must add them inside the *after_deploy*, method like so:
-
-bc. def after_deploy
-  run_custom_task "my_custom_task"
-  run_custom_task "nested:my_custom_task"
-end
-
-p. This method will be invoked right before *Deployer* sets permissions on, and restarts the your Rails application. 
-
-
-h3. Built-in Additional Tasks
-
-p. *Deployer* has some built-in tasks that are often used by developers.
-
-p. *Whenever*, To update the crontab on deployment:
-
-bc. def after_deploy
-  run_custom_task "whenever:update_crontab"
-end
-
-p. *Delayed Job*, To start/stop daemons
-
-bc. def after_deploy
-  run_custom_task "delayed_job:start"
-  run_custom_task "delayed_job:start n=3" # "n" specifies the amount of daemons that should run
-  run_custom_task "delayed_job:stop"
-end
-
-
-h2. Assumptions / Conventions
-
-p. Deployer favors Convention of Configuration. There are a few things you need to be aware of before you start using it. Just so it doesn't confuse you.
-
-p. By filling in the 4 variables (ip, domain, subdomain, user) you are practically set to create a remote git repository, push your local repository to it, create your production environment, deploy to your production environment from your remote repository and even let *Deployer* parse the simple apache2 and nginx configuration vhost files and transfer them to the server. Of course, you can also just choose to do setup your virtual hosts manually, it is totally optional. The availability of this option depends on your OS architecture/webserver installation path.
-
-p. Now, just to clear some things up with some facts about the conventions:
-
-*Rails Application Deployment Path*
-
-bc. /var/rails/:domain
-
-*Git Repository Path* unless specified otherwise in the configuration file.
-
-bc. /var/git/:domain.git
-
-*If using the Apache2 create/destroy/restart/destroy_all features, Apache2's sites-available path must be the following*, unless specified otherwise in the configuration file.
-
-bc. /etc/apache2/sites-available/
-
-*If using the NginX create/destroy/restart/destroy_all features, NginX's sites-enabled path must be the following*, unless specified otherwise in the configuration file.
-
-bc. /opt/nginx/conf/sites-enabled/
-
-p. Additionally, you must be able to start/stop the NginX webserver through these commands: "/etc/init.d/nginx start" and "/etc/init.d/nginx stop"
-If you don't have this functionality, but want it, check out: "http://github.com/meskyanichi/rails-nginx-passenger-ubuntu":http://github.com/meskyanichi/rails-nginx-passenger-ubuntu
-For NginX you must also add this: *include sites-enabled/** inside the nginx configuration file, inside the *server{}* block to include all settings that *Deployer* transfers into the sites-enabled
-
-* Assumes you are using Phusion Passenger for deployment
-* Assumes Git Repository will be located on the same server as where the actual application will be deployed. Unless specified otherwise in the configuration file.
-* The config/database.yml will be transferred to the shared/config/database.yml and symlinked to on the initial deployment. You can re-sync it later with *cap deploy:db:sync_yaml*.
-* I have overwritten/adjusted the "rake gems:install" command in production mode to try and force a successful gem installation process.
-There are occasions where there are unexpected exceptions raised when trying to issue the rake task. For example when you have an "Uninitialized Constant" inside the environment.rb which "is" initialized in development mode because you have the gem installed locally, but fails in the production environment because it does not have the gem. *Deployer* shall try to install any gem specified inside the config/environment.rb regardless of what exception is being raised to ensure all gem dependencies are installed on deployment.
-
-
-*NOTE*
-
-p. This is a _very early_ release. A lot may be subject to change, for the good!
-
-
-h2. Suggestions, Requests, Idea's?
-
-Tell, Ask, Fork and Help!
-
-
-h2. Copyright
-
-Copyright (c) 2010 Michael van Rooijen. See LICENSE for details.

data/Rakefile

@@ -1,52 +0,0 @@
-require 'rubygems'
-require 'rake'
-
-begin
-  require 'jeweler'
-  Jeweler::Tasks.new do |gem|
-    gem.name = "deployer"
-    gem.summary = %Q{Deployer is a deployment engine (Ruby Gem) that enhances Capistrano with a set of useful automated deployment tasks. It favors convention over configuration, and it simplifies Rails Application Deployment with Capistrano.}
-    gem.description = %Q{Deployer is a deployment engine (Ruby Gem) that enhances Capistrano with a set of useful automated deployment tasks. It favors convention over configuration, and it simplifies Rails Application Deployment with Capistrano.}
-    gem.email = "meskyanichi@gmail.com"
-    #gem.homepage = "http://github.com/meskyanichi/deployer"
-    gem.authors = ["Michael van Rooijen"]
-    gem.add_dependency "capistrano", ">= 2.5.13"
-  end
-  Jeweler::GemcutterTasks.new
-rescue LoadError
-  puts "Jeweler (or a dependency) not available. Install it with: gem install jeweler"
-end
-
-require 'rake/testtask'
-Rake::TestTask.new(:test) do |test|
-  test.libs << 'lib' << 'test'
-  test.pattern = 'test/**/test_*.rb'
-  test.verbose = true
-end
-
-begin
-  require 'rcov/rcovtask'
-  Rcov::RcovTask.new do |test|
-    test.libs << 'test'
-    test.pattern = 'test/**/test_*.rb'
-    test.verbose = true
-  end
-rescue LoadError
-  task :rcov do
-    abort "RCov is not available. In order to run rcov, you must: sudo gem install spicycode-rcov"
-  end
-end
-
-task :test => :check_dependencies
-
-task :default => :test
-
-require 'rake/rdoctask'
-Rake::RDocTask.new do |rdoc|
-  version = File.exist?('VERSION') ? File.read('VERSION') : ""
-
-  rdoc.rdoc_dir = 'rdoc'
-  rdoc.title = "deployer #{version}"
-  rdoc.rdoc_files.include('README*')
-  rdoc.rdoc_files.include('lib/**/*.rb')
-end

data/VERSION

@@ -1 +0,0 @@
-0.1.1