This add-on is operated by Devels Advocates LLP
Track and manage your runtime errors directly in Github
Last updated 13 October 2015
Table of Contents
Track errors in your web application. Your team is notified when errors happen. Manage your errors from your existing project management tools. Don’t waste time recreating bug reports.
1. Provisioning the add-on
RuntimeError can be attached to a Heroku application via the CLI:
$ heroku addons:create runtimeerror:test -----> Adding runtimeerror to sharp-mountain-4005... done, v18 (test)
Once RuntimeError has been added a
RUNTIMEERROR_EMAIL setting will be available in the app configuration and will contain the runtimeerror email is used to route errors to the correct the Github project. This can be confirmed using the
heroku config:get command.
$ heroku config:get RUNTIMEERROR_EMAIL email@example.com
2. Configure the add-on
Once you’ve added the add-on, you’ll need to point to your Github repository. Do this through the configuration panel on Dashboard. You can access this in two ways. You can use the CLI:
$ heroku addons:open runtimeerror
Or you can click through from your app dashboard, into the RuntimeError add-on, and choose your Github repository you want for managing Issues.
Your application is now configured to fully integrate with the add-on.
Add the following entry into
Update application dependencies with bundler.
$ bundle install
Finally, initialize the project with a standard config
- Either using the rails generator,
rails generate runtimeerror_notifier:install
- Or by manually creating
config/initializers/runtimeerror_notifier.rbfile with the content below
if defined?(RuntimeerrorNotifier) RuntimeerrorNotifier.for ENV['RUNTIMEERROR_EMAIL'] RuntimeerrorNotifier::Notifier::IGNORED_EXCEPTIONS.push(*%w[ ActionController::RoutingError ]) end
Removing the add-on
RuntimeError can be removed via the CLI.
This will destroy all associated data and cannot be undone!
$ heroku addons:destroy runtimeerror:test -----> Removing runtimeerror from sharp-mountain-4005... done, v20 (test)
All RuntimeError support and runtime issues should be submitted to RuntimeError Support