How to get SASS to work with Rails 3 on Heroku (without using any plugins)

#1

Post by aslamnd » Thu, Mar 31, 2011, 7:10 AM UTC

Using SASS in Heroku could be a little tricky. This post explains how to do it without using any 3rd party plugins.

How to get SASS to work with Rails 3 on Heroku (without using any plugins)
frontcube.com

Re: How to get SASS to work with Rails 3 on Heroku (without using any plugins)

#2

Post by wmwong » Thu, Mar 31, 2011, 8:07 AM UTC

There is documentation from Heroku on how to get Compass working without plugins. I tried it out before and it works nicely.

http://devcenter.heroku.com/articles/using-compass

Re: How to get SASS to work with Rails 3 on Heroku (without using any plugins)

#3

Post by SingAlong » Thu, Mar 31, 2011, 9:27 AM UTC

A simpler solution. Just add the following line to your production config:

Compass.configuration.sass_options={:never_update=>true}

That's it :) Now when you update the sass files you just have to start the rails dev server once and git commit and push.

Re: How to get SASS to work with Rails 3 on Heroku (without using any plugins)

#4

Post by patio11 » Thu, Mar 31, 2011, 11:36 AM UTC

SingAlong wrote: post #3

A simpler solution. Just add the following line to your production config: Compass.configuration.sass_options={:never_update=>true} That's it :) Now when you update the sass files you just have to start the rails dev server once and git commit and push.

This is similar to solutions I've had to hack around for gems on heroku before, but just to play devil's advocate, one generally tries to avoid committing anything compiled to source control. Especially if you do that "you just have to..." step manually (instead of, e.g., through a post-commit hook), you're writing yourself technical debt, payable at a future date when the compiled output goes out of sync with the source and this causes a problem on the site not seen by the responsible developer. That is going to be a particularly hard problem to notice and debug, since CSS issues are practically immune to most forms of automated testing.

This will keep happening until you do it the right way. (If I sound like someone who has been burned by this...)

Re: How to get SASS to work with Rails 3 on Heroku (without using any plugins)

#5

Post by SingAlong » Thu, Mar 31, 2011, 12:30 PM UTC

patio11 wrote: post #4

SingAlong wrote: post #3

A simpler solution. Just add the following line to your production config: Compass.configuration.sass_options={:never_update=>true} That's it :) Now when you update the sass files you just have to start the rails dev server once and git commit and push.

This is similar to solutions I've had to hack around for gems on heroku before, but just to play devil's advocate, one generally tries to avoid committing anything compiled to source control. Especially if you do that "you just have to..." step manually (instead of, e.g., through a post-commit hook), you're writing yourself technical debt, payable at a future date when the compiled output goes out of sync with the so…

Hmm, I agree. I just realized that what I was doing was a bad hack. I'll change my practice.

Re: How to get SASS to work with Rails 3 on Heroku (without using any plugins)

#6

Post by aslamnd » Thu, Mar 31, 2011, 2:42 PM UTC

SingAlong wrote: post #5

patio11 wrote: post #4

Earlier quoted context omitted.

This is similar to solutions I've had to hack around for gems on heroku before, but just to play devil's advocate, one generally tries to avoid committing anything compiled to source control. Especially if you do that "you just have to..." step manually (instead of, e.g., through a post-commit hook), you're writing yourself technical debt, payable at a future date when the compiled output goes out of sync with the so…

Hmm, I agree. I just realized that what I was doing was a bad hack. I'll change my practice.

Glad you realized that! :-)