Gmail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
Upgrading to Rails 2.3.3 requires a Passenger upgrade?
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  5 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Cyrille  
View profile  
 More options Jun 26, 5:50 am
From: Cyrille <cbonne...@gmail.com>
Date: Fri, 26 Jun 2009 02:50:50 -0700 (PDT)
Local: Fri, Jun 26 2009 5:50 am
Subject: Upgrading to Rails 2.3.3 requires a Passenger upgrade?
Hi guys,

while reading about upgrading to Rails 2.3.2, I found this post:

http://www.caboo.se/articles/2009/5/9/rails-2-3-2-not-ready-for-prime...

The post itself is a bit too dismissive to my taste but the comments
make for an interesting read:

"Another showstopper is the fact that the Rack binding in Rails 2.3
loads entire file uploads into memory (instead of just storing a
reference to the file). This causes any app that processes uploads to
leak memory like there's no tomorrow"

Uh-oh.

And then later on, Hongli Lai (from Passenger) says: "That's partially
Phusion Passenger's fault. Upgrade to Phusion Passenger 2.2.2 and you
should be fine"

Well, it seems serious enough to warrant a double upgrade, but I am
not sure if the bug applies only if one uses Rack or it basically
applies to all??

If anyone can shed any light on this...

Cheers

Cyrille


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Tim Uckun  
View profile  
 More options Jun 26, 6:21 am
From: Tim Uckun <timuc...@gmail.com>
Date: Fri, 26 Jun 2009 22:21:04 +1200
Local: Fri, Jun 26 2009 6:21 am
Subject: Re: [WellRailed] Upgrading to Rails 2.3.3 requires a Passenger upgrade?

> Well, it seems serious enough to warrant a double upgrade, but I am
> not sure if the bug applies only if one uses Rack or it basically
> applies to all??

> If anyone can shed any light on this...

I upgraded to rails 2.3  I had already upgraded passenger before I
deployed my app.

The passenger upgrade went without a hitch. The rails upgrade required
a lot of code changes and upgrading a lot of plugins.

If you have gone through the trouble of upgrading rails I'd suggest
you upgrade passenger. It only takes a few seconds.


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Henry Maddocks  
View profile  
 More options Jun 26, 7:36 pm
From: Henry Maddocks <henry.maddo...@gmail.com>
Date: Sat, 27 Jun 2009 11:36:45 +1200
Local: Fri, Jun 26 2009 7:36 pm
Subject: Re: [WellRailed] Upgrading to Rails 2.3.3 requires a Passenger upgrade?
On 26/06/2009, at 9:50 PM, Cyrille <cbonne...@gmail.com> wrote:

I'm a bit out of touch with Rails at the mo…

> Well, it seems serious enough to warrant a double upgrade, but I am
> not sure if the bug applies only if one uses Rack or it basically
> applies to all??

Rails includes Rack these days doesn't it.

    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Nahum Wild  
View profile  
 More options Jun 26, 8:20 pm
From: Nahum Wild <nahum.w...@gmail.com>
Date: Fri, 26 Jun 2009 17:20:56 -0700 (PDT)
Local: Fri, Jun 26 2009 8:20 pm
Subject: Re: Upgrading to Rails 2.3.3 requires a Passenger upgrade?
yeah, and Rails Metail is worth looking at if you want to dodge
ActionController entirely.  We are about to use this for some high
volume actions to see if it makes any difference.

nahum.

On Jun 27, 11:36 am, Henry Maddocks <henry.maddo...@gmail.com> wrote:


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Will Bryant  
View profile  
 More options Jun 26, 9:01 pm
From: Will Bryant <will.bry...@gmail.com>
Date: Sat, 27 Jun 2009 13:01:48 +1200
Local: Fri, Jun 26 2009 9:01 pm
Subject: Re: [WellRailed] Upgrading to Rails 2.3.3 requires a Passenger upgrade?

On Fri, Jun 26, 2009 at 9:50 PM, Cyrille<cbonne...@gmail.com> wrote:
> And then later on, Hongli Lai (from Passenger) says: "That's partially
> Phusion Passenger's fault. Upgrade to Phusion Passenger 2.2.2 and you
> should be fine"

> Well, it seems serious enough to warrant a double upgrade, but I am
> not sure if the bug applies only if one uses Rack or it basically
> applies to all??

From 2.3 on, Rails uses Rack as the glue between Rails and the
webserver, so yes you will be using it.

You should upgrade Passenger when you upgrade to 2.3, because 2.3.3 at
least contains an updated version of Rack that is not fully compatible
with early versions of Passenger.

You should be able to upgrade Passenger while still on 2.2 if you're
nervous about upgrading both at the same time, but we tried out latest
REE + current Passenger + Rails 2.3.3 on a staging server  on thursday
and it tested out fine (no errors under load test etc.).


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google