Skip to content
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

Require sprockets in application.rb #384

Merged
merged 1 commit into from Sep 13, 2011
Merged

Require sprockets in application.rb #384

merged 1 commit into from Sep 13, 2011

Conversation

jgaskins
Copy link
Contributor

This will fix the issue @steveklabnik has been mentioning on Twitter with the asset pipeline not working properly.

@steveklabnik
Copy link
Contributor

That'd be sweeeet. Ill check this out when I'm not in this meeting. :)

Thanks so much.
On Sep 13, 2011 7:13 PM, "Jamie Gaskins" <
reply@reply.github.com>
wrote:

This will fix the issue @steveklabnik has been mentioning on Twitter with
the asset pipeline not working properly.

You can merge this Pull Request by running:

git pull https://github.com/jgaskins/rstat.us development

Or you can view, comment on it, or merge it online at:

#384

-- Commit Summary --

  • Require sprockets in application.rb

-- File Changes --

M config/application.rb (1)

-- Patch Links --

https://github.com/hotsh/rstat.us/pull/384.patch
https://github.com/hotsh/rstat.us/pull/384.diff

Reply to this email directly or view it on GitHub:
#384

@jgaskins
Copy link
Contributor Author

I had the exact same issue in my own project last week (also an upgrade). Baffled me for 2 days straight. I ended up figuring the damn thing out when I created a separate Rails 3.1 app from scratch and compared the various config files.

@steveklabnik steveklabnik merged commit 0970835 into hotsh:development Sep 13, 2011
@steveklabnik
Copy link
Contributor

Totally worked. I'll love you forever.

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.

None yet

2 participants