Presuming you're using Bundler, you could possibly move Sass into the development group, and do:
heroku config:add BUNDLE_WITHOUT=development:test Just a thought... :brad On Sat, Dec 18, 2010 at 4:53 PM, Andrew Burleson <[email protected]>wrote: > I have a site that runs on Heroku... I'm sure you've heard the story. > > So I made a simple rake task that compiles everything, and I can run > this before deploying to Heroku so all my CSS is up-to-date and > checked in as static assets. > > This is working fine, and I haven't encountered a problem yet, but > I've been warned that if, for some reason, Sass tries to update a file > for me (while running on Heroku) that it's going to throw an > exception. The easy fix for this would be to just tell Sass not to > autocompile in Production, but I haven't been able to find how to do > that. > > Any pointers? Thanks! > > -- > 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] <haml%[email protected]>. > For more options, visit this group at > http://groups.google.com/group/haml?hl=en. > > -- Bradley Grzesiak co-founder, bendyworks llc http://bendyworks.com/ -- 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.
