aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSteve Klabnik <steve@steveklabnik.com>2012-11-09 15:13:18 +0100
committerSteve Klabnik <steve@steveklabnik.com>2012-11-09 15:13:18 +0100
commite85cb2d3bb95ae5cf2f524ffc6828fd40723c83e (patch)
tree954255559854a513bc6e9cfb9de72113aa78275c
parent4d61d1f8f58f7db6f2bffee52cc2debc66ba7657 (diff)
downloadrails-e85cb2d3bb95ae5cf2f524ffc6828fd40723c83e.tar.gz
rails-e85cb2d3bb95ae5cf2f524ffc6828fd40723c83e.tar.bz2
rails-e85cb2d3bb95ae5cf2f524ffc6828fd40723c83e.zip
Add note about asset pipeline and CDNs.
Fixes #2468.
-rw-r--r--guides/source/asset_pipeline.md11
1 files changed, 11 insertions, 0 deletions
diff --git a/guides/source/asset_pipeline.md b/guides/source/asset_pipeline.md
index 0540516a74..0c5e65ae67 100644
--- a/guides/source/asset_pipeline.md
+++ b/guides/source/asset_pipeline.md
@@ -575,6 +575,17 @@ group :production do
end
```
+### CDNs
+
+If your assets are being served by a CDN, ensure they don't stick around in
+your cache forever. This can cause problems. If you use
+`config.action_controller.perform_caching = true`, Rack::Cache will use
+`Rails.cache` to store assets. This can cause your cache to fill up quickly.
+
+Every CDN is different, so evaluate how your CDN handles caching and make sure
+that it plays nicely with the pipeline; you may find quirks related to your
+specific set up.
+
Customizing the Pipeline
------------------------