-
Notifications
You must be signed in to change notification settings - Fork 346
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Have to set config.assets.compile = true in Rails 4.0.3 to make asset_sync paths correct #255
Comments
I'm experiencing this issue as well. |
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... |
See also #257 |
Any development on this issue? I'm encountering the same issue after upgrading a Rails 3.2 app to Rails 4.2. |
+1 |
Maybe you should set |
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?
The text was updated successfully, but these errors were encountered: