git-deploy 0.5.4 → 0.5.5

data/README.markdown

@@ -1,17 +1,20 @@
 Easy git deployment
 ===================
 
-Straightforward, [Heroku][]-style, push-based deployment. Your deploys will look like this:
+Straightforward, [Heroku][]-style, push-based deployment. Your deploys can become as simple as this:
 
     $ git push production master
 
 To get started, install the "git-deploy" gem.
 
-    $ gem install git-deploy
+    gem install git-deploy
 
+Only the person who is setting up deployment for the first time needs to install
+the gem. You don't have to add it to your project's Gemfile.
 
-What application frameworks/languages are supported?
-----------------------------------------------------
+
+Which app languages/frameworks are supported?
+---------------------------------------------
 
 Regardless of the fact that this tool is mostly written in Ruby, git-deploy can be useful for any kind of code that needs deploying on a remote server. The default scripts are suited for Ruby web apps, but can be edited to accommodate other frameworks.
 
@@ -20,50 +23,63 @@ Your deployment is customized with per-project callback scripts which can be wri
 The assumption is that you're deploying to a single host to which you connect over SSH using public/private key authentication.
 
 
-Setup steps
------------
+Initial setup
+-------------
 
 1.  Create a git remote for where you'll push the code on your server. The name of this remote in the examples is "production", but it can be whatever you wish ("online", "website", or other).
-    
-        $ git remote add production user@example.com:/path/to/myapp
-    
-    The "/path/to/myapp" is the directory where your code will reside. It doesn't have to exist; it will be created for you during this setup.
+
+    ```sh
+    git remote add production "user@example.com:/apps/mynewapp"
+    ```
+
+    `/apps/mynewapp` is the directory where you want your code to reside on the
+    remote server. If the directory doesn't exist, the next step creates it.
 
 2.  Run the setup task:
-    
-        $ git deploy setup -r production
-    
-    This will initialize the remote git repository in the target directory ("/path/to/myapp" in the above example) and install the remote git hooks.
+
+    ```sh
+    git deploy setup -r "production"
+    ```
+
+    This will initialize the remote git repository in the deploy directory
+    (`/apps/mynewapp` in the above example) and install the remote git hook.
 
 3.  Run the init task:
-    
-        $ git deploy init
-    
-    This generates default deploy callback scripts in the "deploy/" directory. You must check them in version control. They are going to be executed on the server on each deploy.
+
+    ```sh
+    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.
 
 4.  Push the code.
 
-        $ git push production master
+    ```sh
+    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.
-
+    * check your `config/database.yml` and create the production database.
 
-Deployment
-----------
 
-If you've set your app correctly, visiting "http://example.com" in your browser should show it up and running.
+Everyday deployments
+--------------------
 
-Now, subsequent deployments are done simply by pushing to the branch that is currently checked out on the remote:
+If you've set your app correctly, visiting <http://example.com> in your browser
+should show it up and running.
 
-    $ git push production master
+Now, subsequent deployments are done simply **by pushing to the branch that is
+currently checked out on the remote**:
 
-Because the deployments are done with git, not everyone on the team had to install git-deploy. Just the person who was doing the setup.
+    git push production master
 
-Deployments are logged to "log/deploy.log" in your application.
+Because the deployments are performed with git, nobody else on the team needs to
+install the "git-deploy" gem.
 
-On every deploy, the "deploy/after_push" script performs the following:
+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;
@@ -71,16 +87,30 @@ On every deploy, the "deploy/after_push" script performs the following:
 4. clears cached CSS/JS assets in "public/stylesheets" and "public/javascripts";
 5. restarts the web application.
 
-You can customize all of this by editing scripts in the "deploy/" directory of your app.
+You can customize all this by editing generated scripts in the `deploy/`
+directory of your app.
+
+Deployments are logged to `log/deploy.log` in your application's directory.
+
 
 How it works
 ------------
 
-The "setup" task installed a "post-receive" hook in the remote git repository. This is how your working copy on the server is kept up to date. This hook, after checking out latest code, asynchronously dispatches to "deploy/after_push" script in your application. This script executes on the server and also calls "deploy/before_restart", "restart", and "after_restart" callbacks if they are present.
+The `git deploy setup` command installed a `post-receive` git hook in the remote
+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/after_push` - on subsequent pushes. It in turn executes:
+  * `deploy/before_restart`
+  * `deploy/restart`
+  * `deploy/after_restart`
 
-These scripts are ordinary unix executable files. The ones which are generated for you are written in shell script and Ruby.
+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
+script and Ruby.
 
 It's worth remembering that "after_push" is done **asynchronously from your git push**. This is because migrating the database and updating submodules might take a long time and you don't want to wait for all that during a git push. But, this means that when the push is done, the server has *not yet restarted*. You might need to wait a few seconds or a minute.
 
 
-  [heroku]: http://heroku.com/
+  [heroku]: http://heroku.com/

data/lib/git_deploy.rb

@@ -55,7 +55,7 @@ class GitDeploy < Thor
   
   desc "restart", "Restarts the application on the server"
   def restart
-    run "cd #{deploy_to} && deploy/restart | tee -a log/deploy.log"
+    run "cd #{deploy_to} && deploy/restart 2>&1 | tee -a log/deploy.log"
   end
 
   desc "rollback", "Rolls back the checkout to before the last push"
@@ -83,15 +83,3 @@ class GitDeploy < Thor
     }
   end
 end
-
-__END__
-Multiple hosts:
-# deploy:
-  invoke :code
-  command = ["cd #{deploy_to}"]
-  command << ".git/hooks/post-reset `cat .git/ORIG_HEAD` HEAD 2>&1 | tee -a log/deploy.log"
-
-# code:
-command = ["cd #{deploy_to}"]
-command << source.scm('fetch', remote, "+refs/heads/#{branch}:refs/remotes/origin/#{branch}")
-command << source.scm('reset', '--hard', "origin/#{branch}")

data/lib/git_deploy/configuration.rb

@@ -34,7 +34,9 @@ class GitDeploy
     end
 
     def remote_urls(remote)
-      git_config["config --get-all remote.#{remote}.url"].to_s.split("\n")
+      git_config["remote -v"].to_s.split("\n").
+        select {|l| l =~ /^#{remote}\t/ }.
+        map {|l| l.split("\t")[1].sub(/\(.+?\)$/, '') }
     end
 
     def remote_url(remote = options[:remote])

data/lib/git_deploy/templates/after_push.sh

@@ -11,7 +11,7 @@ echo files changed: $(git diff $oldrev $newrev --diff-filter=ACDMR --name-only |
 
 umask 002
 
-git submodule init && git submodule sync && git submodule update
+git submodule sync && git submodule update --init --recursive
 
 run deploy/before_restart
 run deploy/restart && run deploy/after_restart

data/lib/hooks/post-receive.sh

@@ -42,11 +42,11 @@ if [ -z "${oldrev//0}" ]; then
   chmod 0664 $logfile $restart
 
   # init submodules
-  git submodule update --init | tee -a $logfile
+  git submodule update --recursive --init 2>&1 | tee -a $logfile
 else
   # log timestamp
   echo ==== $(date) ==== >> $logfile
 
   # execute the deploy hook in background
-  [ -x deploy/after_push ] && nohup deploy/after_push $oldrev $newrev 1>>$logfile 2>>$logfile &
+  [ -x deploy/after_push ] && (nohup deploy/after_push $oldrev $newrev 1>>$logfile 2>>$logfile &)
 fi

data/spec/configuration_spec.rb

@@ -1,4 +1,4 @@
-require 'rspec'
+require 'rspec/autorun'
 require 'git_deploy/configuration'
 
 describe GitDeploy::Configuration do
@@ -22,7 +22,7 @@ describe GitDeploy::Configuration do
   end
 
   def stub_remote_url(url, remote = options[:remote])
-    stub_git_config("config --get-all remote.#{remote}.url", url)
+    stub_git_config("remote -v", "#{remote}\t#{url} (fetch)")
   end
 
   describe "extracting user/host from remote url" do

metadata

@@ -1,49 +1,64 @@
 --- !ruby/object:Gem::Specification
 name: git-deploy
 version: !ruby/object:Gem::Version
-  version: 0.5.4
   prerelease: 
+  version: 0.5.5
 platform: ruby
 authors:
 - Mislav Marohnić
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2012-04-03 00:00:00.000000000 Z
+date: 2013-07-11 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
+  prerelease: false
+  type: :runtime
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - '='
+      - !ruby/object:Gem::Version
+        version: 0.14.6
   name: thor
-  requirement: &70233531184120 !ruby/object:Gem::Requirement
+  requirement: !ruby/object:Gem::Requirement
     none: false
     requirements:
-    - - ! '>='
+    - - '='
       - !ruby/object:Gem::Version
-        version: '0'
-  type: :runtime
-  prerelease: false
-  version_requirements: *70233531184120
+        version: 0.14.6
 - !ruby/object:Gem::Dependency
+  prerelease: false
+  type: :runtime
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: 2.6.6
   name: net-ssh
-  requirement: &70233531200000 !ruby/object:Gem::Requirement
+  requirement: !ruby/object:Gem::Requirement
     none: false
     requirements:
-    - - ! '>='
+    - - ~>
       - !ruby/object:Gem::Version
-        version: '0'
-  type: :runtime
-  prerelease: false
-  version_requirements: *70233531200000
+        version: 2.6.6
 - !ruby/object:Gem::Dependency
+  prerelease: false
+  type: :runtime
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: 1.1.0
   name: net-scp
-  requirement: &70233531199500 !ruby/object:Gem::Requirement
+  requirement: !ruby/object:Gem::Requirement
     none: false
     requirements:
-    - - ! '>='
+    - - ~>
       - !ruby/object:Gem::Version
-        version: '0'
-  type: :runtime
-  prerelease: false
-  version_requirements: *70233531199500
+        version: 1.1.0
 description: A tool to install useful git hooks on your remote repository to enable
   push-based, Heroku-like deployment on your host.
 email: mislav.marohnic@gmail.com
@@ -65,7 +80,8 @@ files:
 - README.markdown
 - LICENSE
 homepage: https://github.com/mislav/git-deploy
-licenses: []
+licenses:
+- MIT
 post_install_message: 
 rdoc_options: []
 require_paths:
@@ -84,9 +100,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 1.8.12
+rubygems_version: 1.8.23
 signing_key: 
 specification_version: 3
 summary: Simple git push-based application deployment
 test_files: []
-has_rdoc: