Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Newer
Older
100644 395 lines (267 sloc) 12.551 kb
c4e26cbe »
2009-08-20 Starting YARD'ing up the plugin
1 = HoptoadNotifier
34a31064 »
2007-12-18 Added hoptoad_notifier
2
e1e6a383 »
2010-01-04 Change wording to refer to the gem instead of plugin, and start a lis…
3 This is the notifier gem for integrating apps with Hoptoad.
19e1cfe1 »
2008-03-27 documentation changes
4
e2a86769 »
2010-02-18 Added upgrade instructions to the README
5 When an uncaught exception occurs, HoptoadNotifier will POST the relevant data
8394e203 »
2008-03-27 update to docs
6 to the Hoptoad server specified in your environment.
19e1cfe1 »
2008-03-27 documentation changes
7
ed12d59a »
2009-11-06 adding mailing list, IRC links
8 == Help
9
10 * {IRC}[irc://irc.freenode.net/thoughtbot]
11 * {mailing list}[http://groups.google.com/group/hoptoad-notifier-dev]
12
3496c0fd »
2010-01-27 Added an integration test and docs for rack apps
13 == Rails Installation
cee2e9b5 »
2008-11-18 Updated the README and INSTALL to inform people to remove ExceptionNo…
14
c4e26cbe »
2009-08-20 Starting YARD'ing up the plugin
15 === Remove exception_notifier
cee2e9b5 »
2008-11-18 Updated the README and INSTALL to inform people to remove ExceptionNo…
16
c4e26cbe »
2009-08-20 Starting YARD'ing up the plugin
17 in your ApplicationController, REMOVE this line:
cee2e9b5 »
2008-11-18 Updated the README and INSTALL to inform people to remove ExceptionNo…
18
19 include ExceptionNotifiable
20
21 In your config/environment* files, remove all references to ExceptionNotifier
22
23 Remove the vendor/plugins/exception_notifier directory.
24
ec02fe18 »
2010-01-25 LH-591 Added a new step in the README file
25 === Remove hoptoad_notifier plugin
26
0cd71546 »
2010-01-27 Updating the uninstall instructions to use script/plugin remove
27 Remove the vendor/plugins/hoptoad_notifier directory before installing the gem, or run:
28
29 script/plugin remove hoptoad_notifier
ec02fe18 »
2010-01-25 LH-591 Added a new step in the README file
30
021d3d1c »
2010-06-02 Add documentation for Rails 3.x installation
31 === Rails 3.x
32
33 Add the hoptoad_notifier gem to your Gemfile. In Gemfile:
34
35 gem 'hoptoad_notifier'
36
37 Then from your project's RAILS_ROOT, run:
38
39 bundle install
40 script/rails generate hoptoad --api-key your_key_here
41
42 That's it!
43
b9f295ff »
2010-01-19 Updated the README with instructions for installing/configuring the gem
44 === Rails 2.x
8394e203 »
2008-03-27 update to docs
45
e1e6a383 »
2010-01-04 Change wording to refer to the gem instead of plugin, and start a lis…
46 Add the hoptoad_notifier gem to your app. In config/environment.rb:
8394e203 »
2008-03-27 update to docs
47
e1e6a383 »
2010-01-04 Change wording to refer to the gem instead of plugin, and start a lis…
48 config.gem 'hoptoad_notifier'
49
50 Then from your project's RAILS_ROOT, run:
51
52 rake gems:install
e38b6a74 »
2010-01-22 Update documentation to outline the need to vendor the hoptoad_notifi…
53 rake gems:unpack GEM=hoptoad_notifier
5bc06de5 »
2010-05-14 revise gem unpack instructions step
54 script/generate hoptoad --api-key your_key_here
e38b6a74 »
2010-01-22 Update documentation to outline the need to vendor the hoptoad_notifi…
55
56 As always, if you choose not to vendor the hoptoad_notifier gem, make sure
57 every server you deploy to has the gem installed or your application won't start.
58
b9f295ff »
2010-01-19 Updated the README with instructions for installing/configuring the gem
59 === Rails 1.2.6
8394e203 »
2008-03-27 update to docs
60
e2a86769 »
2010-02-18 Added upgrade instructions to the README
61 Install the hoptoad_notifier gem:
52b7460b »
2010-02-02 add more info to README for 1.2.6
62
4d8e880e »
2010-02-02 Adding additional instructions for Rails 1.2.6
63 gem install hoptoad_notifier
64
65 Once installed, you should vendor the hoptoad_notifier gem:
66
67 mkdir vendor/gems
3849ca69 »
2010-02-02 fix gem unpack line for 1.2.6
68 cd vendor/gems
4d8e880e »
2010-02-02 Adding additional instructions for Rails 1.2.6
69 gem unpack hoptoad_notifier
52b7460b »
2010-02-02 add more info to README for 1.2.6
70
1be3591f »
2010-02-02 Typesetting in README.rdoc
71 And then add the following to the Rails::Initializer.run do |config|
4d8e880e »
2010-02-02 Adding additional instructions for Rails 1.2.6
72 block in environment.rb so that the vendored gem is loaded.
52b7460b »
2010-02-02 add more info to README for 1.2.6
73
74 # Add the vendor/gems/*/lib directories to the LOAD_PATH
75 config.load_paths += Dir.glob(File.join(RAILS_ROOT, 'vendor', 'gems', '*', 'lib'))
76
77 Next add something like this at the bottom of your config/environment.rb:
34a31064 »
2007-12-18 Added hoptoad_notifier
78
4d8e880e »
2010-02-02 Adding additional instructions for Rails 1.2.6
79 require 'hoptoad_notifier'
80 require 'hoptoad_notifier/rails'
ece01054 »
2008-02-04 Updated README to have the right config example.
81 HoptoadNotifier.configure do |config|
b9f295ff »
2010-01-19 Updated the README with instructions for installing/configuring the gem
82 config.api_key = 'your_key_here'
ece01054 »
2008-02-04 Updated README to have the right config example.
83 end
6a12bbe3 »
2009-03-10 Auto-including the Catcher into ApplicationController::Base, updated …
84
52b7460b »
2010-02-02 add more info to README for 1.2.6
85 You will also need to copy the hoptoad_notifier_tasks.rake file into your
4d8e880e »
2010-02-02 Adding additional instructions for Rails 1.2.6
86 RAILS_ROOT/lib/tasks directory in order for the rake hoptoad:test task to work:
87
e2a86769 »
2010-02-18 Added upgrade instructions to the README
88 cp vendor/gems/hoptoad_notifier-*/generators/hoptoad/templates/hoptoad_notifier_tasks.rake lib/tasks
6df61b3b »
2009-07-23 From http://help.hoptoadapp.com/discussions/suggestions/94 - mention …
89
52b7460b »
2010-02-02 add more info to README for 1.2.6
90 As always, if you choose not to vendor the hoptoad_notifier gem, make sure
91 every server you deploy to has the gem installed or your application won't start.
92
e2a86769 »
2010-02-18 Added upgrade instructions to the README
93 === Upgrading From Earlier Versions of Hoptoad
94
95 If you're currently using the plugin version (if you have a
96 vendor/plugins/hoptoad_notifier directory, you are), you'll need to perform a
97 few extra steps when upgrading to the gem version.
98
99 Add the hoptoad_notifier gem to your app. In config/environment.rb:
100
101 config.gem 'hoptoad_notifier'
102
83924f85 »
2010-02-18 Fixed a typo
103 Remove the plugin:
e2a86769 »
2010-02-18 Added upgrade instructions to the README
104
105 rm -rf vendor/plugins/hoptoad_notifier
106
e2a23804 »
2010-06-02 Add a note to README about removing the explicit Catcher #include in …
107 Make sure the following line DOES NOT appear in your ApplicationController file:
108
109 include HoptoadNotifier::Catcher
110
111 If it does, remove it. The new catcher is automatically included by the gem
112 version of Hoptoad.
113
e2a86769 »
2010-02-18 Added upgrade instructions to the README
114 Before running the hoptoad generator, you need to find your project's API key.
115 Log in to your account at hoptoadapp.com, and click on the "Projects" button.
116 Then, find your project in the list, and click on its name. In the left-hand
117 column, you'll see an "Edit this project" button. Click on that to get your
118 project's API. (If you accidentally use your personal API auth_token, you won't
119 be able to install the gem.)
120
121 Then from your project's RAILS_ROOT, run:
122
123 rake gems:install
124 script/generate hoptoad --api-key your_key_here
125
126 Once installed, you should vendor the hoptoad_notifier gem.
127
128 rake gems:unpack GEM=hoptoad_notifier
129
130 As always, if you choose not to vendor the hoptoad_notifier gem, make sure
131 every server you deploy to has the gem installed or your application won't
132 start.
133
d9926a37 »
2010-02-22 Added notice about removing hoptoad rake tasks to upgrade gem
134 == Upgrading from Earlier Versions of the Hoptoad Gem (with config.gem)
135
136 If you're currently using the gem version of the hoptoad_notifier and have
137 a version of Rails that uses config.gem (in the 2.x series), there is
138 a step or two that you need to do to upgrade. First, you need to remove
139 the old version of the gem from vendor/gems:
140
141 rm -rf vendor/gems/hoptoad_notifier-X.X.X
142
143 Then you must remove the hoptoad_notifier_tasks.rake file from lib:
144
145 rm lib/tasks/hoptoad_notifier_tasks.rake
146
147 You can them continue to install normally. If you don't remove the rake file,
148 you will be unable to unpack this gem (Rails will think it's part of the
149 framework).
150
b9f295ff »
2010-01-19 Updated the README with instructions for installing/configuring the gem
151 === Testing it out
19e1cfe1 »
2008-03-27 documentation changes
152
e2a86769 »
2010-02-18 Added upgrade instructions to the README
153 You can test that Hoptoad is working in your production environment by using
8394e203 »
2008-03-27 update to docs
154 this rake task (from RAILS_ROOT):
24db7486 »
2008-03-12 documentation
155
a11bd687 »
2008-07-25 More README work, to take out references to pre-Rails 2 and to take o…
156 rake hoptoad:test
24db7486 »
2008-03-12 documentation
157
e2a86769 »
2010-02-18 Added upgrade instructions to the README
158 If everything is configured properly, that task will send a notice to Hoptoad
a11bd687 »
2008-07-25 More README work, to take out references to pre-Rails 2 and to take o…
159 which will be visible immediately.
8394e203 »
2008-03-27 update to docs
160
3496c0fd »
2010-01-27 Added an integration test and docs for rack apps
161 == Rack
162
163 In order to use hoptoad_notifier in a non-Rails rack app, just load the
164 hoptoad_notifier, configure your API key, and use the HoptoadNotifier::Rack
165 middleware:
166
167 require 'rack'
168 require 'hoptoad_notifier'
169
170 HoptoadNotifier.configure do |config|
171 config.api_key = 'my_api_key'
172 end
173
174 app = Rack::Builder.app do
175 use HoptoadNotifier::Rack
176 run lambda { |env| raise "Rack down" }
177 end
178
d0711934 »
2010-01-27 Added integration/readme coverage of Sinatra apps
179 == Sinatra
180
181 Using hoptoad_notifier in a Sinatra app is just like a Rack app, but you have
182 to disable Sinatra's error rescuing functionality:
183
184 require 'sinatra/base'
185 require 'hoptoad_notifier'
186
187 HoptoadNotifier.configure do |config|
188 config.api_key = 'my_api_key'
189 end
190
191 class MyApp < Sinatra::Default
192 use HoptoadNotifier::Rack
193 enable :raise_errors
194
195 get "/" do
196 raise "Sinatra has left the building"
197 end
198 end
199
c4e26cbe »
2009-08-20 Starting YARD'ing up the plugin
200 == Usage
8394e203 »
2008-03-27 update to docs
201
e2a86769 »
2010-02-18 Added upgrade instructions to the README
202 For the most part, Hoptoad works for itself. Once you've included the notifier
203 in your ApplicationController (which is now done automatically by the gem),
e1e6a383 »
2010-01-04 Change wording to refer to the gem instead of plugin, and start a lis…
204 all errors will be rescued by the #rescue_action_in_public provided by the gem.
8394e203 »
2008-03-27 update to docs
205
e2a86769 »
2010-02-18 Added upgrade instructions to the README
206 If you want to log arbitrary things which you've rescued yourself from a
8394e203 »
2008-03-27 update to docs
207 controller, you can do something like this:
208
11457056 »
2008-04-01 Added ability to whitelist exceptions from being sent to the Hoptoad …
209 ...
210 rescue => ex
a4a44fc8 »
2008-04-04 README updates for correct syntax
211 notify_hoptoad(ex)
11457056 »
2008-04-01 Added ability to whitelist exceptions from being sent to the Hoptoad …
212 flash[:failure] = 'Encryptions could not be rerouted, try again.'
213 end
214 ...
8394e203 »
2008-03-27 update to docs
215
e1e6a383 »
2010-01-04 Change wording to refer to the gem instead of plugin, and start a lis…
216 The #notify_hoptoad call will send the notice over to Hoptoad for later
217 analysis. While in your controllers you use the notify_hoptoad method, anywhere
218 else in your code, use HoptoadNotifier.notify.
8394e203 »
2008-03-27 update to docs
219
e1e6a383 »
2010-01-04 Change wording to refer to the gem instead of plugin, and start a lis…
220 To perform custom error processing after Hoptoad has been notified, define the
221 instance method #rescue_action_in_public_without_hoptoad(exception) in your
222 controller.
5813f5d4 »
2009-06-05 added documentation for controller custom error processing
223
300ef187 »
2009-11-06 minor doc updates
224 == Tracking deployments in Hoptoad
0babd4f0 »
2009-03-26 deploy tracking documentation
225
300ef187 »
2009-11-06 minor doc updates
226 Paying Hoptoad plans support the ability to track deployments of your application in Hoptoad.
85945edf »
2009-05-28 Fix typo
227 By notifying Hoptoad of your application deployments, all errors are resolved when a deploy occurs,
0babd4f0 »
2009-03-26 deploy tracking documentation
228 so that you'll be notified again about any errors that reoccur after a deployment.
229
230 Additionally, it's possible to review the errors in Hoptoad that occurred before and after a deploy.
231
300ef187 »
2009-11-06 minor doc updates
232 When Hoptoad is installed as a gem, you need to add
c4e26cbe »
2009-08-20 Starting YARD'ing up the plugin
233
eaebbe9f »
2010-01-29 Fixing the capistrano hook bit in the readme
234 require 'hoptoad_notifier/capistrano'
c4e26cbe »
2009-08-20 Starting YARD'ing up the plugin
235
0babd4f0 »
2009-03-26 deploy tracking documentation
236 to your deploy.rb
237
c4e26cbe »
2009-08-20 Starting YARD'ing up the plugin
238 == Going beyond exceptions
99b34a20 »
2008-10-21 adding GOING BEYOND EXCEPTIONS section, courtesy of Eugene Bolshakov
239
e1e6a383 »
2010-01-04 Change wording to refer to the gem instead of plugin, and start a lis…
240 You can also pass a hash to notify_hoptoad method and store whatever you want,
241 not just an exception. And you can also use it anywhere, not just in
242 controllers:
99b34a20 »
2008-10-21 adding GOING BEYOND EXCEPTIONS section, courtesy of Eugene Bolshakov
243
c4e26cbe »
2009-08-20 Starting YARD'ing up the plugin
244 begin
245 params = {
e2a86769 »
2010-02-18 Added upgrade instructions to the README
246 # params that you pass to a method that can throw an exception
eb8db447 »
2008-10-21 integrating feedback from Eugene
247 }
c4e26cbe »
2009-08-20 Starting YARD'ing up the plugin
248 my_unpredicable_method(params)
99b34a20 »
2008-10-21 adding GOING BEYOND EXCEPTIONS section, courtesy of Eugene Bolshakov
249 rescue => e
250 HoptoadNotifier.notify(
8d69e4a9 »
2009-11-24 Updated notifier documentation on manually sending notifications
251 :error_class => "Special Error",
c4e26cbe »
2009-08-20 Starting YARD'ing up the plugin
252 :error_message => "Special Error: #{e.message}",
8d69e4a9 »
2009-11-24 Updated notifier documentation on manually sending notifications
253 :parameters => params
99b34a20 »
2008-10-21 adding GOING BEYOND EXCEPTIONS section, courtesy of Eugene Bolshakov
254 )
255 end
256
e1e6a383 »
2010-01-04 Change wording to refer to the gem instead of plugin, and start a lis…
257 While in your controllers you use the notify_hoptoad method, anywhere else in
258 your code, use HoptoadNotifier.notify. Hoptoad will get all the information
259 about the error itself. As for a hash, these are the keys you should pass:
99b34a20 »
2008-10-21 adding GOING BEYOND EXCEPTIONS section, courtesy of Eugene Bolshakov
260
e1e6a383 »
2010-01-04 Change wording to refer to the gem instead of plugin, and start a lis…
261 * :error_class - Use this to group similar errors together. When Hoptoad catches an exception it sends the class name of that exception object.
262 * :error_message - This is the title of the error you see in the errors list. For exceptions it is "#{exception.class.name}: #{exception.message}"
263 * :parameters - While there are several ways to send additional data to Hoptoad, passing a Hash as :parameters as in the example above is the most common use case. When Hoptoad catches an exception in a controller, the actual HTTP client request parameters are sent using this key.
99b34a20 »
2008-10-21 adding GOING BEYOND EXCEPTIONS section, courtesy of Eugene Bolshakov
264
265 Hoptoad merges the hash you pass with these default options:
266
8d69e4a9 »
2009-11-24 Updated notifier documentation on manually sending notifications
267 {
268 :api_key => HoptoadNotifier.api_key,
269 :error_message => 'Notification',
270 :backtrace => caller,
271 :parameters => {},
272 :session => {}
273 }
99b34a20 »
2008-10-21 adding GOING BEYOND EXCEPTIONS section, courtesy of Eugene Bolshakov
274
275 You can override any of those parameters.
8394e203 »
2008-03-27 update to docs
276
48f21797 »
2010-03-10 LH-556 Clarify sending ENV environment variables
277 === Sending shell environment variables when "Going beyond exceptions"
278
279 One common request we see is to send shell environment variables along with
280 manual exception notification. We recommend sending them along with CGI data
281 or Rack environment (:cgi_data or :rack_env keys, respectively.)
282
283 See HoptoadNotifier::Notice#initialize in lib/hoptoad_notifier/notice.rb for
284 more details.
285
c4e26cbe »
2009-08-20 Starting YARD'ing up the plugin
286 == Filtering
11457056 »
2008-04-01 Added ability to whitelist exceptions from being sent to the Hoptoad …
287
e2a86769 »
2010-02-18 Added upgrade instructions to the README
288 You can specify a whitelist of errors, that Hoptoad will not report on. Use
289 this feature when you are so apathetic to certain errors that you don't want
36467260 »
2008-07-25 More README/INSTALL fixes.
290 them even logged.
65e18b3d »
2008-04-01 Updated name of #inform_hoptoad to #notify in README and formatted li…
291
e2a86769 »
2010-02-18 Added upgrade instructions to the README
292 This filter will only be applied to automatic notifications, not manual
65e18b3d »
2008-04-01 Updated name of #inform_hoptoad to #notify in README and formatted li…
293 notifications (when #notify is called directly).
11457056 »
2008-04-01 Added ability to whitelist exceptions from being sent to the Hoptoad …
294
295 Hoptoad ignores the following exceptions by default:
c4e26cbe »
2009-08-20 Starting YARD'ing up the plugin
296
11457056 »
2008-04-01 Added ability to whitelist exceptions from being sent to the Hoptoad …
297 ActiveRecord::RecordNotFound
a4a44fc8 »
2008-04-04 README updates for correct syntax
298 ActionController::RoutingError
d6ca96c7 »
2008-04-04 Fixed bug related to refactoring of #ignore=, added InvalidAuthentici…
299 ActionController::InvalidAuthenticityToken
b04d54d8 »
2009-06-29 Adding ActionController::UnknownAction to the readme list of default …
300 ActionController::UnknownAction
a4a44fc8 »
2008-04-04 README updates for correct syntax
301 CGI::Session::CookieStore::TamperedWithCookie
853aa352 »
2009-05-28 adding information about environment filters to the README
302
e2a86769 »
2010-02-18 Added upgrade instructions to the README
303 To ignore errors in addition to those, specify their names in your Hoptoad
65e18b3d »
2008-04-01 Updated name of #inform_hoptoad to #notify in README and formatted li…
304 configuration block.
11457056 »
2008-04-01 Added ability to whitelist exceptions from being sent to the Hoptoad …
305
306 HoptoadNotifier.configure do |config|
a6f405be »
2008-07-14 Changed project_name to api_key
307 config.api_key = '1234567890abcdef'
a4a44fc8 »
2008-04-04 README updates for correct syntax
308 config.ignore << ActiveRecord::IgnoreThisError
11457056 »
2008-04-01 Added ability to whitelist exceptions from being sent to the Hoptoad …
309 end
310
e2a86769 »
2010-02-18 Added upgrade instructions to the README
311 To ignore *only* certain errors (and override the defaults), use the
65e18b3d »
2008-04-01 Updated name of #inform_hoptoad to #notify in README and formatted li…
312 #ignore_only attribute.
11457056 »
2008-04-01 Added ability to whitelist exceptions from being sent to the Hoptoad …
313
314 HoptoadNotifier.configure do |config|
a6f405be »
2008-07-14 Changed project_name to api_key
315 config.api_key = '1234567890abcdef'
a4a44fc8 »
2008-04-04 README updates for correct syntax
316 config.ignore_only = [ActiveRecord::IgnoreThisError]
11457056 »
2008-04-01 Added ability to whitelist exceptions from being sent to the Hoptoad …
317 end
318
2e08e444 »
2009-03-10 Adding in ignore_user_agent, patch contributed by phillip on tender.
319 To ignore certain user agents, add in the #ignore_user_agent attribute as a
320 string or regexp:
321
322 HoptoadNotifier.configure do |config|
323 config.api_key = '1234567890abcdef'
324 config.ignore_user_agent << /Ignored/
325 config.ignore_user_agent << 'IgnoredUserAgent'
326 end
327
05199ded »
2009-04-23 Merging in Kevin Menard's ignore_by_filter patch and updating README …
328 To ignore exceptions based on other conditions, use #ignore_by_filter:
329
330 HoptoadNotifier.configure do |config|
331 config.api_key = '1234567890abcdef'
332 config.ignore_by_filter do |exception_data|
333 true if exception_data[:error_class] == "RuntimeError"
334 end
335 end
336
300ef187 »
2009-11-06 minor doc updates
337 To replace sensitive information sent to the Hoptoad service with [FILTERED] use #params_filters:
853aa352 »
2009-05-28 adding information about environment filters to the README
338
339 HoptoadNotifier.configure do |config|
340 config.api_key = '1234567890abcdef'
7be8dce5 »
2009-07-15 Adding information about filtering out custom params to the readme
341 config.params_filters << "credit_card_number"
853aa352 »
2009-05-28 adding information about environment filters to the README
342 end
343
1ff0714a »
2009-10-09 Updated the readme
344 Note that, when rescuing exceptions within an ActionController method,
69f406cf »
2010-06-24 wip: fixing rails3 filter_params and applying params filters to sessi…
345 hoptoad_notifier will reuse filters specified by #filter_parameter_logging.
1ff0714a »
2009-10-09 Updated the readme
346
c4e26cbe »
2009-08-20 Starting YARD'ing up the plugin
347 == Testing
8394e203 »
2008-03-27 update to docs
348
300ef187 »
2009-11-06 minor doc updates
349 When you run your tests, you might notice that the Hoptoad service is recording
e2a86769 »
2010-02-18 Added upgrade instructions to the README
350 notices generated using #notify when you don't expect it to. You can
351 use code like this in your test_helper.rb to redefine that method so those
8394e203 »
2008-03-27 update to docs
352 errors are not reported while running tests.
353
6c3e9130 »
2010-01-11 Fixed bug in the docs
354 module HoptoadNotifier
355 def self.notify(thing)
65e18b3d »
2008-04-01 Updated name of #inform_hoptoad to #notify in README and formatted li…
356 # do nothing.
357 end
358 end
99b34a20 »
2008-10-21 adding GOING BEYOND EXCEPTIONS section, courtesy of Eugene Bolshakov
359
95b86dc7 »
2010-02-23 document proxy support
360 == Proxy Support
361
362 The notifier supports using a proxy, if your server is not able to directly reach the Hoptoad servers. To configure the proxy settings, added the following information to your Hoptoad configuration block.
363
364 HoptoadNotifier.configure do |config|
365 config.proxy_host = ...
366 config.proxy_port = ...
367 config.proxy_user = ...
368 config.proxy_pass = ...
369
1f878913 »
2010-01-19 Added integration coverage and fixes for older versions of Rails
370 == Supported Rails versions
371
372 See SUPPORTED_RAILS_VERSIONS for a list of official supported versions of
373 Rails.
ab991c81 »
2009-06-11 Updating README with supported versions of Rails
374
e1e6a383 »
2010-01-04 Change wording to refer to the gem instead of plugin, and start a lis…
375 Please open up a support ticket on Tender ( http://help.hoptoadapp.com ) if
376 you're using a version of Rails that is not listed above and the notifier is
377 not working properly.
ab991c81 »
2009-06-11 Updating README with supported versions of Rails
378
2ddeb84b »
2010-07-21 Initial injection of JS notifier.
379 == Javascript Notifer
380
381 To automatically include the Javascript node on every page, set the
382 :js_notifier to true:
383
384 HoptoadNotifier.configure do |config|
385 config.js_notifier = true
386 end
387
388 It automatically uses the API key, host, and port specified in the
389 configuration.
390
c4e26cbe »
2009-08-20 Starting YARD'ing up the plugin
391 == Thanks
99b34a20 »
2008-10-21 adding GOING BEYOND EXCEPTIONS section, courtesy of Eugene Bolshakov
392
e1e6a383 »
2010-01-04 Change wording to refer to the gem instead of plugin, and start a lis…
393 Thanks to Eugene Bolshakov for the excellent write-up on GOING BEYOND
394 EXCEPTIONS, which we have included above.
Something went wrong with that request. Please try again.