Thanks for the cast. One question. What happens if you're using the same layout for say the user's controller and the main page and you want to include only the application.js for the main page, but you want to add user.js for the user's page, but not admin.js (from an admin page for example). Thank you.

Thanks Caike! I have a few questions, would it make more sense to include the application js/css for global css and the locals where applicable for overrides or specific view requirements? also, you change those asset settings by mode so they only have to be setup one time depending on where you are deploying your code?

Whoa.. sorry for the super late reply. Yes, Chris. Using an application js/css for global stuff and then using specific ones where applicable is a strategy that I use a lot.

About This Screencast

The Rails Asset Pipeline is a powerful tool for managing an application's assets but it can be difficult to use at first. In this screencast we'll look at the basic concept behind the pipeline, how to organize manifest files, use sass-rails helpers and debug production assets locally.

You need to be an enrolled student in order to view this video and subscribe.