-
Notifications
You must be signed in to change notification settings - Fork 71
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
Oink and serving assets #25
Comments
Since Oink is executed in Rack Middleware, an approach like this might be a good way to go: Happy to accept a patch that works similarly to this for Oink's middleware. |
Any progress with this? |
Seems like this is basically a development-only kind of issue. Are you making use of Oink in development? If not would just suggest turning oink off entirely in development mode. Otherwise, not sure -- you could wrap the oink middleware in your own to exclude assets. |
Just fyi, we're no longer using Oink in development. |
Would it be possible to filter out oink logging when Rails is serving assets (in development)?
It currently spams my logs like this (asset logging itself is being silenced, otherwise those requests would show up):
The text was updated successfully, but these errors were encountered: