capistrano-postgresql 2.0.0 → 3.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 86fb4bf23488e11c1621ea0220f0f9de556bd54b
-  data.tar.gz: fb80400a70f99e7235f18e154ebe413903716f97
+  metadata.gz: f2168ffbd411cc717cc481467336c5ddf60f6b14
+  data.tar.gz: 111fc809e5d5378dd771d9a873732ba2f45e607c
 SHA512:
-  metadata.gz: 2a26868b035dc682b3a9a73c332b0837c91f8ef5738d580a20e13df409204005a9bb5ff3b347ad05183b3abeebc1128f43149bd26541bfd129aa212975956829
-  data.tar.gz: a109426f8a310440d3827c5938883e9688f2dcb9a15e10ced05ea690ad52b0a7d099aa2615b9df3a13b8f870dde89d936c68d26ba4e389727a3b59db5d3e14e9
+  metadata.gz: 27eaa6cd688543c31c9699bf2e24bb4915c431044ae4f6123248e5fdad8e2ba5acbe8286a079b727cf9509bf2c153bac55cc0dc13c92b9495599fadcc729ea42
+  data.tar.gz: 17f848b96ef6747e7a68001d8b8b1cbe5fcb67e1c6df233a527622485b8e37d73038fccc7dddbdbc4367371ba43b8496d783fcee7bf001614865afed4f8acacc

data/CHANGELOG.md

@@ -1,3 +1,5 @@
+### v3.0.0, 2014-04-11
+- all the work is moved to the `setup` task
 ### v2.0.0, 2014-03-30
 - shorten variable names: postgresql -> pg
 - better helpers module separation

data/README.md

@@ -25,7 +25,7 @@ Put the following in your application's `Gemfile`:
 
     group :development do
       gem 'capistrano', '~> 3.1'
-      gem 'capistrano-postgresql'
+      gem 'capistrano-postgresql', '~> 3.0'
     end
 
 Then:
@@ -39,9 +39,15 @@ the following in `Capfile` file:
 
     require 'capistrano/postgresql'
 
-And deploy:
+Make sure the `deploy_to` path exists and has the right privileges on the
+server (i.e. `/var/www/myapp`).<br/>
+Or just install
+[capistrano-safe-deploy-to](https://github.com/bruno-/capistrano-safe-deploy-to)
+plugin and don't think about it.
 
-    $ bundle exec cap production deploy
+To setup the server, run:
+
+    $ bundle exec cap production setup
 
 Easy, right?
 
@@ -52,7 +58,7 @@ Check below to see what happens in the background.
 Check here for the full capistrano deployment flow
 [http://capistranorb.com/documentation/getting-started/flow/](http://capistranorb.com/documentation/getting-started/flow/).
 
-The following tasks run automatically after `deploy:started` task:
+The following tasks run during the `setup` task:
 
 * `postgresql:create_db_user`<br/>
 creates a postgresql user. Password for the user is automatically generated and

data/lib/capistrano/postgresql/version.rb

@@ -1,5 +1,5 @@
 module Capistrano
   module Postgresql
-    VERSION = "2.0.0"
+    VERSION = "3.0.0"
   end
 end

data/lib/capistrano/tasks/postgresql.rake

@@ -70,9 +70,12 @@ namespace :postgresql do
     set :linked_files, fetch(:linked_files, []).push('config/database.yml')
   end
 
-  after 'deploy:started', 'postgresql:create_db_user'
-  after 'deploy:started', 'postgresql:create_database'
-  after 'deploy:started', 'postgresql:generate_database_yml'
   after 'deploy:started', 'postgresql:database_yml_symlink'
+end
 
+desc 'Server setup tasks'
+task :setup do
+  invoke 'postgresql:create_db_user'
+  invoke 'postgresql:create_database'
+  invoke 'postgresql:generate_database_yml'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: capistrano-postgresql
 version: !ruby/object:Gem::Version
-  version: 2.0.0
+  version: 3.0.0
 platform: ruby
 authors:
 - Bruno Sutic
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-03-30 00:00:00.000000000 Z
+date: 2014-04-11 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: capistrano