Version 5.0.13 of the Phusion Passenger application server for Ruby, Python, Node.js and Meteor has been released.
If you hadn't already, be sure to check out the many major improvements that the 5.x series of Passenger introduces. And please be aware that you can enjoy enterprise features and sponsor the open source development directly by buying Phusion Passenger Enterprise.
Version 5.0.12 has been skipped because it contained a hotfix for Enterprise customers. The changes in 5.0.12 and 5.0.13 together are as follows.
- SELinux policy issues in the RPMs have been fixed.
passenger-config reopen-logsdidn't work on Apache unless you explicitly set
PassengerLogFile. This has now been fixed.
- [Standalone] Due to some internal refactorings, the Passenger Standalone Nginx configuration template has changed. If you used a custom Nginx configuration template, please merge our latest changes into it.
- [Enterprise] Fixed passenger-irb. It was broken in 5.0.10 because of the change that made using admin commands without sudo possible.
passenger-config restart-appcommand now supports the option
--ignore-passenger-not-running. If this option is given, the command will exit normally instead of exiting with an error, if Passenger is not running. This option is useful in deployments involving Passenger Standalone. In an initial deployment, Passenger Standalone may not yet be running. Passing this option allows you to ignore that issue.
Installing or upgrading to 5.0.13
We recommend upgrading to the latest version of Passenger, especially if you are on version 5.0.5 or below.
If you are upgrading from 4.x, please read the 5.0 upgrade notes to learn about potential upgrade caveats.