-
-
Notifications
You must be signed in to change notification settings - Fork 482
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
Rails sentry configuration #115
Comments
@madisvain it's possible we have in issue in the rake command that its not actually configuring against the rails environment. |
@dcramer it seems to be magically working in production environment which is a good thing. My ruby skills are horrible compared to python so sorry if there is something I'm just missing here. |
As are mine :) Will defer this ticket to someone else who can help us investigate it better |
I think this is because rake raven:test does not load the current rails environment, which means your initializers won't be run and your DSN remains unset. @madisvain, can you confirm that, as a workaround, if you set your SENTRY_DSN environment variable to your DSN, will the rake test work? |
@nateberkopec yes, when set directly on the |
Running :envionment task before :test task solved it for me. I must add a check for Rails in order to work on non-rails environments and I guess it's fixed. |
Nice fix. I think #121 closes this. |
After doing everything that the getsentry website tells me
I still get
rake raven:test Your client is not configured!
If I run with the DSN provided then everything works
I'm using Rails 3.2.13
Is the documentation correct?
The text was updated successfully, but these errors were encountered: