Have to set config.assets.compile = true in Rails 4.0.3 to make asset_sync paths correct

[i0n]

Hi there.

I have found that in order to make the paths generated by asset_sync behave correctly in staging/production I have to define config.assets.compile = true in the relevant environment. If I don't do this then the domain ( in my case S3 ) is generated correctly, but the path remains the same as in development, i.e DOMAIN.com/stylesheets/application.css instead of DOMAIN.com/assets/application-RANDOM-HASH.css Is this a known issue?

[sidwood]

I'm experiencing this issue as well.

[steakchaser]

Seeing the same issue with Rails 4.2.0. Removing the asset_sync gem definitely resolves this; however, I've scoured the asset_sync source and can't find anything that I think would prevent Rails from including the digest in the asset URLs. I don't get it...

[steakchaser]

See also #257

[traviskroberts]

Any development on this issue?

I'm encountering the same issue after upgrading a Rails 3.2 app to Rails 4.2.

[aaronlifton]

+1

[PikachuEXE]

Maybe you should set
config.assets.digest = true?