Skip to content
Browse files

Mention what cache_classes defaults to in all three default environments

  • Loading branch information...
1 parent 2683773 commit 8b114bec061d83352312d5710689ace4557443ab @radar radar committed Nov 26, 2010
Showing with 2 additions and 2 deletions.
  1. +2 −2 railties/guides/source/configuring.textile
View
4 railties/guides/source/configuring.textile
@@ -32,14 +32,14 @@ In general, the work of configuring Rails means configuring the components of Ra
This is a setting for Rails itself. If you want to pass settings to individual Rails components, you can do so via the same +config+ object:
<ruby>
-config.active_record.timestamped_migrations = false
+ config.active_record.timestamped_migrations = false
</ruby>
Rails will use that particular setting to configure Active Record.
h4. Rails General Configuration
-* +config.cache_classes+ controls whether or not application classes should be reloaded on each request.
+* +config.cache_classes+ controls whether or not application classes should be reloaded on each request. Defaults to _true_ in development, _false_ in test and production.
* +config.cache_store+ configures which cache store to use for Rails caching. Options include +:memory_store+, +:file_store+, +:mem_cache_store+ or the name of your own custom class.

0 comments on commit 8b114be

Please sign in to comment.
Something went wrong with that request. Please try again.