-
-
Notifications
You must be signed in to change notification settings - Fork 297
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
accommodating default rack-cache settings #52
Comments
Interesting, the rack_cache setting would then silence the logs or disable rack-cache altogether? |
Not sure I understand your question. What happens is if one uses config.action_dispatch.rack_cache =
{ metastore: "rails:/", entitystore: "rails:/", verbose: false } |
Ah, now I understand, sorry. This would happen when someone disable rack_cache then. I can add a workaround for that. |
Before this change, the following config setting which is provided as example in production.rb of current rails versions: config.action_dispatch.rack_cache = true would result in a startup failure. Fixes roidrage#52
Before this change, the following config setting which is provided as example in production.rb of current rails versions: config.action_dispatch.rack_cache = true would result in a startup failure. Fixes roidrage#52
Before this change, the following config setting which is provided as example in production.rb of current rails versions: config.action_dispatch.rack_cache = true would result in a startup failure. Fixes roidrage#52
I think starting in rails 4, rack-cache can be configured with a simple boolean like so:
And rails will use defaults: https://github.com/rails/rails/blob/master/railties/lib/rails/application/default_middleware_stack.rb#L83-L91
lograge doesn't accommodate this scenario, and ends up trying to access
[]=
ontrue
https://github.com/roidrage/lograge/blob/master/lib/lograge.rb#L103since the default verbosity is
false
anyway, this scenario can be accommodated by simply doing nothing ifapp.config.action_dispatch.rack_cache == true
let me know what you think and i can put together a pull request
The text was updated successfully, but these errors were encountered: