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

Can we still use the asset pipeline? #50

Closed
lukebooth opened this Issue Nov 26, 2012 · 1 comment

Comments

Projects
None yet
2 participants
@lukebooth

lukebooth commented Nov 26, 2012

I want to use ember.js with rails and rails-api looks promising for this. All my views will be rendered with ember and aren't needed in rails. I threw your gem in my app and the asset pipeline isn't being compiled anymore; it is still enabled in my application.rb though.

Is there a way to still use the asset pipeline with this gem?

@steveklabnik

This comment has been minimized.

Show comment
Hide comment
@steveklabnik

steveklabnik Nov 26, 2012

Contributor

You can 'use the asset pipeline,' like you said, it's not removed. Just mkdir /app/assets/{javascripts,stylesheets,images} and you're good to go.

That said, upon the next release, we will be generating those directories, because, as you say, ember will obviously want to use it. Check out 1364ad1. We're also considering replacing sprockets with something like rake-pipeline.

Contributor

steveklabnik commented Nov 26, 2012

You can 'use the asset pipeline,' like you said, it's not removed. Just mkdir /app/assets/{javascripts,stylesheets,images} and you're good to go.

That said, upon the next release, we will be generating those directories, because, as you say, ember will obviously want to use it. Check out 1364ad1. We're also considering replacing sprockets with something like rake-pipeline.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment