This repository has been archived by the owner on Nov 11, 2017. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Added INSTALL to display config info when the plugin is installed.
- Loading branch information
Jon Yurek
committed
Dec 1, 2009
1 parent
7220d02
commit 6c000e7
Showing
2 changed files
with
26 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
=== Configuration | ||
|
||
You should have something like this in config/initializers/hoptoad.rb. | ||
|
||
HoptoadNotifier.configure do |config| | ||
config.api_key = '1234567890abcdef' | ||
end | ||
|
||
(Please note that this configuration should be in a global configuration, and | ||
is *not* environment-specific. Hoptoad is smart enough to know what errors are | ||
caused by what environments, so your staging errors don't get mixed in with | ||
your production errors.) | ||
|
||
You can test that Hoptoad is working in your production environment by using | ||
this rake task (from RAILS_ROOT): | ||
|
||
rake hoptoad:test | ||
|
||
If everything is configured properly, that task will send a notice to Hoptoad | ||
which will be visible immediately. | ||
|
||
NOTE FOR RAILS 1.2.* USERS: | ||
|
||
You will need to copy the hoptoad_notifier_tasks.rake file into your | ||
RAILS_ROOT/lib/tasks directory in order for the rake hoptoad:test task to work. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters