pushdeploy 0.0.22 → 0.0.23

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,41 @@
1
+ =Pushdeploy
2
+
3
+ Pushdeploy is a very simple replacement for capistrano to deploy your rails applications.
4
+ It works just as on heroku - you just say 'git push' and everything is done. No 'cap deploy' and
5
+ no additional release folders.
6
+
7
+ ==How it works
8
+
9
+ * It installs a post-receive hook in your git repository which runs 'git pull' and then runs 'after_deploy.rb' script.
10
+ * after_deploy.rb runs bundler, migrate, restarts passenger and launches all additional commands you may specify.
11
+
12
+ ==Installation
13
+
14
+ Install is very easy and consist of two steps.
15
+ Let's say you have two machines:
16
+
17
+ One is a development machine where you do all the development and from which you do git commits and pushes.
18
+ Another one is a production machine where you push your commits and where your webserver is running.
19
+
20
+ * On your development machine. Inside of your project root folder:
21
+
22
+ gem install pushdeploy
23
+ pushdeploy_create_config
24
+
25
+ It will create auto_deploy.rb script in your 'config' folder. You can edit it to add any additional commands
26
+ you want to launch on your production machine after 'git push'.
27
+
28
+ * On your production machine. Inside of your project root folder:
29
+
30
+ gem install pushdeploy
31
+ pushdeploy_install_hook
32
+
33
+ It will install a post-receive hook in your git repository. First it will try to determine the path to your repo and if it can't
34
+ it will ask you some questions about your enironment. You can also launch in manual mode by using option '-m'.
35
+
36
+ Note, that if you're using RVM you have to be in the gemset that is right for this current project. Or you have to run pushdeploy_install_hook
37
+ with the option '-m' and specify your gemset and ruby version manually.
38
+
39
+ ==Credits
40
+
41
+ Inspired and watched into code of https://github.com/tpope/hookup and https://github.com/remi/pushand
@@ -7,7 +7,6 @@ class PushDeploy
7
7
  puts 'Running after_deploy...'
8
8
 
9
9
  @deploy_to, @oldrev, @newrev = args.shift, args.shift, args.shift || 'HEAD'
10
- puts "deploy !! #{@deploy_to}"
11
10
  if @oldrev == '0000000000000000000000000000000000000000'
12
11
  @oldrev = EMPTY_DIR
13
12
  elsif @oldrev.nil?
@@ -1,3 +1,3 @@
1
1
  module Pushdeploy
2
- VERSION = "0.0.22"
2
+ VERSION = "0.0.23"
3
3
  end
metadata CHANGED
@@ -2,7 +2,7 @@
2
2
  name: pushdeploy
3
3
  version: !ruby/object:Gem::Version
4
4
  prerelease:
5
- version: 0.0.22
5
+ version: 0.0.23
6
6
  platform: ruby
7
7
  authors:
8
8
  - Artem Yankov
@@ -27,7 +27,7 @@ files:
27
27
  - .gitignore
28
28
  - Gemfile
29
29
  - MIT-LICENSE
30
- - README.md
30
+ - README.rdoc
31
31
  - Rakefile
32
32
  - bin/pushdeploy_create_config
33
33
  - bin/pushdeploy_install_hook
data/README.md DELETED
@@ -1,14 +0,0 @@
1
- Pushdeploy
2
- ==========
3
-
4
- * 1
5
- * 2
6
- * 3
7
-
8
- Install
9
- -------
10
- $ some code
11
- $ goeshere
12
-
13
- Usage
14
- -----