Dreamhost Rails upgrade troubles

rubyonrails-talk
1

I am running a Ruby on Rails site in a shared hosting environment on Dreamhost (using Passenger), and recently they upgraded from Rails 2.3.x to Rails 3. It looks like this broke the site.

Here is the URL: http://www.mycondonetwork.com

You can see the Passenger error I'm getting.

My ideal situation would be to somehow freeze Rails to use 2.3.3 (last known version that worked... I don't monitor this site that often).

I would rather not upgrade the site to use Rails 3 (unless it's easy).

Any help would be appreciated.

2

Brian Wolk wrote in post #970105:

I am running a Ruby on Rails site in a shared hosting environment on Dreamhost (using Passenger), and recently they upgraded from Rails 2.3.x to Rails 3. It looks like this broke the site.

Here is the URL: http://www.mycondonetwork.com

You can see the Passenger error I'm getting.

My ideal situation would be to somehow freeze Rails to use 2.3.3 (last known version that worked... I don't monitor this site that often).

So do that! What's stopping you?

I would rather not upgrade the site to use Rails 3 (unless it's easy).

You probably should upgrade eventually.

Any help would be appreciated.

Best,

3

I guess what I'm asking is how do I freeze the Rails version to 2.3.3 (actually make that 2.3.5)?

I've already followed the steps here: http://wiki.rubyonrails.org/getting-started/upgrading

..and gem installed 2.3.5, and then modified environment.rb, setting RAILS_GEM_VERSION = '2.3.5'.

Then I ran rake:rails update but it didn't seem to do anything, and I'm still getting the same error as before.

Did I miss something?

4

Please quote when replying.

Brian Wolk wrote in post #970115:

I guess what I'm asking is how do I freeze the Rails version to 2.3.3 (actually make that 2.3.5)?

Do you want to? My understanding is that for security reasons, you should probably be using 2.3.10.

I've already followed the steps here: http://wiki.rubyonrails.org/getting-started/upgrading

..and gem installed 2.3.5, and then modified environment.rb, setting RAILS_GEM_VERSION = '2.3.5'.

Right. That will select Rails 2.3.5 if it's installed on the host. It will not magically run 2.3.5 if Dreamhost removed it (which I don't know).

Then I ran rake:rails update but it didn't seem to do anything, and I'm still getting the same error as before.

Well, the error looks like it's coming from an improper installation of ActiveSupport.

Did I miss something?

You missed the actual freezing of the Rails gems into your project. There's a Rake task for that.

Best,

5

Try this (found on Google):

rake rails:freeze:edge RELEASE=2.3.5

Walter

6

Check whether they have also upgraded ruby to 1.9. If you have not got 1.8.7 available then I think you will not be able to run rails 2.3. Unless others can correct me...

Colin

7

Colin Law wrote in post #970123:

known version that worked... I don't monitor this site that often).

Check whether they have also upgraded ruby to 1.9. If you have not got 1.8.7 available then I think you will not be able to run rails 2.3. Unless others can correct me...

Rails 2.3 works with Ruby 1.9. Certain gems may not, though.

Colin

Best,

8

Well I am surprised, I certainly had it in my head that rails 2.3.x was not happy with ruby 1.9.2. After some googling however I have to admit that I cannot find any evidence to back that up so I stand corrected. Maybe I was confused by issues around 1.9.1 and rails. Sorry for the noise.

Colin

9

Thanks for the replies, everyone.

I tried what Water suggested:

$ rake rails:freeze:edge RELEASE=2.3.5

..and I get this:

(in /home/<username>/website) cd vendor Downloading Rails from http://dev.rubyonrails.org/archives/rails_2.3.5.zip rake aborted! Connection reset by peer

If I manually navigate to that URL, I see that it no longer exists (even dev.rubyonrails.org is no longer available).

Does anyone know off hand if this domain been moved to another url? If so, can I update a domain variable somewhere to point to the new url?

10

I believe rake is just driving gem at that point, so you might want to try the extended gem syntax for installing a particular version of a particular gem from a particular server. (man gem in a terminal for the entire syntax) See if there's a copy on github's gem server, or rubyforge, or one of the other best-guess places.

Walter

11

I don't think you want the edge.

If you want to freeze to the version of rails that the app is currently using then just rake rails:freeze:gems should do it I think.

Colin