Hi!

Today is 25 Dec 2024 and Christmas. Awesome time to make greet announce.

I am announcing fork of Errbit. Welcome, Errbit-NG!

So, why to fork, you will ask me?

Current development of Errbit is stale. I try hard to make a bunch of changes to keep it up-to-date and working. Anyone can see my PRs to Errbit:

  1. errbit#1520 – My first PR updates Ruby from 2.7.5 to 2.7.6, puma and nokogiri. All this updates contain CVE fixes (security).
  2. errbit#1522 – Remove unless binstubs and fix bin/rails and bin/rake binstubs.
  3. errbit#1523 – Update mini_racer gem (so, errbit can be run-ed on modern macOS).
  4. errbit#1525 – Remove Rack::Deflater (just use http cache server or reverse proxy like nginx or traefik).
  5. errbit#1526 – Just another bunch of dependencies updates.
  6. errbit#1528 – Remove GEMFILE_RUBY_VERSION.
  7. errbit#1530 – Rails 5.0 upgrade.
  8. errbit#1531 – Migrate to GitHub Actions, update gems, improve security with omniauth-rails_csrf_protection gem.

And then, PR with Rails 6.1 upgrade stuck from Aug 27, 2022.

After this, I understand that Errbit developers don’t use it in production.

So, what I should do when I need simple and self-hosted error tracker? I fork it.

With all my respect to all original Authors of Errbit and with all my respect to all contributors to original Errbit, We need fresh blood.

Ok, who am I? I am Igor (Ihor) Zubkov. Software developer from Mariupol, Ukraine. You may see Mariupol in news and see how brave defenders of Ukraine fight with russian occupants.

So, fork goal:

  1. Keep errbit instances up-and-running with minimal effort.
  2. Keep errbit up-to-date with dependencies (security part).
  3. Keep errbit on latest and the best technologies that Rails ecosystem provides. Like: stimulus, turbo, solid_queue.

Before describing any plans, let me show what was already done in fork.

  1. Rails 5.1.7
  2. Rails 5.2.8.1
  3. Enable bootsnap
  4. Ruby to 3.1.6 & Rails to 6.0.6.1
  5. Rails 6.1.7.10
  6. Enable dependabot
  7. Bundler: enable CHECKSUMS
  8. Add simplecov gem
  9. Migrate to zeitwerk loader
  10. Improve bundler platforms support (for faster docker image builds)
  11. Ruby 3.2.6
  12. Standardize project
  13. Run test on Ruby 3.1 (for JRuby support), 3.2 and 3.2
  14. JRuby support
  15. Replace poltergeist with selenium-webdriver
  16. Drop mini_racer gem
  17. Ruby 3.3.6
  18. Update RubyGems to 3.6.1 & Bundler to 2.6.1

And… Plan:

  1. Enable official docker builds
  2. Upgrade Ruby on Rails to 7.0.x
  3. Upgrade Ruby on Rails to 7.1.x
  4. Upgrade Ruby on Rails to 7.2.x
  5. Upgrade Ruby on Rails to 8.0.x
  6. Remove jQuery
  7. Migrate to Turbo and Stimulus

First alpha release in Q1 2025. List of blocking issues:

  1. Upgrade Ruby on Rails (at least) to 7.2.x
  2. Enable official docker builds
  3. Some kind of documentation

First stable release as soon as it will be ready after alpha/beta testing.

Subscribe to RSS to track our news.

Thanks for reading!