From f713bf6e38147f36a77d0372b1908300b8d0bdc4 Mon Sep 17 00:00:00 2001 From: Andrey Vakarev Date: Sat, 16 Jun 2012 02:32:59 +0300 Subject: [PATCH] Extend assets cache store section in Assets Pipeline Guide [ci skip] --- guides/source/asset_pipeline.textile | 21 ++++++++++++++++++--- 1 file changed, 18 insertions(+), 3 deletions(-) diff --git a/guides/source/asset_pipeline.textile b/guides/source/asset_pipeline.textile index edc6735a19387..6df23e55dda7b 100644 --- a/guides/source/asset_pipeline.textile +++ b/guides/source/asset_pipeline.textile @@ -649,11 +649,26 @@ Apache and nginx support this option, which can be enabled in config/environ WARNING: If you are upgrading an existing application and intend to use this option, take care to paste this configuration option only into +production.rb+ and any other environments you define with production behavior (not +application.rb+). -h3. How Caching Works +h3. Assets Cache Store -Sprockets uses the default Rails cache store to cache assets in development and production. +If you will not configure assets cache store, your application's cache store will be used to cache assets in development and production. -TODO: Add more about changing the default store. +You always can access your application's cache by calling +Rails.cache+. + +Default assets cache store can be changed to something else, like memory store: + + +config.assets.cache_store = :memory_store + + +All the assets cache store parameters should be passed in the same way like for application's cache store. + + +config.assets.cache_store = :memory_store, { :size => 32.megabytes } + + +Any appropriate application cache store adapter can be used for assets cache store. +You can read more about application's cache stores and their options in the "Caching with Rails Guide":./caching_with_rails.html#cache-stores. h3. Adding Assets to Your Gems