diff options
author | Steve Klabnik <steve@steveklabnik.com> | 2012-11-09 15:19:40 +0100 |
---|---|---|
committer | Steve Klabnik <steve@steveklabnik.com> | 2012-11-09 15:19:40 +0100 |
commit | d2a0781b03eec21dddbd228e857897955283a81b (patch) | |
tree | 0493cdada5ec4e4dd4bdc401bbefeb7e54d2bdc9 | |
parent | e85cb2d3bb95ae5cf2f524ffc6828fd40723c83e (diff) | |
download | rails-d2a0781b03eec21dddbd228e857897955283a81b.tar.gz rails-d2a0781b03eec21dddbd228e857897955283a81b.tar.bz2 rails-d2a0781b03eec21dddbd228e857897955283a81b.zip |
Further explain the CDN and caching situation.
-rw-r--r-- | guides/source/asset_pipeline.md | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/guides/source/asset_pipeline.md b/guides/source/asset_pipeline.md index 0c5e65ae67..a79a6f10ae 100644 --- a/guides/source/asset_pipeline.md +++ b/guides/source/asset_pipeline.md @@ -582,9 +582,10 @@ 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. +Every cache 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, you may not. The defaults nginx uses, for example, +should give you no problems when used as an HTTP cache. Customizing the Pipeline ------------------------ |