Phusion white papers Phusion overview

Phusion Passenger 2.0.1 (final) released

By Hongli Lai on June 25th, 2008

Phusion Passenger version 2.0.1 has been officially released. Not much has changed since 2.0 RC 2: only some documentation has been updated.

See the announcements for versions 2.0 RC 1 and 2.0 RC 2 for a full list of changes compared to version 1.0.x.

How do I upgrade to 2.0.1?

Please install it with the following command:

gem install passenger

Next, run:

passenger-install-apache2-module

Please don’t forget to copy & paste the Apache config snippet that the installer gives you.

Phusion Passenger

  • http://www.gizzar.com Ken

    Does this support the Edge Merb feature of background tasks?

    http://wiki.merbivore.com/pages/background-tasks

  • Thomas Balthazar

    Hello,

    I cannot find the 2.0.1 gem.

    Any clue?

    Best,
    Thomas.

  • Thomas Balthazar

    $gem install passenger try to install 1.9, the 2.0.1 is maybe not yet propagated.
    Solution :
    $curl -O http://files.rubyforge.vm.bytemark.co.uk/passenger/passenger-2.0.1.gem
    $sudo gem install passenger-2.0.1.gem
    $passenger-install-apache2-module

  • clouder

    I was wondering if setting PassengerRuby (as well as RailsRuby) to use ruby ee is of any benefit. I have done this for a couple of days and have yet to see any adverse effects (only visitor thus far is me though). I should probably do my own benchmarks when I get a chance, but I would like to hear your thoughts on this (or of any commenter for that matter). Finally real quickly I’d just like to say thanks for the awesomeness :D

  • clouder

    woops my bad, just found the deprecated section in the docs and saw that RailsRuby is deprecated. Thought they were two different things.

  • http://www.nytimes.com Aron Pilhofer

    Hey Guys,

    We love passenger. Only problem we’ve had is the max connection limit issue that I know other Ubuntu users have noted in 1.9.1, which does not appear in 1.0.5 (at least that I’ve experienced). Does 2.0.1 take care of that issue? Thanks again for a terrific piece of software.

  • http://stonean.com Andrew Stone

    Hey guys. First, thanks for passenger, it’s a great product. I do have one issue though: namespaced controllers. I have /users and /admin/users controllers. When I try to access /admin/users the view breaks due to an uninitialized instance variable: @users. The same code works fine under thin, mongrel and webrick so I’m assuming it’s a passenger issue. I’ve googled but haven’t found a solution. Please help, I would like to continue using passenger, but this is a deal breaker for me. :(

    I’m on the latest version: passenger 2.0.1.

  • Pingback: Phusion Passenger 2.0.1 Released: A Significant Upgrade

  • Pingback: Mc-Kenna.com » mod_rails / Phusion Passenger 2 goes gold

  • Paul

    Will there ever be a windows version of Passenger?

  • Pingback: Enlaces :ruby, :rails => “junio 2008″ | Javier Vidal Postigo

  • James

    can some help me, when i try to install the version 2.0.3 or even the 1.9.1, i get the following error :
    g++ -I.. -fPIC -g -DPASSENGER_DEBUG -DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -I/usr/include/apr-0 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -m32 -march=i386 -mtune=pentium4 -fasynchronous-unwind-tables -I/usr/include/httpd -D_REENTRANT -g -DPASSENGER_DEBUG -Wall -I/usr/local/include -c Hooks.cpp
    MessageChannel.h: In member function ‘int Passenger::MessageChannel::readFileDescriptor()’:
    MessageChannel.h:488: error: ‘’ is/uses anonymous type
    MessageChannel.h:488: error: trying to instantiate ‘template struct boost::is_integral’
    Hooks.cpp: In member function ‘boost::shared_ptr Hooks::receiveRequestBody(request_rec*)’:
    Hooks.cpp:520: warning: comparison between signed and unsigned integer expressions
    rake aborted!
    Command failed with status (1): [g++ -I.. -fPIC -g -DPASSENGER_DEBUG -DLINU...]
    /usr/local/lib/ruby-ent/lib/ruby/gems/1.8/gems/passenger-2.0.3/Rakefile:169
    (See full trace by running task with –trace)

    ——————————————–
    It looks like something went wrong