Hello All, Many thanks for all your suggestions. I’m going to respond to all of them here. But first an embarrassing admission: When I did the same thing (I think) as I did earlier today, I got the expected result:
K:\_Projects\Ruby\_Rails_Apps\Rails_2.0_Demo>ruby script/server => Booting Mongrel (use 'script/server webrick' to force WEBrick) => Rails application starting on http://0.0.0.0:3000 => Call with -d to detach => Ctrl-C to shutdown server ** Starting Mongrel listening at 0.0.0.0:3000 ** Starting Rails with development environment... ** Rails loaded. ** Loading any Rails specific GemPlugins ** Signals ready. INT => stop (no restart). ** Mongrel 1.1.4 available at 0.0.0.0:3000 ** Use CTRL-C to stop. Sorry about the false alarm. However, I will gain from your suggestions. > Jeff: What does gem -v report? 1.0.1 > Conrad: Does your environment.rb reflect the version that's installed? RAILS_GEM_VERSION environment var is undefined environment.rb sets RAILS_GEM_VERSION = '2.0.2' rails –v => Rails 2.0.2 > Conrad: Run the “rake rails:update“ after you update environment.rb: Will do in the future. Thanks > Jason: I think that the function "require_gem" is now just "require" [snip] > line 28 of your config/boot.rb file. There’s no "require_gem" in config/boot.rb > To update to the new version of rails, run from your root: "rake > rails:update:configs" Nice to know, Thanks > Freezing apps that run on older versions: > http://support.tigertech.net/freeze-rails Nice to know, Thanks Again, thanks to all of you. You’re a great bunch! Best wishes, Richard --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
