-
Notifications
You must be signed in to change notification settings - Fork 368
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
Avoiding :urgent strategy in the console? #495
Labels
Comments
I know it's a hack, but I put in the following code in our initializer in the ES off block:
|
Right now use your hack, I'm going to make the console strategy configurable. Also, you can submit a PR by yourself. Here it is set: https://github.com/toptal/chewy/blob/master/lib/chewy/railtie.rb#L49 |
I'll take a look at adding this functionality while I'm digging into it this weekend. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In some of our staging environments we don't have ES hooked up, and it's controlled by an environment variable to set all strategies to
:bypass
in an initializer. However when you fire up a console in that environment, an instance of the:urgent
strategy gets added to the stack:Is there a way to avoid this
:urgent
strategy getting added?Also, ideally I'd love to not have to worry about strategies at all when I just need to completely disable Chewy in certain environments. I'd love for there to be a configuration object like
enabled
that could be set to true just to stop everything Chewy related.The text was updated successfully, but these errors were encountered: