Phusion Passenger 4.0.1 final release
blog.phusion.nl
Phusion Passenger 4.0.1 final release
1–10 of 24 posts
Re: Phusion Passenger 4.0.1 final release
#2Check out this new Phusion Passenger 4.x series. It has much, MUCH improved performance, stability and features that rivals that of Unicorn, Puma, etc. It's used by the likes of New York Times, Symantec, AirBnB, etc.
The main reason why people use Phusion Passenger is because of its ease of use. The way it integrates into Apache and Nginx is unlike other app servers and saves a lot of administration time and effort.
Re: Phusion Passenger 4.0.1 final release
#3If the phusion passenger people built a plugin for cpanel that gave easy installation and configuration of ruby/pythons app, I really think it could disrupt the php monopoly on cheap hosting for mid level web devs.
Deployment would be vastly eased to the same php strategy of "just ftp the files to the server and visit the website".
Re: Phusion Passenger 4.0.1 final release
#4How can we improve Phusion Passenger? We're very open to feedback from HN readers. If you have any suggestions, please let us know. If you have any questions about it please feel free to ask.
Re: Phusion Passenger 4.0.1 final release
#5I really like the general out-of-bound work feature, however I have a hard time imagining a use-case that is not garbage-collection, and that wouldn't be better solved by having a background worker process. Can anyone suggest some situations?
Re: Phusion Passenger 4.0.1 final release
#6I really like the general out-of-bound work feature, however I have a hard time imagining a use-case that is not garbage-collection, and that wouldn't be better solved by having a background worker process. Can anyone suggest some situations?
In theory it can be used for any kind of work that cannot be (easily) passed to another process, and that would block all threads. Another use case that I can think of is generating garbage collection statistics. But perhaps the community can find more use cases, we made it general so that people can be creative. :)
Re: Phusion Passenger 4.0.1 final release
#7How can we improve Phusion Passenger? We're very open to feedback from HN readers. If you have any suggestions, please let us know. If you have any questions about it please feel free to ask.
1. Does nginx spdy module is enabled by default?
2. Sometime ago you said that Ruby 2.0 has some bugs you suggested to wait for next Ruby 2.0 patch release. Is this still the case?
Re: Phusion Passenger 4.0.1 final release
#8How can we improve Phusion Passenger? We're very open to feedback from HN readers. If you have any suggestions, please let us know. If you have any questions about it please feel free to ask.
I'd love to see a 'phusion passenger for background tasks'. Managing large amounts of resque workers is a pain.
Re: Phusion Passenger 4.0.1 final release
#9How can we improve Phusion Passenger? We're very open to feedback from HN readers. If you have any suggestions, please let us know. If you have any questions about it please feel free to ask.
1. Does nginx spdy module is enabled by default? 2. Sometime ago you said that Ruby 2.0 has some bugs you suggested to wait for next Ruby 2.0 patch release. Is this still the case?
1. No, but you can easily enable it by yourself by choosing option "(2) I want to customize my Nginx installation. (for advanced users)" in passenger-install-nginx-module. Arbitrary Nginx configuration is fully supported. We're going to enable SPDY by default in a future versions.
2. Yes. Phusion Passenger 4 fully supports Ruby 2.0 so it doesn't prevent you from using it, but you may run into Ruby 2.0 bugs, e.g. https://bugs.ruby-lang.org/issues/8100. We recommend staying with 1.9.3 until the next Ruby 2.0 patchlevel, but the choice is yours.
Re: Phusion Passenger 4.0.1 final release
#10How can we improve Phusion Passenger? We're very open to feedback from HN readers. If you have any suggestions, please let us know. If you have any questions about it please feel free to ask.
I'd love to see a 'phusion passenger for background tasks'. Managing large amounts of resque workers is a pain.
That is a great suggestion, and it has actually been on our minds of a while now.