On 3/20/06, Hogan, Brian P. [email protected] wrote:
Yes you would run two WEBrick servers on different ports. I guess I’ve
never run into a situation on my local machine where that’s been an
issue; if I need that, then I deploy to staging.
Whatever works for you!
Yeah, using separate ports will be an acceptable solution. If there’s
some weirdness when it moves from development to staging then I’ll
deal with it then. I think it’ll be fine though.
As for your caching… I’m baffled. Perhaps you have the environment set
to production in the environment file?
The only thing uncommented out in environment.rb is:
require File.join(File.dirname(FILE), ‘boot’)
Rails::Initializer.run do |config|
end
That’s it. And here is what’s uncommented in the environment files:
development.rb
config.cache_classes = false
config.whiny_nils = true
config.breakpoint_server = true
config.action_controller.consider_all_requests_local = true
config.action_controller.perform_caching = false
config.action_mailer.raise_delivery_errors = false
test.rb
(all the same as above except the last line)
config.action_mailer.delivery_method = :test
production.rb
config.cache_classes = false
config.action_controller.consider_all_requests_local = false
config.action_controller.perform_caching = false
And that’s it. But it still insists on caching the class when I
change it. Here’s the kicker, I can change the controller all day
long and it doesn’t cache it. So, for example, my “blah” method just
returns a static string, I then set @page_title to what it returns
before it’s handed off to my layout, partials and view. If I change
what article.rb returns it doesn’t change (appears to be cached), BUT
if I change the controller and just append “BRENT” to what it returns,
THAT change appears but the text that prepends that is still the old
cached string from the blah call.
It’s driving me nuts. I’m definitely NOT going to restart the server
after every little change to a class.
Thanks,