Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Updated guides with proposed asset pipeline changes #7767

Closed
wants to merge 1 commit into
from

Conversation

Projects
None yet
5 participants
Contributor

ndbroadbent commented Sep 27, 2012

There are the changes to the guides that correspond with pull request #21 on sprockets-rails.

Member

steveklabnik commented Sep 27, 2012

Don't forget about docrails in the future. But 👍

guides/source/asset_pipeline.md
```
The default location for the manifest is the root of the location specified in `config.assets.prefix` ('/assets' by default).
NOTE: If there are missing precompiled files in production you will get an `Sprockets::Helpers::RailsHelper::AssetPaths::AssetNotPrecompiledError` exception indicating the name of the missing file(s).
+#### Only recompile changed assets
+
+The asset pipeline will now only recompile assets that have changed. When deploying with Capistrano,
@steveklabnik

steveklabnik Sep 27, 2012

Member

This isn't really a bad thing, but why the \n here?

Owner

guilleiguaran commented Sep 28, 2012

We should wait first for the merge in sprockets, immediately later I will merge the PR in sprockets-rails and ping here to get this merged in Rails 😄

Member

schneems commented Sep 28, 2012

Thanks for your work on this 👍

Owner

guilleiguaran commented Oct 24, 2012

Closing there since looks like this isn't needed anymore in Rails.next :)

Thanks for your contribution 👍

Contributor

ndbroadbent commented Oct 24, 2012

No problem, I'm still happy that the turbo-sprockets-rails3 gem is
getting some users 😄

On Wednesday, 24 October 2012, Guillermo Iguaran wrote:

Closing there since looks like this isn't needed anymore in Rails.next :)

Thanks for your contribution [image: 👍]


Reply to this email directly or view it on GitHubhttps://github.com/rails/rails/pull/7767#issuecomment-9726708.

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