bricks-deploy 0.6.10 → 0.6.11

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 65885ccb6f1af101a7b039f80ef7abf89658034c
-  data.tar.gz: 872f0193dd18091f6268e10f5c7244ef3a3fa444
+  metadata.gz: d16dc7ba979ba4778e926a7dfc5f2eb4ca4c5e78
+  data.tar.gz: c39befb72cb7c65f72ec4e9655a1bd37fcea8761
 SHA512:
-  metadata.gz: f40a40cd193b0329f9019a09628bde3555a2f516fb0e38c6ba8059a26a0b95dde787ae803909f3df4fc24ffae0e6f34bd39eac483ce30106fa70cceabd84a543
-  data.tar.gz: 39e3198fc93b49fc511383df183536f9e2209cc4d9219e3a9ddfc607552fa95d27de9e989e13601c8801398fe99c5cd8753e3cd8dcce699e2259b457821a177d
+  metadata.gz: 371c5226c66542cd48db28360f83af4ca5a04e4b7d2f5f7aa66deb0580647d4ce6794b4c839b01a3303da583b2041b6f0e08e1581dabe759654cbde5efb7888e
+  data.tar.gz: 9cab34f2d6d20c9bf2527d388c78cb0e20ce9271e6b19b459c79c688c8ec0a40221559d12f4fc040e9d632db22878615c85c0e97a0ef829e75870c959e9a7e4a

data/README.markdown

@@ -38,11 +38,12 @@ Initial setup
 2.  Run the setup task:
 
     ```sh
-    git deploy setup -r "production"
+    git deploy setup -r "production" --stage "live" --color "twentysteps"
     ```
 
     This will initialize the remote git repository in the deploy directory
-    (`/apps/mynewapp` in the above example) and install the remote git hook.
+    (`/apps/mynewapp` in the above example), install the remote git hook and
+    output the string "live" in app/config/stage and "twentysteps" in app/config/color.
 
 3.  Run the init task:
 
@@ -50,9 +51,7 @@ Initial setup
     git deploy init
     ```
 
-    This generates default deploy callback scripts in the `deploy/` directory.
-    You should check them in git because they are going to be executed on the
-    server during each deploy.
+    This generates default deploy callback scripts in the `bin/deploy/remote/` directory - edit the callback scripts according to your needs (cp. below)
 
 4.  Push the code.
 
@@ -60,10 +59,6 @@ Initial setup
     git push production master
     ```
 
-3.  Login to your server and manually perform necessary one-time administrative operations. This might include:
-    * set up the Apache/nginx virtual host for this application;
-    * check your `config/database.yml` and create the production database.
-
 
 Everyday deployments
 --------------------
@@ -82,15 +77,12 @@ install the "bricks-deploy" gem.
 On every deploy, the default `deploy/after_push` script performs the following:
 
 1. updates git submodules (if there are any);
-2. runs `bundle install --deployment` if there is a Gemfile;
-3. runs `rake db:migrate` if new migrations have been added;
-4. clears cached CSS/JS assets in "public/stylesheets" and "public/javascripts";
 5. restarts the web application.
 
-You can customize all this by editing generated scripts in the `deploy/`
+You can customize all this by editing generated scripts in the `app/config/remote/`
 directory of your app.
 
-Deployments are logged to `log/deploy.log` in your application's directory.
+Deployments are logged to `var/logs/deploy.log` in your application's directory.
 
 
 How it works
@@ -101,12 +93,12 @@ repository. This is how your code on the server is kept up to date. This script
 checks out the latest version of your project from the current branch and
 runs the following callback scripts:
 
-* `deploy/setup` - on first push.
-* `deploy/after_push` - on subsequent pushes. It in turn executes:
+* `bin/deploy/remote/setup` - on first push.
+* `bin/deploy/remote/after_push` - on subsequent pushes. It in turn executes:
   * `deploy/before_restart`
   * `deploy/restart`
   * `deploy/after_restart`
-* `deploy/rollback` - executed for `git deploy rollback`.
+* `bin/deploy/remote/rollback` - executed for `git deploy rollback`.
 
 All of the callbacks are optional. These scripts are ordinary Unix executables.
 The ones which get generated for you by `git deploy init` are written in shell
@@ -130,5 +122,4 @@ Extra commands
 * `git deploy upload <files>` - Copy local files to the remote app
 
 
-
-  [heroku]: http://heroku.com/
+  [Heroku]: http://heroku.com/

data/lib/bricks_deploy/generator.rb

@@ -19,6 +19,7 @@ class BricksDeploy::Generator < Thor::Group
     copy_hook 'before_restart.sh', 'bin/deploy/remote/before_restart'
     copy_hook 'after_restart.sh', 'bin/deploy/remote/after_restart'
     copy_hook 'setup.sh', 'bin/deploy/remote/setup'
+    copy_hook 'rollback.sh', 'bin/deploy/remote/rollback'
   end
 
   private

data/lib/bricks_deploy/templates/after_push.sh

@@ -1,4 +1,5 @@
 #!/usr/bin/env bash
+
 set -e
 oldrev=$1
 newrev=$2

data/lib/bricks_deploy/templates/after_restart.sh

@@ -1,3 +1,3 @@
 #!/usr/bin/env bash
 
-echo "After restart of Bricks app ...\n"
+echo "After restart of Bricks app ..."

data/lib/bricks_deploy/templates/before_restart.sh

@@ -1,3 +1,3 @@
-#!/usr/bin/env ruby
+#!/usr/bin/env bash
 
-echo "Before restart of Bricks app ...\n"
+echo "Before restart of Bricks app ..."

data/lib/bricks_deploy/templates/restart.sh

@@ -1,3 +1,4 @@
-#!/bin/sh
+#!/usr/bin/env bash
+
 touch var/tmp/restart.txt
-echo "Restarting Bricks app... \n"
+echo "Restarting Bricks app ..."

data/lib/bricks_deploy/templates/rollback.sh

@@ -0,0 +1,3 @@
+#!/usr/bin/env bash
+
+echo "Rolling back Bricks app ..."

data/lib/bricks_deploy/templates/setup.sh

@@ -1,3 +1,3 @@
-#!/bin/sh
+#!/usr/bin/env bash
 
-echo "Setting up Bricks app ... \n"
+echo "Setting up Bricks app ..."

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: bricks-deploy
 version: !ruby/object:Gem::Version
-  version: 0.6.10
+  version: 0.6.11
 platform: ruby
 authors:
 - Mislav Marohnić
@@ -72,6 +72,7 @@ files:
 - lib/bricks_deploy/templates/after_restart.sh
 - lib/bricks_deploy/templates/before_restart.sh
 - lib/bricks_deploy/templates/restart.sh
+- lib/bricks_deploy/templates/rollback.sh
 - lib/bricks_deploy/templates/setup.sh
 - lib/hooks/post-receive.sh
 - spec/configuration_spec.rb