capfire 0.3.0 → 0.3.2

Sign up to get free protection for your applications and to get access to all the features.
@@ -4,12 +4,14 @@ Inspired by http://github.com/blog/609-tracking-deploys-with-compare-view we , h
4
4
 
5
5
  This gem adds a way to send a message to campfire after a deploy, in the message is the app-name, the github-compare view url and the deployer.
6
6
 
7
+ Since version 0.3.0 capfire will also check if the currently deployed version differs from the version you're about to deploy, aka see if you forgot to do a push before deploying. If this happens it'll also post a message to Campfire, since we all know public shaming JustWorks(tm).
8
+
7
9
  == Install
8
10
  `gem install capfire`
9
11
 
10
12
  Now either the generator:
11
13
  `script/generate capfire -k "campfire_token" -r "chat_room" -a "campfire_account"`
12
- This will create a ~/.campfire file and add a line to your config/deploy.rb file.
14
+ This will create a ~/.campfire file and add a line to your config/deploy.rb file.
13
15
 
14
16
  Or do it by hand:
15
17
  In your config/deploy.rb append `require capfire/capistrano`, in your home folder create .campfire with the following contents
@@ -23,9 +25,13 @@ with `cap #args# (#compare_url#)"
23
25
 
24
26
  From now on your deploys will send a message to Campfire containing the Github-compare view url.
25
27
 
28
+ == Options
29
+
30
+ Since it's initial release a few options have crept into capfire, take a look at `lib/capfire/capistrano' and look for cowsay, the same for the messages, they're all adjustable in your settings file.
31
+ '
26
32
  == Multiple Projects
27
33
 
28
- Either run the generator (without options since you've arleady got a ~/.campfire file it won't complain) again or append by hand the `require capfire/capistrano` line to your deploy file.
34
+ Either run the generator (without options since you've arleady got a ~/.campfire file it won't complain) again or append by hand the `require capfire/capistrano` line to your deploy file.
29
35
 
30
36
  == Usage
31
37
  After the install you're done. Really, do a `cap deploy` and it should post to campfire.
data/Rakefile CHANGED
@@ -6,7 +6,7 @@ begin
6
6
  Jeweler::Tasks.new do |gem|
7
7
  gem.name = "capfire"
8
8
  gem.summary = %Q{Send a notification to Campfire after a cap deploy}
9
- gem.description = %Q{Inspired by http://github.com/blog/609-tracking-deploys-with-compare-view}
9
+ gem.description = %Q{Send a notification to Campfire after a cap deploy}
10
10
  gem.email = "piet@10to1.be"
11
11
  gem.homepage = "http://github.com/pjaspers/capfire"
12
12
  gem.authors = ["pjaspers", "atog"]
data/VERSION CHANGED
@@ -1 +1 @@
1
- 0.3.0
1
+ 0.3.2
@@ -1,5 +1,8 @@
1
1
  # Gem for applications to automatically post to Campfire after an deploy.
2
2
 
3
+ require 'broach'
4
+ require 'etc'
5
+
3
6
  class Capfire
4
7
  # To see how it actually works take a gander at the generator
5
8
  # or in the capistrano.rb
@@ -3,7 +3,6 @@
3
3
  # There are two ways to use Capfire, either run the generator (see the README)
4
4
  # or add 'require "capfire/capistrano"' to your deploy.rb.
5
5
 
6
- require 'broach'
7
6
  require 'capfire'
8
7
 
9
8
  Capistrano::Configuration.instance(:must_exist).load do
metadata CHANGED
@@ -1,13 +1,13 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: capfire
3
3
  version: !ruby/object:Gem::Version
4
- hash: 19
4
+ hash: 23
5
5
  prerelease: false
6
6
  segments:
7
7
  - 0
8
8
  - 3
9
- - 0
10
- version: 0.3.0
9
+ - 2
10
+ version: 0.3.2
11
11
  platform: ruby
12
12
  authors:
13
13
  - pjaspers
@@ -49,7 +49,7 @@ dependencies:
49
49
  version: 0.2.1
50
50
  type: :runtime
51
51
  version_requirements: *id002
52
- description: Inspired by http://github.com/blog/609-tracking-deploys-with-compare-view
52
+ description: Send a notification to Campfire after a cap deploy
53
53
  email: piet@10to1.be
54
54
  executables: []
55
55