From 07d346646f61dbf0ef020eefc4dc11e140b55baf Mon Sep 17 00:00:00 2001
From: Sam Oliver <sam@samoliver.com>
Date: Mon, 11 Jun 2012 23:29:59 +0100
Subject: Fix cache_store configuration example

---
 guides/source/caching_with_rails.textile | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'guides/source/caching_with_rails.textile')

diff --git a/guides/source/caching_with_rails.textile b/guides/source/caching_with_rails.textile
index 34a100cd3a..3ee36ae971 100644
--- a/guides/source/caching_with_rails.textile
+++ b/guides/source/caching_with_rails.textile
@@ -332,7 +332,7 @@ h4. ActiveSupport::Cache::MemoryStore
 This cache store keeps entries in memory in the same Ruby process. The cache store has a bounded size specified by the +:size+ options to the initializer (default is 32Mb). When the cache exceeds the allotted size, a cleanup will occur and the least recently used entries will be removed.
 
 <ruby>
-config.cache_store = :memory_store, :size => 64.megabytes
+config.cache_store = :memory_store, { :size => 64.megabytes }
 </ruby>
 
 If you're running multiple Ruby on Rails server processes (which is the case if you're using mongrel_cluster or Phusion Passenger), then your Rails server process instances won't be able to share cache data with each other. This cache store is not appropriate for large application deployments, but can work well for small, low traffic sites with only a couple of server processes or for development and test environments.
-- 
cgit v1.2.3

