Skip to content

Fix asset path munging to work in production env. #36

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

Merged
merged 1 commit into from
Mar 31, 2014

Conversation

johnthethird
Copy link
Contributor

Fix issue #31 by changing the initializer method. If you use after_initialize you can't then change the Sprockets path in production mode, as it becomes immutable.

Also, clean up the way the variant configs are initialized to fix issue #11.

I pulled out these specific changes from my server-rendering branch, so that they do not depend at all on server-rendering. I will rebase the server rendering changes on top of this so that they can be pulled in separately at the appropriate time.

@jtmalinowski
Copy link
Collaborator

This is great! It's getting merged as soon as @zpao will confirm your CLA.

jtmalinowski added a commit that referenced this pull request Mar 31, 2014
Fix asset path munging to work in production env.
@jtmalinowski jtmalinowski merged commit 46c3f70 into reactjs:master Mar 31, 2014
@vipulnsward
Copy link
Contributor

@johnthethird this seems to be causing #148 sporadically.
Can you point me where you picked up after => "sprockets.environment" config?
I am not able to track it down, to solve this.

@rmosolgo
Copy link
Member

I've also asked here: rails/sprockets-rails#227

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants