paratrooper 1.2.1 → 1.2.2

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.
checksums.yaml CHANGED
@@ -1,15 +1,15 @@
1
1
  ---
2
2
  !binary "U0hBMQ==":
3
3
  metadata.gz: !binary |-
4
- NTNkMmU3MDBhNmJmMDNhOTQ5MDEyOTFlMjFlMzkzM2E4ZjYzYzlhZQ==
4
+ ZjZmZGEzYjhjYzkwNjNmOWRhZTkwMTFkOGY5ZGMxNjdjN2UzZDZiYQ==
5
5
  data.tar.gz: !binary |-
6
- NmQzYmEwYTNmYTQ0YjQwMTFkMWE3MjI0ZThhZGNmODZhYWM1OGI4ZA==
6
+ NWVhZTgyOTg4YTA5OWQ0NDIwMjJmYmRjNDJhNGM5OGM5NDFjZjFkYQ==
7
7
  !binary "U0hBNTEy":
8
8
  metadata.gz: !binary |-
9
- Njg3ZDg5YmNjZTcxYTc2YTVlNGIwZThlNjg2NTAxYTZhMjRkOTVhZGY4NWZi
10
- ODRkNjJiOTJiOGJhYmZkYTQ2MDE4ODNjYmIwYTEyNGFhOGM5NWU5OGY0NjY5
11
- NzdjYTBhY2RjNzRlZDkxOGUyZjNhNWExNWNhN2VhOGM4MTlkNTE=
9
+ ZWMzMmYxMjU4MjcwMDRiOWU2NzVhOGE1NDg4NWNiZDJmM2EzYjljN2Y0MGI3
10
+ ZWMxZTgzOWQ5OGQ4NGJhMmNiOGE4OGE2YjMzZjEzYmJlMTA3ZGVjZjIyM2Fj
11
+ NGYxNzFhZmU1ODg0ZmE3ZDEwOWM0MzI0MjdhYmZjZjQyZmZiODI=
12
12
  data.tar.gz: !binary |-
13
- MzhjZTAyMzkyYTFhNjU5YTkzZmI3YWY1YzkzZGUwYjBjMWM3NTdjMTI4NzU2
14
- YTgyNzYwNGJmZDVjNTk2YjAyNmNjNjYxZWQxY2VkNzY1MDI0ZDgwY2IwNzcw
15
- MmU5MTRhZDdiMjI5MjRiYzY4YWZhYzM4MDU3Y2RjNzVhZTZhYmY=
13
+ NjRjMDVkNTk3NWFmZDgzZDhiMWNiNjU0YjZmMTJkZDM2NmI0NTc0OWViN2Jj
14
+ N2RkMGEyNjU5OTkzYWEwZGI3YzA3YTlhNzQ1NjdhMjg1OWQ1YTliYjU3YWY3
15
+ Njg1NTY3Y2Y0MTIzYTYzOGZjNTkyZDg0NGViMDQxNTMwMmQ5ZmI=
data/README.md CHANGED
@@ -44,15 +44,15 @@ Paratrooper::Deploy.new('amazing-app', tag: 'staging')
44
44
 
45
45
  ## Authentication
46
46
 
47
- You can authenticate your Heroku account in a few different ways:
47
+ You can authenticate your Heroku account in a few ways:
48
48
 
49
- * Providing API Key
49
+ * Provide an API Key
50
50
 
51
51
  ```ruby
52
52
  Paratrooper::Deploy.new('app', api_key: 'API_KEY')
53
53
  ```
54
54
 
55
- * Setting an environment variable
55
+ * Set an environment variable
56
56
 
57
57
  ```ruby
58
58
  ENV['HEROKU_API_KEY'] = 'API_KEY'
@@ -65,11 +65,11 @@ Paratrooper::Deploy.new('app')
65
65
  Paratrooper::Deploy.new('app')
66
66
  ```
67
67
 
68
- This method works via a local Netrc file which is handled via the [Heroku Toolbelt][] and is the default and preferred method of providing your authentication key.
68
+ This method works via a local Netrc file handled via the [Heroku Toolbelt][] and is the default and preferred method for providing authentication keys.
69
69
 
70
70
  ## Tag Management
71
71
 
72
- By providing tag options into Paratrooper, your code can be tagged and deployed from different reference points.
72
+ By providing tag options for Paratrooper, your code can be tagged and deployed from various reference points.
73
73
 
74
74
  ### Staging example
75
75
  ```ruby
@@ -77,7 +77,7 @@ By providing tag options into Paratrooper, your code can be tagged and deployed
77
77
  tag: 'staging'
78
78
  )
79
79
  ```
80
- This will create/update a `staging` git tag at `HEAD`
80
+ This will create/update a `staging` git tag at `HEAD`.
81
81
 
82
82
  ### Production example
83
83
  ```ruby
@@ -86,15 +86,15 @@ This will create/update a `staging` git tag at `HEAD`
86
86
  match_tag_to: 'staging'
87
87
  )
88
88
  ```
89
- This will create/update a `production` git tag at `staging` and deploys the `production` tag
89
+ This will create/update a `production` git tag at `staging` and deploy the `production` tag.
90
90
 
91
91
  ## Sensible Default Deployment
92
92
 
93
- You can use the objects methods any way you'd like, but we've provided a sensible default at `Paratrooper#deploy`
93
+ You can use the object's methods any way you'd like, but we've provided a sensible default at `Paratrooper#deploy`.
94
94
 
95
95
  This will perform the following tasks:
96
96
 
97
- * Activating maintenance mode
97
+ * Activate maintenance mode
98
98
  * Create or update a git tag (if provided)
99
99
  * Push changes to Heroku
100
100
  * Run database migrations
@@ -131,9 +131,9 @@ end
131
131
 
132
132
  ## Bucking the Norm
133
133
 
134
- Our default deploy gets us most of the way, but maybe it's not for you. We've
134
+ Our default deploy gets us most of the way, but maybe it's not for you--we've
135
135
  got you covered. Every deployment method sends a notification that can be
136
- captured and used in most any way you can think of.
136
+ captured and used in almost any way you can imagine.
137
137
 
138
138
  For example, say you want to let [New Relic][] know that you are deploying and
139
139
  to disable your application monitoring.
@@ -154,7 +154,7 @@ namespace :deploy do
154
154
  tag: 'production',
155
155
  match_tag_to: 'staging',
156
156
  notifiers: [
157
- Paratrooper::Notifers::ScreenNotifier.new,
157
+ Paratrooper::Notifiers::ScreenNotifier.new,
158
158
  Paratrooper::Newrelic::Notifier.new('api_key', 'account_id', 'application_id')
159
159
  ]
160
160
  )
@@ -163,23 +163,23 @@ end
163
163
  ```
164
164
 
165
165
  * The `ScreenNotifier` is added by default so when you override the `notifiers`
166
- option you need to manually add it in to continue getting screen output.
166
+ option you need to manually add it to continue receiving screen output.
167
167
 
168
168
  To make your own notifier, take a look at [`Paratrooper::Notifier`][] to see
169
- what methods are available to be overridden.
169
+ what methods are available for override.
170
170
 
171
171
 
172
172
  ## Contributing
173
173
 
174
174
  1. Fork it
175
- 2. Create your feature branch (`git checkout -b my-new-feature`)
176
- 3. Commit your changes (`git commit -am 'Add some feature'`)
177
- 4. Push to the branch (`git push origin my-new-feature`)
178
- 5. Create new Pull Request
175
+ 2. Create your feature branch (`git checkout -b my-new-feature`).
176
+ 3. Commit your changes (`git commit -am 'Add some feature'`).
177
+ 4. Push to the branch (`git push origin my-new-feature`).
178
+ 5. Create new Pull Request.
179
179
 
180
180
  ## Thanks
181
181
 
182
- * [Rye Mason][] for the fantastic heading image
182
+ * [Rye Mason][] for the fantastic heading image.
183
183
 
184
184
  [Heroku]: http://heroku.com
185
185
  [Heroku Toolbelt]: http://toolbelt.heroku.com
@@ -66,7 +66,7 @@ module Paratrooper
66
66
  unless tag_name.nil? || tag_name.empty?
67
67
  notify(:update_repo_tag)
68
68
  system_call "git tag #{tag_name} #{match_tag} -f"
69
- system_call "git push -f origin #{tag_name}"
69
+ system_call "git push -f #{git_remote} #{tag_name}"
70
70
  end
71
71
  end
72
72
 
@@ -1,3 +1,3 @@
1
1
  module Paratrooper
2
- VERSION = "1.2.1"
2
+ VERSION = "1.2.2"
3
3
  end
@@ -111,7 +111,7 @@ describe Paratrooper::Deploy do
111
111
  end
112
112
 
113
113
  it 'pushes git tag' do
114
- system_caller.should_receive(:execute).with('git push -f origin awesome')
114
+ system_caller.should_receive(:execute).with('git push -f git@heroku.com:app.git awesome')
115
115
  deployer.update_repo_tag
116
116
  end
117
117
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: paratrooper
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.2.1
4
+ version: 1.2.2
5
5
  platform: ruby
6
6
  authors:
7
7
  - Matt Polito
@@ -9,7 +9,7 @@ authors:
9
9
  autorequire:
10
10
  bindir: bin
11
11
  cert_chain: []
12
- date: 2013-03-14 00:00:00.000000000 Z
12
+ date: 2013-03-27 00:00:00.000000000 Z
13
13
  dependencies:
14
14
  - !ruby/object:Gem::Dependency
15
15
  name: rake