Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

The open source error catcher that's Hoptoad API compliant

This branch is 1 commit ahead and 0 commits behind master

Fetching latest commit…

Cannot retrieve the latest commit at this time

README.md

Errbit TravisCI

The open source self-hosted error catcher

Errbit is a tool for collecting and managing errors from other applications. It is Airbrake (formerly known as Hoptoad) API compliant, so if you are already using Airbrake, you can just point hoptoad_notifier at your Errbit server.

Errbit may be a good fit for you if:

  • Your exceptions may contain sensitive data that you don't want sitting on someone else's server
  • Your application is behind a firewall
  • You'd like to brand your error catcher
  • You want to add customer features to your error catcher
  • You're crazy and love managing servers

If this doesn't sound like you, you should probably stick with Airbrake. The Thoughtbot guys offer great support for it and it is much more worry-free. They have a free package and even offer a "Airbrake behind your firewall" solution.

Demo

There is a demo available at http://errbit-demo.herokuapp.com/

Email: demo@errbit-demo.herokuapp.com Password: password

Installation

Note: This app is intended for people with experience deploying and maintining Rails applications. If you're uncomfortable with any step below then Errbit is not for you. Checkout Airbrake from the guys over at Thoughtbot, which Errbit is based on.

Set up your local box or server(Ubuntu):

  1. Install MongoDB. Follow the directions here, then:
apt-get update
apt-get install mongodb
  1. Install libxml and libcurl
apt-get install libxml2 libxml2-dev libxslt-dev libcurl4-openssl-dev
  1. Install Bundler
gem install bundler

Running Locally:

  1. Install dependencies
bundle install
  1. Bootstrap Errbit. This will copy over config.yml and also seed the database.
rake errbit:bootstrap
  1. Update the config.yml and mongoid.yml files with information about your environment

  2. Start Server

script/rails server

Deploying:

  1. Bootstrap Errbit. This will copy over config.yml and also seed the database.
rake errbit:bootstrap
  1. Update the deploy.rb file with information about your server
  2. Setup server and deploy
cap deploy:setup deploy

Deploying to Heroku:

  1. Clone the repository
git clone http://github.com/errbit/errbit.git
  1. Create & configure for Heroku
gem install heroku
heroku create example-errbit --stack cedar
heroku addons:add mongohq:free
heroku addons:add sendgrid:starter
heroku config:add HEROKU=true
heroku config:add ERRBIT_HOST=some-hostname.example.com
heroku config:add ERRBIT_EMAIL_FROM=example@example.com
git push heroku master
  1. Seed the DB (NOTE: No bootstrap task is used on Heroku!)
heroku run rake db:seed
  1. If you are using a free database on Heroku, you may want to periodically clear resolved errors to free up space.
# Install the heroku cron addon, to clear resolved errors daily:
heroku addons:add cron:daily

# Or, clear resolved errors manually:
heroku rake errbit:db:clear_resolved
  1. Enjoy!

Configuring LDAP authentication:

  1. In config/config.yml, set user_has_username to true
  2. Follow the instructions at https://github.com/cschiewek/devise_ldap_authenticatable to set up the devise_ldap_authenticatable gem.

  3. If you are authenticating by username, you will need to set the user's email after authentication. You can do this by adding the following lines to app/models/user.rb:

  before_save :set_ldap_email
  def set_ldap_email
    self.email = Devise::LdapAdapter.get_ldap_param(self.username, "mail")
  end

Upgrading

Note: When upgrading Errbit, please run:

git pull origin master # assuming origin is the github.com/errbit/errbit repo
rake db:migrate

If we change the way that data is stored, this will run any migrations to bring your database up to date.

Issue Trackers

Lighthouseapp Integration

Redmine Integration

Pivotal Tracker Integration

Thoughtworks Mingle Integration

  • Account is the host of your mingle installation. i.e. https://mingle.example.com note: You should use SSL if possible.
  • Errbit uses 'sign-in name' & password authentication. You may want to set up an errbit user with limited rights.
  • Project id is the identifier of your project, i.e. awesomeapp for project at https://mingle.example.com/projects/awesomeapp
  • Card properties are comma separated key value pairs. You must specify a 'card_type', but anything else is optional. i.e. card_type = Defect, status = Open, priority = Essential

Github Issues Integration

  • For 'Account/Repository', the account will either be a username or organization. i.e. errbit/errbit
  • If you are logged in on Github, you can find your API Token on this page: https://github.com/account/admin.
  • You will also need to provide the username that your API Token is connected to.

What if Errbit has an error?

Errbit will log it's own errors to an internal app named Self.Errbit. The Self.Errbit app will be automatically created whenever the first error happens.

If your Errbit instance has logged an error, we would appreciate a bug report on Github Issues. You can post this manually at https://github.com/errbit/errbit/issues, or you can set up the Github Issues tracker for your Self.Errbit app:

  1. Go to the Self.Errbit app's edit page. If that app does not exist yet, go to the apps page and click Add a new App to create it. (You can also create it by running rake hoptoad:test.)

  2. In the Issue Tracker section, click Github Issues.

  3. Fill in the Account/Repository field with errbit/errbit.

  4. Fill in the Username field with your github username.

  5. If you are logged in on Github, you can find your API Token on this page: https://github.com/account/admin.

  6. Save the settings by clicking Update App (or Add App)

  7. You can now easily post bug reports to Github Issues by clicking the Create Issue button on a Self.Errbit error.

TODO

  • Add ability for watchers to be configured for types of notifications they should receive

Special Thanks

  • Michael Parenteau - For rocking the Errbit design and providing a great user experience.
  • Nick Recobra aka oruen - Nick is Errbit's first core contributor. He's been working hard at making Errbit more awesome.
  • Relevance - For giving me Open-source Fridays to work on Errbit and all my awesome co-workers for giving feedback and inspiration.
  • Thoughtbot - For being great open-source advocates and setting the bar with Airbrake.

Contributing

We welcome any contributions. If you need to tweak Errbit for your organization's needs, there are probably other users who will appreciate your work. Please try to determine whether or not your feature should be global or optional, and make optional features configurable via config/config.yml.

Examples of optional features:

  • Enable / disable user comments on errors.
  • Adding a username field to the User model.

How to contribute:

  • Fork the project.
  • Make your feature addition or bug fix.
  • Add tests for it. This is important so we don't break it in a future version unintentionally.
  • Commit, do not mess with Rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself we can ignore when we pull)
  • Send us a pull request. Bonus points for topic branches.

Copyright

Copyright (c) 2010-2011 Jared Pace. See LICENSE for details.

Something went wrong with that request. Please try again.