On Mon, Aug 16, 2010 at 7:10 PM, Tomasz Romanowski <[email protected]> wrote: > Yep, that's it, thanks. Makes me wonder how I can control which classes > should be reloaded. I'm trying to make something off of development.rb > and production.rb.
Rails comes with 3 development environments already ready to go, look database.yml. In development and testing, all classes are always reloaded. In production they are always cached. How is this not exactly what you want? :) -- Greg Donald destiney.com | gregdonald.com -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
