aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRyan Bigg <radarlistener@gmail.com>2011-06-28 08:15:41 +1000
committerRyan Bigg <radarlistener@gmail.com>2011-06-28 08:15:41 +1000
commit49bb053b171f0da95be5a1ab72e7d79aa65dda1b (patch)
tree2c11dc83cbd2636afb1975cedd68391ea9e8e2da
parent87a709846ec4bc1c3a101a7eec5e76d8b3db9c85 (diff)
downloadrails-49bb053b171f0da95be5a1ab72e7d79aa65dda1b.tar.gz
rails-49bb053b171f0da95be5a1ab72e7d79aa65dda1b.tar.bz2
rails-49bb053b171f0da95be5a1ab72e7d79aa65dda1b.zip
[asset pipeline] production assets covered later in the guide
-rw-r--r--railties/guides/source/asset_pipeline.textile2
1 files changed, 1 insertions, 1 deletions
diff --git a/railties/guides/source/asset_pipeline.textile b/railties/guides/source/asset_pipeline.textile
index 1fc422426a..94c6cb9fb7 100644
--- a/railties/guides/source/asset_pipeline.textile
+++ b/railties/guides/source/asset_pipeline.textile
@@ -49,7 +49,7 @@ To serve assets, we can use the same tags that we are generally familiar with:
<%= image_tag "rails.png" %>
</erb>
-Providing that assets are enabled within our application (+config.assets.enabled+ in your environment is set to +true+), this file will be served by Sprockets unless a file at +public/assets/rails.png+ exists, in which case that file will be served. Alternatively, a file with an MD5 hash after its name such as +public/assets/rails-af27b6a414e6da00003503148be9b409.png+ will also be picked up by Sprockets.
+Providing that assets are enabled within our application (+config.assets.enabled+ in your environment is set to +true+), this file will be served by Sprockets unless a file at +public/assets/rails.png+ exists, in which case that file will be served. Alternatively, a file with an MD5 hash after its name such as +public/assets/rails-af27b6a414e6da00003503148be9b409.png+ will also be picked up by Sprockets. How these hashes are generated is covered in the "Production Assets":#production_assets section later on in this guide.
Otherwise, Sprockets will look through the available paths until it finds a file that matches the name and then will serve it, first looking in the application's assets directories and then falling back to the various engines of the application.