-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Raygun should not depend on Mix.Project #3
Comments
Yes, this was a bit sloppy/lazy on my part. Ideally we’d keep the details section, but I will remove the code that pull values via Mix. I may be able to get away with :application.get_env here, we’ll see. If you have any other suggestions please send them my way either via a comment or pull request. Thanks!
|
I understand, but these variables just are not there anymore after compile time, :application.get_env will not help you here. |
You could probably set these options as a class variable. That should save your original reference on compile time, so that you can use it after compile time. |
Not these Mix values, but there are values that :application.get_key can use (such as :vsn). I hope to have a patch soon. :)
|
Ok, I've released version 0.1.1 which should work as a release. I have the disksup stuff commented out for the moment, but I think that the rest should be working. |
Mix values should be available at compile time, but as you are compiling to production, I'm not sure actually. |
I tested with an exrm Phoenix release and it worked. Please let me know if you have any more issues with this. I will leave this open for a few days and then I'll close it if I don't hear back. Thanks. |
@smeevil Fixed this for Honeybadger like this: smeevil/honeybadger-elixir@63f6a1c Which should work fine for Raygun, @brweber2 |
raygun/lib/raygun/format.ex
Lines 116 to 129 in 1f0afe1
If you are running your application in production using i.e. erts, mix is not included in your production build, therefore Mix.Project does not exist. Please remove it, or add mix as a dependency for the production environment, which would probably be a bad idea.
The text was updated successfully, but these errors were encountered: