On Tuesday 12 February 2008 13:17:47 Greg Fitzgerald wrote: > Little run down on my setup. I am coding my software locally and > importing into a git repo. I decided since I will be moving my css files > over to sass now I no longer want to keep them in the git repository > thinking they would be generated by sass first hit to the site. Plus if > I did keep them in repository I would have to go delete them off the > server if I changed anything in sass? Really not sure if that last bit > is correct. Maybe sass knows its out of date and regenerates the css? > > Anyways, I have nginx as my server connecting to a mongrel cluster. > Everything was working fine till I deployed my app now I have no css > files. It appears that sass is not generating the css files for me on my > production server. For some reason I got it in my head that it had to do > with :cache => true for my stylesheets, turned that off no luck. I'm not > seeing any errors in my production log other than no route to said css > files which is normal considering sass has not generated them. > > Some ideas on what could be causing this. I know haml is working because > the site has been using haml for a month now I just never got to using > sass till now. Feel free to correct me in my thoughts on how sass is > working or how I'm doing business with my git setup.
Hello, Greg I'm using simple hack to avoid this issue Sass::Plugin.options[:always_check] = true somewhere in config/initializers -- Eugene --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Haml" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/haml?hl=en -~----------~----~----~----~------~----~------~--~---
