-
Notifications
You must be signed in to change notification settings - Fork 46
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 4.1 compatibility? #50
Comments
Rails 4.1 should be supported. I just created an empty Rails 4.1 app, added Serving a simple
@jscheid do you think you would be able to create a sample app, so I could poke around and see what is causing the problem for you? |
Hi @thedarkone, sorry I didn't get back to you earlier. To be honest, at least for our app I don't have a need for this project or related hacks/workarounds anymore. For what it's worth, the change that made everything work quite snappy with Rails 4.1 for us was removing all the hacks and adding this setting:
Just to clarify, I don't know if that means your project isn't useful in Rails 4.1, your timings above seem to indicate it can improve matters. All I'm saying is that in our case, the app now performs well enough in dev mode without it. I can't provide you with a sample app -- the app with which I experienced the original problem isn't open source, and making a separate app for reproducing the issue would be quite a lot of work for which I just don't have the time. Feel free to close this issue and sorry I can't be of more help. |
Hi,
Is this supposed to work with Rails 4.1? I don't actually know what precisely your Gem is doing to speed things up, but it doesn't appear to fix the problem of asset requests checking for updated classes. In fact it seems to make it worse, loading a simple asset takes ~2 seconds with rails_dev_boost. Am I doing something wrong or is 4.1 just not supported (yet)?
The text was updated successfully, but these errors were encountered: