Phusion Passenger 5.0.1 released

[Hongli Lai]

Please read https://blog.phusion.nl/2015/03/04/phusion-passenger-5-0-1-released/
for the announcement.

--
Phusion | Web Application deployment, scaling, and monitoring solutions

Web: http://www.phusion.nl/
E-mail: in...@phusion.nl
Chamber of commerce no: 08173483 (The Netherlands)

[Greg]

Hi, it is not clear if version 5 still supports app reloading via "touch tmp/restart.txt". A new way is described but does the old way (restart.txt) still work?

[Hongli Lai]

Yes, the old way still works, but with a default timeout of 10
seconds. So by default, there is a max 10 seconds delay before
Passenger notices that you have touched restart.txt.

You can revert to the old behavior by setting PassengerStatThrottleRate to 0.

On Thu, Mar 5, 2015 at 11:34 AM, Greg <gdan...@gmail.com> wrote:
> Hi, it is not clear if version 5 still supports app reloading via "touch
> tmp/restart.txt". A new way is described but does the old way (restart.txt)

> still works?

[John Lemp]

Do the apt repos still have version 4.0.59 anywhere? It seems that existing repo now only has version 5 and the breaking changes around the nginx passenger_temp_dir directive is preventing nginx from starting and I would like to install 4.x until I can prepare for 5.x.

Thanks,

John

[Hongli Lai]

The 4.0.59 files are still in the repository. However, due to the
limitations in the APT repository software we use (reprepro), the APT
indices do not list these old versions. You should download the .deb
files directly from the server:
https://oss-binaries.phusionpassenger.com/apt/passenger/

But if you ask me, it's easier to just fix your Nginx config file to
make it work with Passenger 5. There are very few breaking changes,
and the they're easy to fix. passenger_temp_dir has been renamed to
two different config options, as documented here:
https://blog.phusion.nl/2015/03/04/phusion-passenger-5-0-1-released/#upgrade_notes

[John Lemp]

I am working on the fix but the install and deploy process is automated with Chef and used in AWS launch configs for automatic failover and auto scaling policies. I didn't anticipate a breaking change in the existing repository channel from the existing version not being available.

[Cody Robbins]

Yeah, removing availability of 4.0.59 is seriously bad. I also have an entire set up configured by Chef on AWS that this completely breaks.

Whether or not it seems easy to upgrade to 5, it has breaking changes and the unavailability of 4.0.59 now forces people to upgrade.

[Peter Arentsen]

A very bad choice to even allow it to upgrade on the same named package with breaking changes.

We had to revert manually on our servers the upgrade to 4.0.59 from the apt cache because everything below rails 3 broke.

Even rails 2.3 didn't work even though the release notes say it should still work.

It normally got installed automaticly because of security fixes.

[Hongli Lai]

I hear you. I will setup a repository specifically for 4.x in the coming week.

Sent from my Android phone.

[Hongli Lai]

The Passenger 4 repository is now available:
https://blog.phusion.nl/2015/03/08/passenger-4-apt-repository-now-available/