Rail development environment without overloading change

Question

I deleted my development environment too quickly, and now I need to reboot my server every time I make a modification of views or controllers. This is a pain with a lot of small changes.

Now, even when my development.rb goes back to the original, views, the controllers need to restart to see the changes. I'm not sure what is going on.

Any help is really appreciated as it slows down my development.

thanks

Here is my environment.rb:

config.time_zone = 'Eastern Time (US & Canada)' config.cache_classes = true ENV['NLS_LANG']='american_america.AL32UTF8' config.i18n.default_locale = :en config.gem "authlogic" config.gem "matthuhiggins-foreigner", :lib => "foreigner" config.gem "memcache-client", :lib => "memcached" end require "will_paginate" require "RedCloth" require "authlogic" require 'memcached' 

My development.rb looks like this:

 config.cache_classes = true config.whiny_nils = true config.action_controller.consider_all_requests_local = true config.action_view.debug_rjs = true config.action_controller.perform_caching = false #cache only the models to avoid nil.include? errors in development mode. config.load_once_paths += %W( #{RAILS_ROOT}/app/models ) # Don't care if the mailer can't send config.action_mailer.raise_delivery_errors = false config.after_initialize do Workling::Remote.dispatcher = Workling::Remote::Runners::StarlingRunner.new end 

I tried to run mongrel_start using verbose mode, but this did not help:

 mongrel_rails start -B ** Starting Mongrel listening at 0.0.0.0:3000 ** Installing debugging prefixed filters. Look in log/mongrel_debug for the files. ** Starting Rails with development environment... ** Rails loaded. ** Loading any Rails specific GemPlugins ** Signals ready. TERM => stop. USR2 => restart. INT => stop (no restart). ** Rails signals registered. HUP => reload (without restart). It might not work well. ** Mongrel 1.1.5 available at 0.0.0.0:3000 

Answer 1

In my development .rb

 # In the development environment your application code is reloaded on # every request. This slows down response time but is perfect for development # since you don't have to restart the webserver when you make code changes. config.cache_classes = false 

So, I think you should do it false