I'm not entirely sure what would be causing this, but you can always use Sass::Plugin.update_stylesheets in your deploy script to force Sass to update.
On Mon, Jun 1, 2009 at 10:33 AM, Billy Gray <[email protected]> wrote: > > Guys and Gals, > > We've recently started using passenger in our QA and production > environments (still on mongrel locally for development), for a Rails > 2.3.2 app using Haml 2.0.9. When I fire this guy up in production, the > HAML templates were getting processed correctly, but SASS wasn't > happening. > > If I went to stylesheets/application.css I'd get bad route exception, > despite having application.sass in public/stylesheets/sass. > > This seemed to have been fixed last week when I dropped this into > environment.rb: > > config.gem 'haml' > > But I just pushed another round of code up, restarted passenger, and > I'm back to the bad route issue. Is there something particular we need > to be doing to get sass working under passenger? > > I saw some similar issues on this list and the passenger list, but > nothing quite matching the CSS/Sass problem, or any kind of solution. > > Curious how others are handling this! > > Cheers, > Billy > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
