Have you tried deleting the CSS files? That should cause Sass to regenerate them. I often have to do this when I redeploy new Sass. Lame I know.
-- John Long http://wiseheartdesign.com http://recursivecreative.com On Mon, Jul 19, 2010 at 12:56 PM, Joel Oliveira <joel.olive...@gmail.com> wrote: > Hi everyone - > Just deployed a new site to production and for some reason my changes to > sass files aren't being reflected in the main "compiled" css file. > Standard stack on production, nginx with ree + passenger. > Things I've done to remedy - > 1 - touch tmp/restart.txt > 2 - restarted nginx > 3 - I thought that maybe it was a permissions thing so I gave the compiled > stylesheet write permissions for www-data > None of those three did the trick. Is there anything else I should try? > I suppose I could run sass explicitly from its location in vendor but that > would feel a bit hack-y, no? > Thanks everyone! > - Joel