Packages
honeybadger
0.4.0
0.28.0
0.27.0
0.26.0
0.25.0
0.24.1
0.24.0
0.23.0
0.22.1
0.22.0
0.21.0
0.20.0
0.19.0
0.18.1
0.18.0
0.17.0
0.16.4
0.16.3
0.16.2
0.16.1
0.16.0
0.15.0
0.14.1
0.14.0
0.13.1
0.13.0
0.12.1
0.12.0
0.11.0
0.10.3
0.10.2
0.10.1
0.10.0
0.9.0
0.8.0
0.7.0
0.7.0-beta
0.6.3
0.6.2
0.6.1
0.6.0
0.5.0
0.4.0
0.3.1
0.3.0
0.2.0
0.1.2
0.1.1
0.1.0
Elixir client, Plug and error_logger for integrating with the Honeybadger.io exception tracker"
Current section
Files
Jump to
Current section
Files
honeybadger
CHANGELOG.md
CHANGELOG.md
# Honeybadger-Elixir Changelog
## v0.4.0
Due to the `Mix.env/0` function always being set to `prod` for dependencies and
Mix being compiled out of applications by exrm, we now require you to
explicitly declare your `environment_name` for every environment in your
`config.exs` files.
Example:
# config/dev.exs
config :honeybager, environment_name: :dev
Doing this will ensure you get accurate environment information for exceptions
that happen at runtime as well as compile time. You can also set the
`environment_name` setting a `MIX_ENV` environment variable.
Example:
$ MIX_ENV=prod mix phoenix.server
**Note:** setting `environment_name` in your config files takes higher
precedence than the `MIX_ENV` environment variable.
## v0.3.1
* Fix a bug where notifications reported by the `error_logger` were not
sending the the context