I was told that I needed to install Rails2 to work on a project. (Note: Rails3 was released some time ago.)

The documentation was all updated for Rails3. This is good, if you're wanting to use Rails3. It turns out this is very bad if you want to use Rails2.

I started with the getting started tutorial. The first problem I encountered is in the "assumptions" section. I installed Ruby 1.9.2. I then went to install RubyGems. It refused to install. So I tweeted. I actually got help (something I wasn't explicitly looking for) from @luislavena, who actually works on making Ruby more Windows friendly. One of the blog posts in his wiki took about 5 words to note that RubyGems is bundled with Ruby 1.9.x.

Well, problem #1 solved. I skipped the second point of the getting started tutorial purely for its irrelevance to the task at hand, and its length. I ran gem install rails -v 2.8.7, which worked fine. The next step in the tutorial said rails new blog would create a project called "blog". Wrong. It created a project called "new." Turns out this syntax changed between rails2 and rails3.

The next rails command was bundle install. This gave an executable not found error. "bundle" is a separate gem, and was not included by default. This took some Bing-fu to figure out.

And finally, I hit step four, to see if it actually worked. It didn't. rails server did not exist in rails2. The rails2 equivalent was ruby script/server.

At this point, I can only pray that the actual RoR code is compatible across Rails versions...