Installing Passenger Enterprise + Standalone on an AWS production server
for Python apps + generic installation through source tarball

This page describes the installation of Passenger through the following operating system or installation method: generic installation through source tarball. Not the configuration you are looking for? Go back to the operating system / installation method selection menu.

On this page, we will install Passenger. After installing Passenger we can begin with deploying the app.

Table of contents

Installation

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.

Please login to the Passenger Enterprise Customer Area.

Click on the Install button in the Customer Area.

Click on the button to download the license key.

License key download button in the Customer Area

The license key will be downloaded to your local computer. Copy this license key file to your production server, for example using scp:

local-computer$ cd /path-to-your-local-computer-download-folder
local-computer$ scp -i your_ec2_key.pem passenger-enterprise-license adminuser@yourserver.com:

Replace adminuser with the name of an account with administrator privileges or sudo privileges. This is usually admin, ec2-user, root or ubuntu.

Finally, login to your production server and save the file as /etc/passenger-enterprise-license:

local-computer$ ssh -i your_ec2_key.pem adminuser@yourserver.com
production-server$ sudo mv passenger-enterprise-license /etc/passenger-enterprise-license
production-server$ chmod 644 /etc/passenger-enterprise-license

Step 2: download tarball, upload to server and extract

Go to the "Files" section in the Customer Area and download the tar.gz file of the Passenger Enterprise version you want. Copy that file to your production server, for example using scp:

local-computer$ cd /path-to-your-local-computer-download-folder
local-computer$ scp -i your_ec2_key.pem passenger-enterprise-server-X.X.X.tar.gz adminuser@yourserver.com:

(Replace X.X.X with the Passenger Enterprise version)

On your production server, extract the tarball to some place permanent. Replace /somewhere-permanent with the actual directory path that you want to extract to. /opt is usually a good directory.

production-server$ tar -xzvf passenger-enterprise-server-X.X.X.tar.gz -C /somewhere-permanent

From this point on, all commands that you run are supposed to be run on the production server, not on your local computer.

Step 3: install Ruby

Passenger supports multiple languages and its core is written in C++, but its installer and administration tools are written in Ruby, so you must install Ruby.

Even though Ruby is required, Ruby will normally not be loaded during normal operation unless you deploy a Ruby web application on Passenger. Passenger's dependency on Ruby is very minimal. See Lightweight Ruby dependency for details.

Debian, Ubuntu	sudo apt-get update sudo apt-get install -y ruby rake
Red Hat, CentOS, Fedora, ScientificLinux, Amazon Linux	Enable EPEL, then run as root: yum install -y ruby rubygem-rake
Arch Linux	sudo pacman -S ruby
macOS	No action needed. Ruby is installed by default.
Other operating systems	Install Ruby from the Ruby website.

Step 4: add Passenger to PATH

Add the Passenger bin directory to your PATH, so that your shell can locate the Passenger commands.

Open your shell's system-wide startup file. If you're using bash, this is usually /etc/bashrc or /etc/bash.bashrc. Inside that file, add this to the end:

PATH=/somewhere-permanent/passenger-enterprise-server-X.X.X/bin:$PATH
export PATH

Again, replace X.X.X with the Passenger version, and /somewhere-permanent with the actual directory path.

When you're done, restart all your shells so that your new PATH takes effect.

Make sure your bashrc is actually included by your bash profile, which might not be the case if you created the user with useradd instead of adduser for example.

Step 5: validate installation

After installation, please validate the install by running sudo passenger-config validate-install. For example:

$ sudo 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.

FAQ

How do I automate the downloading of the tarball?

You can use HTTP basic authentication.

In the Customer Area, right-click on the download button for the tarball and click "Copy link URL". That is the URL for the tarball. You can automate the download of that tarball by using download as the HTTP username and your download key as the HTTP password.

Here is an example using curl:

$ unset HISTFILE
$ VERSION=5.0.30 && curl --fail -L -o passenger-enterprise-server-${VERSION}.tar.gz -u download:YOUR_DOWNLOAD_KEY "https://www.phusionpassenger.com/orders/download?dir=${VERSION}&file=passenger-enterprise-server-${VERSION}.tar.gz"

Some of the dependent libraries are installed in non-standard locations. How do I allow the compiler to find them?

Please refer to Customizing the compilation process.

How do I pass additional flags to the compiler?