Version 5.2.3 of the Passenger application server for Ruby, Node.js, Meteor and Python has been released. We've fixed a macOS build issue and removed hardcoded references to
/tmp. Python 3 support was improved and a few minor issues fixed.
The 5.2 series brings a major internal overhaul of configuration management, which is the first step in deep inspection and on-the-fly reconfiguration of Passenger. The 5.x series of Passenger in general brings a plethora of improvements in uptime maximization, security and efficiency.
macOS compilation fix
passenger-config compile-nginx-engine command failed to complete on macOS >= 10.13 due to a missing
require call in our code. The command is relevant for users who compile Passenger from source, which also happens under the hood with the Passenger Enterprise Homebrew formula.
Full $TMPDIR support
Passenger already respected the value of the
TMPDIR environment variable as the location of the
/tmp dir in most cases. We've gotten rid of the remaining cases that hardcoded
/tmp (GH-2052), so that it is for example now possible to run Passenger on a read-only filesystem with a custom
Various improvements & fixes
- Fuse Panel support: fixes a few bugs with handling small log files and with apps that don't output any messages.
- Python app support: fixes a Python 3 compatibility issue w.r.t. writing data over the socket.
- Fixes a small memory corruption issue (dangling pointer) in the ApplicationPool subsystem.
- Updated PCRE version to 8.42 (was: 8.41) across the board.
Please see the installation guide.
Upgrading to 5.2.3
We strongly advise staying up to date with the latest version.
See also the upgrade notes below!
If you are upgrading from 4.x, please read the 5.0 upgrade notes to learn about potential upgrade caveats.