Monday, January 6, 2014

[Rails] Re: Sass caching issue in development.

Mathias,

Did you ever find a solution? A few people at my work including myself also have the same issue.

Eric

On Thursday, November 14, 2013 12:46:50 AM UTC-7, Mathias Jean Johansen wrote:
Hi everyone,

Lately, I've had quite an annoying problem when I work with Sass in Rails. For reasons I cannot figure out, I need to kill the local Rails server instance, "rm -rf tmp/cache" and start the server again to see the changes I've made in app/assets/stylesheets. It obviously affects my productivity why I now seek your help.

Many answers on StackOverflow to similar questions suggest that I add config.assets.cache_store = :null_store and config.sass.cache = false to config/environments/development.rb, but unfortunately that does not help me solve my problem. Other answers suggest that I remove tmp/cache which works in my case, but the problem is that I have to do it every single time I change something in app/assets/stylesheets.

I run Ruby 1.9.3p448 (2013-06-27 revision 41675) [x86_64-darwin13.0.0] and Rails 3.2.15 on Mac OS 10.9.

I really hope that some of you might have a solution to my problem.

Kind regards,
Mathias Jean Johansen

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/311da3c6-81ce-4131-8602-73ad6b93dabc%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home


Real Estate