capwagen 0.0.3 → 0.0.4

data/README.md

@@ -1,17 +1,43 @@
 # Capwagen
 
-Capistrano integration for Kraftwagen projects. More information coming soon.
-For the more adventurous of you a very short tutorial below.
+[Capistrano](https://github.com/capistrano/capistrano) integration for
+[Kraftwagen](http://kraftwagen.org) based Drupal projects.
+
+This brings single command, secure (SSH), multi-target deployments to
+Drupal projects.  Capistrano is written in the [Ruby](http://ruby-lang.org)
+programming language, but it has proven itself in the realm of PHP with
+projects like [Capifony](http://capifony.org) (Capistrano for Symfony),
+[capistrano-drupal](https://github.com/previousnext/capistrano-drupal) and
+[WordPress Capistrano Deploy](https://github.com/nathanielks/Wordpress-Capistrano-Deploy).
+
+Since Capistrano is so widely used, it has clearly proven to be a reliable
+method of automating deployments.
+
+
+## Assumptions
+
+Capistrano is "opinionated software", it has very firm ideas about how
+things ought to be done, and is not very flexible in that regard.
+Some of the assumptions behind these opinions are:
+
+* You use SSH to access the remote servers (so *no* native FTP support).
+* You either have (1) the same password to all target machines, or (2)
+  public keys in place to allow passwordless access (preferred).
+
+If you cannot live with these assumptions, Capistrano is likely not
+the right tool for you.
 
-**This is very inmature code at the moment. DO NOT use it for production 
-deployments unless you do not care about breaking your production site.**
 
 ## Installation
 
+Simple, but assumes you have Ruby version 1.8.7+, and the
+[gems](http://rubygems.org) command available:
+
 ```
 gem install capwagen
 ```
 
+
 ## Adding Capwagen to your project
 
 ```
@@ -19,10 +45,13 @@ cd /path/to/project/src
 capwagen .
 ```
 
-Change `/path/to/project/src/cap/deploy.rb` to fit your configuration.
+Now change `./cap/deploy.rb` to fit your configuration.
+
 
 ## Running a deployment
 
+As easy as:
+
 ```
 cd /path/top/project/src
 cap deploy

data/lib/capwagen/version.rb

@@ -1,3 +1,3 @@
 module Capwagen
-  VERSION = "0.0.3"
+  VERSION = "0.0.4"
 end

data/lib/capwagen.rb

@@ -35,6 +35,14 @@ module Capwagen
           end
         end
 
+        task :install do
+          transaction do
+            update_code
+            create_symlink
+            find_and_execute_task("kraftwagen:install")
+          end
+        end
+
         # We override the default finalize update task, because our logic for 
         # filling projects with the correct symlinks, is completely different from
         # Rails projects.
@@ -89,6 +97,12 @@ module Capwagen
 
       # The Kraftwagen namespace contains the Kraftwagen update process
       namespace :kraftwagen do
+        task :install do
+          initialize_database
+          find_and_execute_task("drupal:cache_clear")
+          update
+        end
+
         task :update do
           apply_module_dependencies
           updatedb
@@ -99,6 +113,9 @@ module Capwagen
           find_and_execute_task("drupal:cache_clear")
         end
 
+        task :initialize_database do
+          run "cd #{latest_release} && #{drush_cmd} site-install #{install_profile} --yes"
+        end
         task :apply_module_dependencies do
           run "cd #{latest_release} && #{drush_cmd} kw-apply-module-dependencies #{kraftwagen_environment}"
         end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: capwagen
 version: !ruby/object:Gem::Version
-  version: 0.0.3
+  version: 0.0.4
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-03-06 00:00:00.000000000 Z
+date: 2013-03-19 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: capistrano