capistrano-windows-server 0.2.1 → 0.2.2

data/README.md

@@ -88,7 +88,7 @@ Setting up capistrano for your Rails project
 
     config.gem "capistrano-windows-server", :lib => "capistrano"
 
-Set up capistrano as you normally would.
+Set up capistrano as you normally would with `capify`.
 The [capistrano wiki](https://github.com/capistrano/capistrano/wiki/2.x-From-The-Beginning) and 
 [capistrano handbook](https://github.com/leehambley/capistrano-handbook/blob/master/index.markdown) are helpful.
 
@@ -161,7 +161,7 @@ In addition to creating the directory structure, it clones your project into #{d
     cap deploy:setup
 
 After `cap deploy:setup` runs successfully, it's time to set up the Rails application.
-Create or copy in config/database.yml, set up the database server, install gems, and anything else you need to do to make the app run.
+Create or copy in **config/database.yml**, set up the **database**, **install gems**, and anything else you need to do to make the app run.
 Testing to make sure the app will start with `rails script/server -e production` is a good idea.
 
 Once it's ready, you can deploy your app for the first time:

data/VERSION

@@ -1 +1 @@
-0.2.1
+0.2.2

data/capistrano-windows-server.gemspec

@@ -5,11 +5,11 @@
 
 Gem::Specification.new do |s|
   s.name = %q{capistrano-windows-server}
-  s.version = "0.2.1"
+  s.version = "0.2.2"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["Edward Anderson"]
-  s.date = %q{2011-07-22}
+  s.date = %q{2011-08-01}
   s.description = %q{This gem modifies capistrano recipes to allow deploys to windows machines.
 Several nuances such as the lack of symlinks make the deploy a little different, but it's better than doing it by hand.
 See the github page for instruction on how to set up Windows to get it ready for a deploy.}

data/lib/capistrano/ext/windows_server.rb

@@ -1,3 +1,4 @@
+# Capistrano 1 and 2 have different configuration locations
 configuration = Capistrano::Configuration.respond_to?(:instance) ?
   Capistrano::Configuration.instance(:must_exist) :
   Capistrano.configuration(:must_exist)
@@ -106,6 +107,7 @@ configuration.load do
       desc "Create mongrel services"
       task :setup do
         mongrel_instances.each do |n|
+          run "mkdir -p #{current_path}/{tmp,log}" # These are often not under version control, but their absence keeps mongrel from recognizing the rails app
           run "cd #{current_path} && #{mongrel_cmd} service::install -e #{rails_env} -N #{mongrel_instance_prefix}#{n} -p #{base_port + n - mongrel_instances.first}"
           run %Q(sc.exe config "#{mongrel_instance_prefix}#{n}" start= auto)
         end

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: capistrano-windows-server
 version: !ruby/object:Gem::Version 
-  hash: 21
+  hash: 19
   prerelease: 
   segments: 
   - 0
   - 2
-  - 1
-  version: 0.2.1
+  - 2
+  version: 0.2.2
 platform: ruby
 authors: 
 - Edward Anderson
@@ -15,13 +15,13 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2011-07-22 00:00:00 -04:00
+date: 2011-08-01 00:00:00 -04:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency 
-  prerelease: false
-  name: capistrano
   type: :runtime
+  name: capistrano
+  prerelease: false
   version_requirements: &id001 !ruby/object:Gem::Requirement 
     none: false
     requirements: 
@@ -33,9 +33,9 @@ dependencies:
         version: "0"
   requirement: *id001
 - !ruby/object:Gem::Dependency 
-  prerelease: false
-  name: jeweler
   type: :development
+  name: jeweler
+  prerelease: false
   version_requirements: &id002 !ruby/object:Gem::Requirement 
     none: false
     requirements: