snapmon 1.0.0 → 1.1.0
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.
- data/README.rdoc +17 -1
- data/VERSION +1 -1
- data/snapmon.gemspec +1 -1
- metadata +1 -1
data/README.rdoc
CHANGED
@@ -13,6 +13,10 @@ Run the following in the command line in your projects root directory:
|
|
13
13
|
|
14
14
|
The script will then walk you through setting up a snapmon.conf file, which will contain settings on who to notify when your application goes down.
|
15
15
|
|
16
|
+
If you use capistrano, it will automatically update the settings in snapmon.yml whenever you deploy. If not you can run:
|
17
|
+
|
18
|
+
rake snapmon:setup
|
19
|
+
|
16
20
|
== As a gem:
|
17
21
|
|
18
22
|
Place the following in your environment.rb file:
|
@@ -25,12 +29,24 @@ Then run:
|
|
25
29
|
script/generate snapmon_config
|
26
30
|
|
27
31
|
==== Capistrano
|
28
|
-
|
32
|
+
For gem users to automatically push your config settings add the following to your deploy.rb
|
29
33
|
|
30
34
|
require 'snapmon/recipes'
|
31
35
|
|
32
36
|
Each time you deploy (using Capistrano), your configuration will be updated on snapmon.com
|
33
37
|
|
38
|
+
== Usage
|
39
|
+
|
40
|
+
See config/snapmon.yml for details on configuring monitors.
|
41
|
+
|
42
|
+
=== Enable/Disable
|
43
|
+
|
44
|
+
If you are scheduling maintenance, you can disable the monitors for a time. Simply run:
|
45
|
+
|
46
|
+
cap snapmon:disable
|
47
|
+
cap snapmon:enable
|
48
|
+
|
49
|
+
You can also use rake if you are not using capistrano
|
34
50
|
|
35
51
|
== Why A Plugin/Gem?
|
36
52
|
|
data/VERSION
CHANGED
@@ -1 +1 @@
|
|
1
|
-
1.
|
1
|
+
1.1.0
|
data/snapmon.gemspec
CHANGED