This project is archived and is in readonly mode.
cache_classes should be true by default
Reported by Damian Janowski | July 17th, 2008 @ 06:24 PM
Rails is assuming a "development mode"-like behavior. It seems that this is actually the exception -- ie not more than a "goodie" for developing.
This should not affect anybody in a bad way. Worst case scenario is that this will actually fix things on misconfigured servers (or in cases where you define your custom environment but don't have a config/environments/custom.rb -- by default Rails should assume that is not another development environment).
Comments and changes to this ticket
-
-
-
Jeremy Kemper July 30th, 2008 @ 09:57 AM
- Assigned user set to “josh”
- State changed from “new” to “open”
- Milestone cleared.
-
josh July 31st, 2008 @ 07:31 PM
Fair enough since "config.cache_classes = false" is the default for everyone's generated development environments.
-
Repository July 31st, 2008 @ 07:43 PM
- State changed from “open” to “resolved”
(from [030d5854adcf35e6620d667a93a922f5d91725d8]) Turn cache_classes on by default [#645 state:resolved]
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
People watching this ticket
Damian Janowski
Jeremy Kemper
José Valim
josh
Repository
Attachments
Referenced by
-
637
Issue a warning when running production mode with cache_classes turned off
Fair enough. It looks like the default behavior for a mi...