If the app was previously running 1.2.6, then the easiest thing to do
would be to get it running under 1.2.6 before you start worrying about
migrating it to rails 2. (you can specify which gem version to load in
environment.rb, assuming rails isn't frozen into vendor/rails.
> Thanks, Fred.
> I'm on Dreamhost. From my read of comments at:
> It sounds like I could manually edit my environment.rb to force an
> older rails version, but I'm not sure how. This helpful page:
> http://wiki.rubyonrails.org/rails/pages/GemRails describes how to
> force individual gems versions.
That page is a zillion years old. The way you do this these days is
that environment.rb should have something like
RAILS_GEM_VERSION = '2.0.2' unless defined? RAILS_GEM_VERSION
in it. Replace 2.0.2 with the desired version.
> (In case you haven't pieced it together, I have a related issue which
> is that I'm missing any call to Rails::Initializer in this app)
> Ignore this for now. Or don't. I have a basic app, the output of
> "rails myapp" and I can see where it does have those lines:
> ./myapp/config/boot.rb: defined? Rails::Initializer
> ./myapp/config/boot.rb: Rails::Initializer.run(:set_load_path)
> ./myapp/config/environment.rb:Rails::Initializer.run do |config|
Is the app you're working on really really old? (ie from before
Rails::Initializer & friends were created)