Fixing for sprockets 3 in production #19
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #18
A recent sprockets update changed some internals, which prevented this gem from working in production
This sprockets-rails issue describes the actual error that caused this: rails/sprockets-rails#237
In production, Rails.application.assets is only set if config.assets.compile is enabled (and it's not enabled by default in production)
This fix worked for my. I'm not sure if it works as a global solution, but I supose it should
One thing still remains in the codebase which I did not fix: the whole problematic code is surrounded by a
begin/rescue
, which completely silences any errors within it, which made it harder to spot the problem in the first place, and will make it harder to see if it's working againI'm not sure why it was originally put there, but I didn't remove it (although we probably should, it's a very big smell)