Commit
…debugging, add config.assets.compile and config.assets.digest
- Loading branch information
There are no files selected for viewing
3 comments
on commit f443f9c
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The assets:precompile
rake task will need to be modified for the case where config.assets.digest
is set to false in production.
I am also seeing some unexpected "X isn't precompiled" errors when config.assets.compile
is set to false. Not sure whether there's an issue there or not -- I will investigate further tomorrow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like I'm not the only person experiencing "X isn't precompiled" errors: #2763.
Perhaps a solution is to explicitly set config.assets.compile
to true within the rake task.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@spohlenz: Yes, looks like an issue when config.assets.digest
and config.assets.compile
both are false.
Thinking more about this, raising an error seems like a fairly drastic response to a missing asset. I'd prefer to simply have the asset 404 rather than have the entire page error out (especially given as this is likely to crop up only on deploying to production).
Can we replace
raise AssetNotPrecompiledError
withreturn logical_path
? I've also noticed that we probably shouldn't be mounting the assets in the railtie ifconfig.assets.compile
is false.What do you think @guilleiguaran, @spastorino?