Installing Passenger Enterprise + Apache on a Linux/Unix production server
for Node.js apps + Mac OS X
On this page, we will install Passenger. After installing Passenger we can begin with deploying the app.
Table of contents
Step 1: download and install your license key
Before you can install Passenger Enterprise, you need to download and install your license key. This is a regular file that you need to copy to your production server.
Click on the button to download the license key.
The license key will be downloaded to your local computer. Copy this license key file to your production server, for example using
local-computer$ cd /path-to-your-local-computer-download-folder local-computer$ scp passenger-enterprise-license email@example.com:
adminuser with the name of an account with administrator privileges or sudo privileges.
Finally, login to your production server and save the file as
local-computer$ ssh firstname.lastname@example.org production-server$ sudo mv passenger-enterprise-license /etc/passenger-enterprise-license production-server$ chmod 644 /etc/passenger-enterprise-license
Step 2: obtain your download token
Your download token is needed in order to install Passenger Enterprise. In the Customer Area, find your download token and copy it to your clipboard.
Step 3: install Passenger package
You can install Passenger through Homebrew:
$ brew tap phusion/passenger $ brew install passenger-enterprise
You will be prompted to provide your download token when you install Passenger Enterprise through Homebrew, to avoid this prompt create a file at `~/.passenger-enterprise-download-token` containing only your token.
Not using Homebrew? Please go back to the operating system selection menu and choose "Other" as operating system.
Step 4: enable the Passenger Apache module and restart Apache
Passenger is now installed, but it still needs to be enabled inside Apache. Run
brew info passenger-enterprise and follow the instructions in the "Caveats" section:
$ brew info passenger-enterprise ... ==> Caveats ... To activate Passenger for Apache, create /etc/apache2/other/passenger.conf: (...more instructions that you should follow...)
When you are done following the instructions, restart Apache:
$ sudo apachectl restart
Running OS X Server >= 10.8 Mountain Lion with Web Services?
If you are running a sufficiently recent version of OS X Server (i.e. not the desktop version), and at the same time you are using the Web Services feature, then:
- The configuration file you need to create is not /etc/apache2/other/passenger.conf (despite what Homebrew tells you), but /Library/Server/Web/Config/apache2/httpd_server_app.conf.
- Do not use
apachectlto restart Apache. Use the Web Services administration panel to restart Apache.
Step 5: check installation
After installation, please validate the install by running
sudo /usr/local/bin/passenger-config validate-install. For example:
$ sudo /usr/local/bin/passenger-config validate-install * Checking whether this Phusion Passenger install is in PATH... ✓ * Checking whether there are no other Phusion Passenger installations... ✓
All checks should pass. If any of the checks do not pass, please follow the suggestions on screen.
Finally, check whether Apache has started the Passenger core processes. Run
sudo /usr/local/bin/passenger-memory-stats. You should see Apache processes as well as Passenger processes. For example:
$ sudo /usr/local/bin/passenger-memory-stats Version: 5.0.8 Date : 2015-05-28 08:46:20 +0200 ---------- Apache processes ---------- PID PPID VMSize Private Name -------------------------------------- 3918 1 190.1 MB 0.1 MB /usr/sbin/apache2 ... ----- Passenger processes ------ PID VMSize Private Name -------------------------------- 12517 83.2 MB 0.6 MB Passenger watchdog 12520 266.0 MB 3.4 MB Passenger core 12531 149.5 MB 1.4 MB Passenger ust-router ...
If you do not see any Apache processes or Passenger processes, then you probably have some kind of installation problem or configuration problem. Please refer to the troubleshooting guide.
Now that you have installed Passenger, you are ready to deploy your Node.js application on the production server!