andreasbittner
commented
10 years ago @LimeBlast I ran into the same problem while working with a vagrant shared folder to a windows host. Have you found a workaround to get it to work?
Closed LimeBlast closed 10 years ago
andreasbittner
commented
10 years ago @LimeBlast I ran into the same problem while working with a vagrant shared folder to a windows host. Have you found a workaround to get it to work?
LimeBlast
commented
10 years ago @abnoreality Alas, not yet. As I don't need to do any front end work on this for a couple of months, I've simply disabled sass generation for the moment.
I'm giving some serious though to jumping ship and going over to Grunt...
andreasbittner
commented
10 years ago @LimeBlast I now moved over to generating on the host system through the mounted drive. That works at the moment, but I still hope for a real solution to this.
Have the same problem in another project with Grunt using Compass. No avoiding the problem, it seems.
LimeBlast
commented
10 years ago If the author of this plugin added support for :cache_path (possibly with a little effort as just forwarding the setting onto sass - although nothing nothing about Ruby, I'd not want to suggest that it's 'easy'), it would fix it.
hawx
commented
10 years ago Finally got round to adding this (v1.4.0). You can now just pass any sass option in, so setting :cache_location like you had in that example right at the top now works.
LimeBlast
commented
10 years ago Thank you @hawx, that is awesome. I'll give it a try as soon as I'm able to :)
LimeBlast
commented
10 years ago Yup, this works perfectly, thank you again :)
I'm running guard-sass (via https://github.com/JeffreyWay/Laravel-Guard) inside a Vagrant virtual machine.
Upon running, I'm getting the error message complaining that the cache file was busy.
After a bit of research, I've found that this is possibly due to the
.sass-cachefolder being a vagrant-shared folder (http://stackoverflow.com/a/19312073/1049688) and that if I use the:cache_pathsetting, I can set this to be outside the shared folder (hopefully solving my problem).As such, I've tried setting this using the following line in my Guardfile:
But it doesn't appear to work, as I'm still getting the same error message.
So, long story short (too late), would it be possible for
:cache_pathto be supported by guard-sass? Thank you(here is the error message)