Upgrading Errbit

Upgrading Errbit from v0.9.0 to v0.10.0

Remove USER_GEMFILE env support. From now, only UserGemfile is supported.
Remove SERVE_STATIC_ASSETS env support. Just remove it.
Remove RACK_ENV env support. Use RAILS_ENV env for this. Official docker image set RAILS_ENV to production.
Remove ERRBIT_ENFORCE_SSL env support. From now, Errbit always should be behind reverse proxy with HTTPS support (ACME). Like, e.g., Traefik.
Remove ERRBIT_PROTOCOL env support.
Remove ERRBIT_PORT env support.
MongoDB 4.0 is reached EOL on 21 Jun 2018. 4.0 support will be removed after v0.10.0 release.
MongoDB 4.2 is reached EOL on 09 Aug 2019. 4.2 support will be removed after v0.10.0 release.
MongoDB 4.4 is reached EOL an 25 Jul 2020. 4.4 support will be removed after v0.10.0 release.
MongoDB 5.0 is reached EOL on 08 Jul 2021. 5.0 support will be removed after v0.10.0 release.

Note: There are no migrations to run and the rake task for running migrations has been removed.

You must have already run migrations at least up to v0.3.0. Check to make sure you’re schema version is at least 20131011155638 by running rake db:version before you upgrade beyond v0.4.0
Notice fingerprinting has changed and is now easy to configure. But this means you’ll have to regenerate fingerprints on old notices in order to for them to be properly grouped with new notices. To do this run: bundle exec rake errbit:notice_refingerprint. If you were using a custom fingerprinter class in a previous version, be aware that it will no longer have any effect. Fingerprinting is now configurable within the Errbit UI.
Prior to v0.4.0, users were only able to see apps they were watching. All users can now see all apps and they can watch or unwatch any app. If you were using the watch feature to hide secret apps, you should not upgrade beyond v0.4.0.

All configuration is now done through the environment. See configuration
Ruby 1.9 and 2.0 are no longer officially supported. Please upgrade to Ruby 2.1+
Errbit now maintains an issue tracker only for GitHub. If you’re using another issue tracker integration, you may need to maintain it yourself. See Issue Trackers