Rails 3.1 sass - WEBrick restart required to see style changes

Rails
1

Title pretty much says it all.

Just converted an app to 3.1 using the asset pipeline and I think this
is
the last hangup I’ve got.

I haven’t seen anything about needing to run a watcher or anything, but
right now the only way I can see style changes is to stop/start WEBrick.

Help?

2

Happens to me to.

Sometimes it works for me, sometimes it does not. Same goes for
coffeescript. Perfectly working barista install in 3.0, but on 3.1 with
the
asset pipeline it sporadically does not compile. Are you per any chance
using compass too, maybe that’s the culprit?

3

Yep I am using Compass too. Thanks for the pointer in that direction,
I’m
looking at their CLI docs now for some “unwatch” command or something.

Did you have a bad experience with Compass/3.1?

4

I got it to work after some tinkering on a test project, but I am not
sure
how to proceed. I am going into public beta with a major project soon
and I
would like to start with Rails 3.1 to reduce migration risk later on but
the
fact that sprockets and compass don’t work well together is a real
bummer. I
am probably waiting for a month or so till I am trying this again.
Very disappointing.

On Sun, Jun 19, 2011 at 10:14 AM, Chris Braddock

5

Its possibly all working now (a little more time will tell I suppose),
but I
can verify at least that I just watched some changes apply without
restarting WEBrick. The change I added was this:

@import “**/*”;

to app/assets/application.css.scss per:

I’m a little confused as to what’s happening behind the scenes at this
point
though … do I need both the line I just added AND the line I thought
was
previously importing that code? i.e.

/*
*= require_directory ./default
*/

I might just stop at being happy that its working – at least until the
code
releases involved get a little more stable.

6

On Sun, Jun 19, 2011 at 9:36 AM, Chris Braddock
[email protected]wrote:

Chris and others, I would highly recommend filing ticket for this issue
if
one doesn’t already exist so that it’s properly addressed by the Rails
core
team.

Good luck,

-Conrad

7

Thanks for the info. I guess I’ll try removing Compass altogether 1st
and
see what happens, then reintroduce it, and see again. I’ll post back
here
if there’s anything interesting to tell.