passenger 5.0.14 → 5.0.15

data/doc/Users guide Standalone.html

@@ -1073,25 +1073,7 @@ pre {
 <img src="images/phusion_banner.png" alt="images/phusion_banner.png">
 </a>
 </span></p></div>
-<div class="paragraph"><p><a href="https://www.phusionpassenger.com/">Phusion Passenger</a> is a web server and application server, designed to be fast, robust and lightweight. It runs your web apps with the least amount of hassle by taking care of almost all administrative heavy lifting for you. Advanced administration tools allow you to gain deep insight into your web applications' operations and to keep your servers healthy. Phusion Passenger is polyglot by design, and currently supports Ruby (Rack), Python (WSGI) and Node.js.</p></div>
-<div class="paragraph"><p>In the Standalone mode, Phusion Passenger operates as a fully-featured, secure standalone HTTP server. You do not need to have an existing web server like Apache or Nginx. This mode is ideal…</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-…if you are not familiar with Apache or Nginx
-</p>
-</li>
-<li>
-<p>
-…when you want to quickly start up a server without editing configuration files (e.g. during development)
-</p>
-</li>
-<li>
-<p>
-…or when you want to decouple the web server from the application server, by setting up reverse proxies.
-</p>
-</li>
-</ul></div>
+<div class="paragraph"><p>This is the old, deprecated Passenger Standalone documentation. Please visit <a href="https://www.phusionpassenger.com/library/">https://www.phusionpassenger.com/library/</a> for the new documentation.</p></div>
 </div>
 </div>
 <div id="toc">
@@ -1133,14 +1115,11 @@ pre {
 <div class="foo toclevel3"><a href="#config_file">4.2. Configuration file</a></div>
 <div class="foo toclevel3"><a href="#advanced_configuration">4.3. Advanced configuration</a></div>
 <div class="foo toclevel2"><a href="#_using_passenger_standalone_in_production">5. Using Passenger Standalone in production</a></div>
-<div class="foo toclevel3"><a href="#starting_at_system_boot">5.1. Starting Passenger Standalone at system boot</a></div>
+<div class="foo toclevel3"><a href="#_starting_passenger_standalone_at_system_boot">5.1. Starting Passenger Standalone at system boot</a></div>
 <div class="foo toclevel3"><a href="#sharing_port">5.2. Sharing the same port between multiple Passenger Standalone instances</a></div>
 <div class="foo toclevel3"><a href="#_installing_passenger_standalone_behind_nginx">5.3. Installing Passenger Standalone behind Nginx</a></div>
 <div class="foo toclevel2"><a href="#mass_deployment">6. Mass deployment</a></div>
 <div class="foo toclevel2"><a href="#troubleshooting">7. Troubleshooting</a></div>
-<div class="foo toclevel3"><a href="#_generic_troubleshooting_tips">7.1. Generic troubleshooting tips</a></div>
-<div class="foo toclevel3"><a href="#_upon_uploading_a_file_phusion_passenger_reports_client_body_temp_00000000xx_failed_2_no_such_file_or_directory">7.2. Upon uploading a file, Phusion Passenger reports "client_body_temp/00000000xx failed (2: No such file or directory)"</a></div>
-<div class="foo toclevel3"><a href="#_i_get_command_not_found_when_running_a_phusion_passenger_command_through_sudo">7.3. I get "command not found" when running a Phusion Passenger command through sudo</a></div>
 <div class="foo toclevel2"><a href="#_under_the_hood">8. Under the hood</a></div>
 <div class="foo toclevel3"><a href="#relationship_with_ruby">8.1. Phusion Passenger and its relationship with Ruby</a></div>
 <div class="foo toclevel4"><a href="#_how_ruby_is_used">8.1.1. How Ruby is used</a></div>
@@ -1165,130 +1144,7 @@ pre {
 <div class="sectionbody">
 <div class="sect2">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_supported_operating_systems_and_languages"></span><h3 data-comment-topic="supported-operating-systems-1387080" data-anchor="_supported_operating_systems_and_languages">1.1. Supported operating systems and languages</h3>
-<div class="paragraph"><p>Phusion Passenger works on almost any POSIX-compliant operating system. In other
-words: practically any operating system on earth, except Microsoft Windows.</p></div>
-<div class="paragraph"><p>Supported operating systems:</p></div>
-<table class="tableblock frame-all grid-all" style="
-width:100%;
-">
-<col style="width:50%;">
-<col style="width:50%;">
-<thead>
-<tr>
-<th class="tableblock halign-left valign-top"> OS                  </th>
-<th class="tableblock halign-left valign-top"> Minimum version</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Ubuntu</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">10.04</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Debian</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">6</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Red Hat, CentOS</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">5</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Amazon Linux</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">All versions supported</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Mac OS X</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">10.8 Mountain Lion</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">FreeBSD</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">8</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">OpenBSD</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">5.2</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Other Unix</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">-</p></td>
-</tr>
-</tbody>
-</table>
-<div class="paragraph"><p>"Other Unix" is supported on a "best-effort" basis. We do not regularly check whether Phusion Passenger still works on other Unices, but if users report issues then we’ll try to address them.</p></div>
-<div class="paragraph"><p>Supported architectures:</p></div>
-<table class="tableblock frame-all grid-all" style="
-width:100%;
-">
-<col style="width:50%;">
-<col style="width:50%;">
-<thead>
-<tr>
-<th class="tableblock halign-left valign-top"> Architecture      </th>
-<th class="tableblock halign-left valign-top"> Notes</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">x86 (32-bit)</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">-</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">x86_64 (64-bit)</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">-</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Other</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Supported on a "best-effort" basis.</p></td>
-</tr>
-</tbody>
-</table>
-<div class="paragraph"><p>Supported languages and frameworks:</p></div>
-<table class="tableblock frame-all grid-all" style="
-width:100%;
-">
-<col style="width:50%;">
-<col style="width:50%;">
-<thead>
-<tr>
-<th class="tableblock halign-left valign-top"> Language/framework  </th>
-<th class="tableblock halign-left valign-top"> Minimum version</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Ruby (MRI)</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">1.8.5</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">JRuby</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">1.7.0</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Rubinius</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">2.2.0</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Ruby on Rails</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">2.3</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Python</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">2.6</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Node.js/io.js</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">0.10</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Meteor</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">0.6</p></td>
-</tr>
-</tbody>
-</table>
-<div class="paragraph"><p>If you run into any issues, please
-<a href="https://github.com/phusion/passenger/issues">report a bug</a>
-or
-<a href="http://groups.google.com/group/phusion-passenger">join our discussion forum</a>.</p></div>
+<div class="paragraph"><p>This documentation has moved. <a href="https://www.phusionpassenger.com/library/install/supported_operating_systems_and_languages.html">https://www.phusionpassenger.com/library/install/supported_operating_systems_and_languages.html</a></p></div>
 </div>
 <div class="sect2">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="where_to_get_support"></span><h3 data-comment-topic="where-to-get-support-xkx7rx" data-anchor="where_to_get_support">1.2. Where to get support</h3>
@@ -1330,360 +1186,34 @@ Report security vulnerabilities to <a href="mailto:security@phusion.nl">security
 <div class="sectionbody">
 <div class="sect2">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_synopsis"></span><h3 data-comment-topic="synopsis-92sr34" data-anchor="_synopsis">2.1. Synopsis</h3>
-<div class="paragraph"><p>Because Phusion Passenger is designed to run in a wide variety of operating systems and configurations, there are multiple ways to install it. Most users  — especially first-time users — will prefer <em>OS-specific installation instructions</em>. These are not only the easiest, but also allow Phusion Passenger to integrate into the operating system in the best way possible. Other users should consult the <em>generic installation instructions</em>.</p></div>
-<div class="paragraph"><p>The steps for upgrading or downgrading Phusion Passenger is almost the same as the steps for installing. All the installation guides in this section will also teach you how to upgrade and downgrade.</p></div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/install/">https://www.phusionpassenger.com/library/install/</a></p></div>
 </div>
 <div class="sect2">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="install_osx_homebrew"></span><h3 data-comment-topic="installing-or-upgrading-on-mac-os-x-with-homebrew-fxjdi1" data-anchor="install_osx_homebrew">2.2. Installing or upgrading on Mac OS X with Homebrew</h3>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<strong>Open source</strong>
-</dt>
-<dd>
-<p>
-        Every time we release a new Phusion Passenger version, we make it available through <a href="http://brew.sh/">Homebrew</a>. Please note that the Homebrew maintainers have to merge our pull requests manually, so it may take a day or two before a new version shows up in the official Homebrew repository.
-</p>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-Update the Homebrew recipes:
-</p>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>brew update</pre>
-</div>
-</div>
-</li>
-<li>
-<p>
-Run one of the following, and follow the instructions:
-</p>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>brew install passenger
--OR-
-brew upgrade passenger</pre>
-</div>
-</div>
-</li>
-</ol></div>
-</dd>
-<dt class="hdlist1">
-<strong>Enterprise</strong>
-</dt>
-<dd>
-<p>
-        <a href="https://www.phusionpassenger.com/enterprise">Phusion Passenger Enterprise</a> is currently not available through Homebrew. Please try one of the other installation methods instead.
-</p>
-</dd>
-</dl></div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/install/">https://www.phusionpassenger.com/library/install/</a></p></div>
 </div>
 <div class="sect2">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="install_on_debian_ubuntu"></span><h3 data-comment-topic="installing-or-upgrading-on-debian-or-ubuntu-gme2a9" data-anchor="install_on_debian_ubuntu">2.3. Installing or upgrading on Debian or Ubuntu</h3>
-<div class="paragraph"><p>We provide an official Phusion Passenger APT repository. This APT repository contains Phusion Passenger packages for multiple versions of Debian and Ubuntu. These packages are automatically built by our build server after we push out a source release, and thus are always up to date with the official source releases.</p></div>
-<div class="paragraph"><p>If you use these packages to install Phusion Passenger then you do not need to run <span class="monospaced">passenger-install-apache2-module</span> or <span class="monospaced">passenger-install-nginx-module</span>. These packages contain all the binaries that you need.</p></div>
-<div class="paragraph"><p>Packages are available for the x86 and x86_64 architectures. Our policy is to support all Ubuntu LTS releases that are still supported by Canonical, plus the latest Ubuntu release, plus all Debian releases that are still supported by Debian.</p></div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/install/apt_repo/">https://www.phusionpassenger.com/library/install/apt_repo/</a></p></div>
 <div class="sect3">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="install_add_apt_repo"></span><h4 data-comment-topic="adding-our-apt-repository-1qu2se8" data-anchor="install_add_apt_repo">2.3.1. Adding our APT repository</h4>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-Install our PGP key. Packages are signed by "Phusion Automated Software Signing (<a href="mailto:auto-software-signing@phusion.nl">auto-software-signing@phusion.nl</a>)", fingerprint 1637 8A33 A6EF 1676 2922 526E 561F 9B9C AC40 B2F7.
-</p>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 561F9B9CAC40B2F7</pre>
-</div>
-</div>
-</li>
-<li>
-<p>
-Add HTTPS support for APT. Our APT repository is stored on an HTTPS server.
-</p>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>sudo apt-get install apt-transport-https ca-certificates</pre>
-</div>
-</div>
-</li>
-<li>
-<p>
-Create a file <span class="monospaced">/etc/apt/sources.list.d/passenger.list</span> and insert <strong>one of</strong> the following lines, depending on your distribution.
-</p>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<strong>Open source</strong>
-</dt>
-<dd>
-<div class="listingblock">
-<div class="content">
-<!-- Generator: GNU source-highlight 2.11.1
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt><span style="font-style: italic"><span style="color: #9A1900">##### !!!! Only add ONE of these lines, not all of them !!!! #####</span></span>
-<span style="font-style: italic"><span style="color: #9A1900"># Ubuntu 15.04</span></span>
-deb https<span style="color: #990000">:</span>//oss-binaries<span style="color: #990000">.</span>phusionpassenger<span style="color: #990000">.</span>com/apt/passenger vivid main
-<span style="font-style: italic"><span style="color: #9A1900"># Ubuntu 14.04</span></span>
-deb https<span style="color: #990000">:</span>//oss-binaries<span style="color: #990000">.</span>phusionpassenger<span style="color: #990000">.</span>com/apt/passenger trusty main
-<span style="font-style: italic"><span style="color: #9A1900"># Ubuntu 12.04</span></span>
-deb https<span style="color: #990000">:</span>//oss-binaries<span style="color: #990000">.</span>phusionpassenger<span style="color: #990000">.</span>com/apt/passenger precise main
-<span style="font-style: italic"><span style="color: #9A1900"># Debian 8</span></span>
-deb https<span style="color: #990000">:</span>//oss-binaries<span style="color: #990000">.</span>phusionpassenger<span style="color: #990000">.</span>com/apt/passenger jessie main
-<span style="font-style: italic"><span style="color: #9A1900"># Debian 7</span></span>
-deb https<span style="color: #990000">:</span>//oss-binaries<span style="color: #990000">.</span>phusionpassenger<span style="color: #990000">.</span>com/apt/passenger wheezy main
-<span style="font-style: italic"><span style="color: #9A1900"># Debian 6</span></span>
-deb https<span style="color: #990000">:</span>//oss-binaries<span style="color: #990000">.</span>phusionpassenger<span style="color: #990000">.</span>com/apt/passenger squeeze main</tt></pre>
-</div>
-</div>
-</dd>
-<dt class="hdlist1">
-<strong>Enterprise</strong>
-</dt>
-<dd>
-<div class="listingblock">
-<div class="content">
-<!-- Generator: GNU source-highlight 2.11.1
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt><span style="font-style: italic"><span style="color: #9A1900">##### !!!! Only add ONE of these lines, not all of them !!!! #####</span></span>
-<span style="font-style: italic"><span style="color: #9A1900"># Ubuntu 15.04</span></span>
-deb https<span style="color: #990000">:</span>//download<span style="color: #990000">:</span>YOUR_DOWNLOAD_TOKEN@www<span style="color: #990000">.</span>phusionpassenger<span style="color: #990000">.</span>com/enterprise_apt vivid main
-<span style="font-style: italic"><span style="color: #9A1900"># Ubuntu 14.04</span></span>
-deb https<span style="color: #990000">:</span>//download<span style="color: #990000">:</span>YOUR_DOWNLOAD_TOKEN@www<span style="color: #990000">.</span>phusionpassenger<span style="color: #990000">.</span>com/enterprise_apt trusty main
-<span style="font-style: italic"><span style="color: #9A1900"># Ubuntu 12.04</span></span>
-deb https<span style="color: #990000">:</span>//download<span style="color: #990000">:</span>YOUR_DOWNLOAD_TOKEN@www<span style="color: #990000">.</span>phusionpassenger<span style="color: #990000">.</span>com/enterprise_apt precise main
-<span style="font-style: italic"><span style="color: #9A1900"># Debian 8</span></span>
-deb https<span style="color: #990000">:</span>//download<span style="color: #990000">:</span>YOUR_DOWNLOAD_TOKEN@www<span style="color: #990000">.</span>phusionpassenger<span style="color: #990000">.</span>com/enterprise_apt jessie main
-<span style="font-style: italic"><span style="color: #9A1900"># Debian 7</span></span>
-deb https<span style="color: #990000">:</span>//download<span style="color: #990000">:</span>YOUR_DOWNLOAD_TOKEN@www<span style="color: #990000">.</span>phusionpassenger<span style="color: #990000">.</span>com/enterprise_apt wheezy main
-<span style="font-style: italic"><span style="color: #9A1900"># Debian 6</span></span>
-deb https<span style="color: #990000">:</span>//download<span style="color: #990000">:</span>YOUR_DOWNLOAD_TOKEN@www<span style="color: #990000">.</span>phusionpassenger<span style="color: #990000">.</span>com/enterprise_apt squeeze main</tt></pre>
-</div>
-</div>
-<div class="paragraph"><p>You can find the correct value for <em>YOUR_DOWNLOAD_TOKEN</em> in the <a href="https://www.phusionpassenger.com/orders">Customer Area</a>.</p></div>
-</dd>
-</dl></div>
-</li>
-<li>
-<p>
-Secure <span class="monospaced">passenger.list</span> and update your APT cache:
-</p>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>sudo chown root: /etc/apt/sources.list.d/passenger.list
-sudo chmod 600 /etc/apt/sources.list.d/passenger.list
-sudo apt-get update</pre>
-</div>
-</div>
-</li>
-<li>
-<p>
-(Optional) If using <span class="monospaced">unattended-upgrades</span>, add our APT repository to the list of <span class="monospaced">Allowed-Origins</span> for upgrades, <span class="monospaced">/etc/apt/apt.conf.d/50unattended-upgrades</span>:
-</p>
-<div class="listingblock">
-<div class="content">
-<!-- Generator: GNU source-highlight 2.11.1
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt><span style="color: #990000">//</span> Automatically upgrade packages from these <span style="color: #990000">(</span>origin<span style="color: #990000">:</span>archive<span style="color: #990000">)</span> pairs
-Unattended-Upgrade<span style="color: #990000">::</span>Allowed-Origins {
-  <span style="color: #990000">//</span> To check <span style="color: #FF0000">"Origin:"</span> and <span style="color: #FF0000">"Suite:"</span><span style="color: #990000">,</span> you could use e<span style="color: #990000">.</span>g<span style="color: #990000">.:</span>
-  <span style="color: #990000">//</span> grep <span style="color: #FF0000">"Origin</span><span style="color: #CC33CC">\|</span><span style="color: #FF0000">Suite"</span> /var/lib/apt/lists/oss-binaries<span style="color: #990000">.</span>phusionpassenger<span style="color: #990000">.</span>com<span style="color: #990000">*</span>
-  <span style="color: #FF0000">"Phusion:stable"</span><span style="color: #990000">;</span>
-}<span style="color: #990000">;</span></tt></pre>
-</div>
-</div>
-</li>
-</ol></div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/install/apt_repo/">https://www.phusionpassenger.com/library/install/apt_repo/</a></p></div>
 </div>
 <div class="sect3">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_installing_packages"></span><h4 data-comment-topic="installing-packages-k1zxbg" data-anchor="_installing_packages">2.3.2. Installing packages</h4>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<strong>Open source</strong>
-</dt>
-<dd>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-<a href="#install_add_apt_repo">Add our APT repository.</a>
-</p>
-</li>
-<li>
-<p>
-Install the package:
-</p>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>sudo apt-get install passenger</pre>
-</div>
-</div>
-</li>
-</ol></div>
-</dd>
-<dt class="hdlist1">
-<strong>Enterprise</strong>
-</dt>
-<dd>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-Download your license key from the <a href="https://www.phusionpassenger.com/orders">Customer Area</a> and save it as <span class="monospaced">/etc/passenger-enterprise-license</span>.
-</p>
-</li>
-<li>
-<p>
-<a href="#install_add_apt_repo">Add our APT repository.</a>
-</p>
-</li>
-<li>
-<p>
-Install the packages:
-</p>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>sudo apt-get install passenger-enterprise</pre>
-</div>
-</div>
-</li>
-</ol></div>
-</dd>
-</dl></div>
-<div class="paragraph"><p>You can now proceed with a chapter for Deploying your (specific type of) application.</p></div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/install/apt_repo/">https://www.phusionpassenger.com/library/install/apt_repo/</a></p></div>
 </div>
 </div>
 <div class="sect2">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="installing_or_upgrading_on_red_hat"></span><h3 data-comment-topic="installing-or-upgrading-on-red-hat-fedora-centos-or-scientificlinux-16cek45" data-anchor="installing_or_upgrading_on_red_hat">2.4. Installing or upgrading on Red Hat or CentOS</h3>
-<div class="paragraph"><p>We provide an official Phusion Passenger YUM repository with packages for Red Hat Enterprise Linux and CentOS. These packages are automatically built by our build server after we push out a source release, and thus are always up to date with the official source releases.</p></div>
-<div class="paragraph"><p>If you use these packages to install Phusion Passenger then you do not need to run <span class="monospaced">passenger-install-apache2-module</span> or <span class="monospaced">passenger-install-nginx-module</span>. These packages contain all the binaries that you need. These packages also come with SELinux policy modules so that Passenger works nicely with SELinux.</p></div>
-<div class="paragraph"><p>Packages are available for the x86 and x86_64 architectures. Our policy is to support all Red Hat and CentOS releases that still receive full updates by their vendors. The earliest Red Hat and CentOS version we support is version 5.</p></div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/install/yum_repo/">https://www.phusionpassenger.com/library/install/yum_repo/</a></p></div>
 <div class="sect3">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="install_add_yum_repo"></span><h4 data-comment-topic="adding-our-yum-repository-7c3y3z" data-anchor="install_add_yum_repo">2.4.1. Adding our YUM repository</h4>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-Install <a href="https://fedoraproject.org/wiki/EPEL">EPEL</a> and a few other prerequisites.
-</p>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>sudo yum install epel-release pygpgme curl</pre>
-</div>
-</div>
-</li>
-<li>
-<p>
-Download the Passenger YUM repository definition.
-</p>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<strong>Open source</strong>
-</dt>
-<dd>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>sudo curl --fail -sSLo /etc/yum.repos.d/passenger.repo https://oss-binaries.phusionpassenger.com/yum/definitions/el-passenger.repo</pre>
-</div>
-</div>
-</dd>
-<dt class="hdlist1">
-<strong>Enterprise</strong>
-</dt>
-<dd>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>unset HISTFILE
-sudo curl --fail -sSL -u download:YOUR_DOWNLOAD_TOKEN -o /etc/yum.repos.d/passenger.repo https://www.phusionpassenger.com/enterprise_yum/el-passenger-enterprise.repo</pre>
-</div>
-</div>
-<div class="paragraph"><p>The <span class="monospaced">unset HISTFILE</span> command ensures that your download token isn’t saved to the Bash history file.</p></div>
-<div class="paragraph"><p>You can find the correct value for <em>YOUR_DOWNLOAD_TOKEN</em> in the <a href="https://www.phusionpassenger.com/orders">Customer Area</a>.</p></div>
-</dd>
-</dl></div>
-</li>
-<li>
-<p>
-Secure <span class="monospaced">passenger.repo</span>:
-</p>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>sudo chown root: /etc/yum.repos.d/passenger.repo
-sudo chmod 600 /etc/yum.repos.d/passenger.repo</pre>
-</div>
-</div>
-</li>
-</ol></div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/install/yum_repo/">https://www.phusionpassenger.com/library/install/yum_repo/</a></p></div>
 </div>
 <div class="sect3">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_installing_packages_2"></span><h4 data-comment-topic="installing-packages-1i5z60y" data-anchor="_installing_packages_2">2.4.2. Installing packages</h4>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="./images/icons/note.png" alt="Note">
-</td>
-<td class="content">
-<div class="title">Notes about SELinux on Red Hat 6 and CentOS 6</div>
-<div class="paragraph"><p>If you are on Red Hat 6 or CentOS 6, and you are also using SELinux in enforcing mode, then Passenger requires kernel &gt;= 2.6.39.</p></div>
-<div class="paragraph"><p>If you want to install Passenger on Red Hat 6 or CentOS 6, without upgrading your kernel, then you must <strong>disable</strong> SELinux completely. Edit <span class="monospaced">/etc/selinux/config</span>, set <span class="monospaced">SELINUX=disabled</span> and reboot. Note that merely setting SELinux to permissive mode is not enough.</p></div>
-<div class="paragraph"><p>This issue does not apply to Red Hat &gt;= 7 and CentOS &gt;= 7, because these OS versions supply recent enough kernel versions.</p></div>
-</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>You can install the Passenger packages as follows.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<strong>Open source</strong>
-</dt>
-<dd>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-<a href="#install_add_yum_repo">Add our YUM repository.</a>
-</p>
-</li>
-<li>
-<p>
-Install the package:
-</p>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>sudo yum install passenger</pre>
-</div>
-</div>
-</li>
-</ol></div>
-</dd>
-<dt class="hdlist1">
-<strong>Enterprise</strong>
-</dt>
-<dd>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-Download your license key from the <a href="https://www.phusionpassenger.com/orders">Customer Area</a> and save it as <span class="monospaced">/etc/passenger-enterprise-license</span>.
-</p>
-</li>
-<li>
-<p>
-<a href="#install_add_yum_repo">Add our YUM repository.</a>
-</p>
-</li>
-<li>
-<p>
-Install the packages:
-</p>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>sudo yum install passenger-enterprise</pre>
-</div>
-</div>
-</li>
-</ol></div>
-</dd>
-</dl></div>
-<div class="paragraph"><p>You can now proceed with a chapter for Deploying your (specific type of) application.</p></div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/install/yum_repo/">https://www.phusionpassenger.com/library/install/yum_repo/</a></p></div>
 </div>
 </div>
 <div class="sect2">
@@ -1692,1290 +1222,125 @@ Install the packages:
 </div>
 <div class="sect2">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="rubygems_generic_install"></span><h3 data-comment-topic="generic-installation-upgrade-and-downgrade-method-via-rubygems-1229ugi" data-anchor="rubygems_generic_install">2.6. Generic installation, upgrade and downgrade method: via RubyGems</h3>
-<div class="paragraph"><p>RubyGems is only used as a method to obtain the Phusion Passenger files, so in case you have multiple Ruby versions it does not matter which Ruby’s RubyGems you use for installation. Once installed, Phusion Passenger can work with all other Ruby versions on your system. This is explained in <a href="#relationship_with_ruby">Phusion Passenger and its relationship with Ruby</a>.</p></div>
-<span class="anchor_helper" id="is_ruby_home_or_system_wide_installed"></span><h4 class="float" data-anchor="is_ruby_home_or_system_wide_installed">Step 1: figuring out whether your Ruby is installed in the home directory or system-wide</h4>
-<div class="paragraph"><p>Ruby may either be installed in the home directory, or system-wide. If it’s installed system-wide then we will want to install gems system-wide as well, so you need to switch to a root prompt first. If Ruby is installed in the home directory then we will want to install gems to the home directory as well, as a normal user.</p></div>
-<div class="paragraph"><p>To find out which case applies, run the following command to find out where the <span class="monospaced">ruby</span> command is:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>which ruby</pre>
-</div>
-</div>
-<div class="paragraph"><p>Do you see a filename that references <em>/home</em> or <em>/Users</em>? If so then your Ruby interpreter is installed in your home directory and you can proceed to step 2. Otherwise, you need to switch to a root prompt by running one of the following commands:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Are you using RVM? Run <span class="monospaced">rvmsudo -H bash</span>
-</p>
-</li>
-<li>
-<p>
-Are you not using RVM, or do you not know what RVM is? Run <span class="monospaced">sudo -H -s</span>
-</p>
-</li>
-<li>
-<p>
-Is <em>sudo</em> not installed on your system? Run <span class="monospaced">su -c bash</span>
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>You must maintain this root prompt throughout this installation guide.</p></div>
-<span class="anchor_helper" id="_step_2_install_the_gem"></span><h4 class="float" data-anchor="_step_2_install_the_gem">Step 2: install the gem</h4>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<strong>Open Source</strong>
-</dt>
-<dd>
-<p>
-        Install the latest gem to obtain the files for the latest stable version of the open source Phusion Passenger:
-</p>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>gem install passenger</pre>
-</div>
-</div>
-<div class="sidebarblock">
-<div class="content">
-<div class="title">Previous versions and beta versions</div>
-<div class="paragraph"><p>Sometimes you will want to obtain the latest beta version of Phusion Passenger. Beta versions are not normally selected by <span class="monospaced">gem install</span>, so to opt-in for beta versions you have to add the <span class="monospaced">--pre</span> argument:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>gem install passenger --pre</pre>
-</div>
-</div>
-<div class="paragraph"><p>If you want to obtain a specific version of Phusion Passenger, e.g. because you are downgrading, then specify the version number with <span class="monospaced">--version</span>:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>gem install passenger --version 3.0.0</pre>
-</div>
-</div>
-<div class="paragraph"><p>If you want to obtain a specific <strong>beta</strong> version of Phusion Passenger then you must also pass <span class="monospaced">--pre</span>:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>gem install passenger --version 3.9.1.beta --pre</pre>
-</div>
-</div>
-</div>
-</div>
-</dd>
-<dt class="hdlist1">
-<strong>Enterprise</strong>
-</dt>
-<dd>
-<p>
-First, download the <strong>license key</strong> from the <a href="https://www.phusionpassenger.com/orders">Customer Area</a> and save it as <span class="monospaced">/etc/passenger-enterprise-license</span>.
-</p>
-<div class="paragraph"><p>Next, add the Phusion Passenger Enterprise gem server to your RubyGems source list:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>gem source --add https://download:YOUR_DOWNLOAD_TOKEN@www.phusionpassenger.com/enterprise_gems/</pre>
-</div>
-</div>
-<div class="paragraph"><p>Substitute <em>YOUR_DOWNLOAD_TOKEN</em> with the one you find in the <a href="https://www.phusionpassenger.com/orders">Customer Area</a>. And notice the <strong>trailing slash</strong> in the URL! It is very important.</p></div>
-<div class="paragraph"><p>Finally, install the latest gem to obtain the files for the latest stable version of Passenger Enterprise:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>gem install passenger-enterprise-server</pre>
-</div>
-</div>
-<div class="sidebarblock">
-<div class="content">
-<div class="title">Previous versions and beta versions</div>
-<div class="paragraph"><p>Sometimes you will want to obtain the latest beta version of Phusion Passenger Enterprise. Beta versions are not normally selected by <span class="monospaced">gem install</span>, so to opt-in for beta versions you have to add the <span class="monospaced">--pre</span> argument:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>gem install passenger-enterprise-server --pre</pre>
-</div>
-</div>
-<div class="paragraph"><p>If you want to obtain a specific version of Phusion Passenger Enterprise, e.g. because you are downgrading, then specify the version number with <span class="monospaced">--version</span>:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>gem install passenger-enterprise-server --version 3.0.0</pre>
-</div>
-</div>
-<div class="paragraph"><p>If you want to obtain a specific <strong>beta</strong> version of Phusion Passenger then you must also pass <span class="monospaced">--pre</span>:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>gem install passenger-enterprise-server --version 3.9.1.beta --pre</pre>
-</div>
-</div>
-</div>
-</div>
-</dd>
-</dl></div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/install/">https://www.phusionpassenger.com/library/install/</a></p></div>
 </div>
 <div class="sect2">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="tarball_generic_install"></span><h3 data-comment-topic="generic-installation-upgrade-and-downgrade-method-via-tarball-1rwvasy" data-anchor="tarball_generic_install">2.7. Generic installation, upgrade and downgrade method: via tarball</h3>
-<span class="anchor_helper" id="_step_1_installing_ruby"></span><h4 class="float" data-anchor="_step_1_installing_ruby">Step 1: installing Ruby</h4>
-<div class="paragraph"><p>Phusion 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.</p></div>
-<div class="paragraph"><p>Even though Ruby is required, Ruby will normally not be loaded during normal operation unless you deploy a Ruby web application on Phusion Passenger. Phusion Passenger’s dependency on Ruby is very minimal. See <a href="#relationship_with_ruby">Phusion Passenger and its relationship with Ruby</a> for details.</p></div>
-<table class="tableblock frame-all grid-all" style="
-width:100%;
-">
-<col style="width:50%;">
-<col style="width:50%;">
-<tbody>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Debian, Ubuntu</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock"><span class="monospaced">sudo apt-get update</span><br>
-<span class="monospaced">sudo apt-get install ruby rake</span></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Red Hat, CentOS, ScientificLinux, Amazon Linux</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Enable <a href="http://fedoraproject.org/wiki/EPEL">EPEL</a>, then run as root:<br>
-<span class="monospaced">yum install ruby rubygem-rake</span></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Mac OS X</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">No action needed. Ruby is installed by default.</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Other operating systems</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Install Ruby from <a href="http://www.ruby-lang.org/">the Ruby website</a>.</p></td>
-</tr>
-</tbody>
-</table>
-<span class="anchor_helper" id="_step_2_download_and_extract_the_tarball"></span><h4 class="float" data-anchor="_step_2_download_and_extract_the_tarball">Step 2: download and extract the tarball</h4>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<strong>Open Source</strong>
-</dt>
-<dd>
-<p>
-        Download the open source Phusion Passenger tarball from <a href="https://www.phusionpassenger.com/download#open_source">the Phusion Passenger website</a>.
-</p>
-<div class="paragraph"><p>Older versions can be found in <a href="https://www.phusionpassenger.com/file_releases">the release archive</a>.</p></div>
-</dd>
-<dt class="hdlist1">
-<strong>Enterprise</strong>
-</dt>
-<dd>
-<p>
-        <a href="https://www.phusionpassenger.com/enterprise">Phusion Passenger Enterprise</a> customers can download the Phusion Passenger Enterprise tarball from the <a href="https://www.phusionpassenger.com/orders">Customer Area</a>.
-</p>
-<div class="paragraph"><p>Also be sure to download the <strong>license key</strong> and save it as <span class="monospaced">/etc/passenger-enterprise-license</span>.</p></div>
-</dd>
-</dl></div>
-<div class="paragraph"><p>Once you have downloaded the tarball, pick a location to extract it to. You can pick any location. A good location is <em>/opt/passenger</em>. Create this directory and extract the tarball as follows:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>mkdir /opt/passenger
-cd /opt/passenger
-tar xzvf /location-to/passenger-x.x.x.tar.gz
-cd /opt/passenger/passenger-x.x.x</pre>
-</div>
-</div>
-<div class="paragraph"><p>Note that <span class="monospaced">passenger-x.x.x</span> should be <span class="monospaced">passenger-enterprise-server-x.x.x</span> if you’re using Phusion Passenger Enterprise.</p></div>
-<span class="anchor_helper" id="_step_3_adding_the_phusion_passenger_tools_to_path"></span><h4 class="float" data-anchor="_step_3_adding_the_phusion_passenger_tools_to_path">Step 3: adding the Phusion Passenger tools to PATH</h4>
-<div class="paragraph"><p>Edit <span class="monospaced">/etc/bashrc</span> (or <span class="monospaced">/etc/bash.bashrc</span> on some systems) and append the following to the end of the file:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>export PATH=/opt/passenger/passenger-x.x.x/bin:$PATH</pre>
-</div>
-</div>
-<div class="paragraph"><p>Finally, restart all your shell sessions in order to activate this change. The installation is now complete.</p></div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/install/">https://www.phusionpassenger.com/library/install/</a></p></div>
 </div>
 <div class="sect2">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_upgrading_from_open_source_to_enterprise"></span><h3 data-comment-topic="upgrading-from-open-source-to-enterprise-1kezors" data-anchor="_upgrading_from_open_source_to_enterprise">2.8. Upgrading from open source to Enterprise</h3>
-<div class="paragraph"><p>Phusion Passenger comes in two variants: an open source version, as well as an <a href="https://www.phusionpassenger.com/enterprise">Enterprise version</a> which introduces a myriad of useful features that can improve stability and performance and efficiency.</p></div>
-<div class="paragraph"><p>Customers who have bought Phusion Passenger Enterprise can upgrade their open source installation to Enterprise as follows:</p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-<a href="#uninstalling">Uninstall the open source Phusion Passenger</a>.
-</p>
-</li>
-<li>
-<p>
-Install the Enterprise version by following one of the installation guides in this section (e.g. <a href="#rubygems_generic_install">RubyGems generic installation</a> or <a href="#tarball_generic_install">tarball generic installation</a>).
-</p>
-</li>
-</ol></div>
-<div class="paragraph"><p>The uninstallation is necessary because the Enterprise Ruby gem has a different gem name (<em>passenger-enterprise-server</em> instead of <em>passenger</em>), but the same administration command names (e.g. <span class="monospaced">passenger-status</span>). Uninstalling the open source version avoids any conflicts.</p></div>
+<div class="paragraph"><p>This documentation has moved. <a href="https://www.phusionpassenger.com/library/install/standalone/upgrading_from_oss_to_enterprise.html">https://www.phusionpassenger.com/library/install/standalone/upgrading_from_oss_to_enterprise.html</a></p></div>
 </div>
 <div class="sect2">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_cryptographic_verification_of_installation_files"></span><h3 data-comment-topic="cryptographic-verification-of-installation-files-85nwoi" data-anchor="_cryptographic_verification_of_installation_files">2.9. Cryptographic verification of installation files</h3>
 <div class="sect3">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_synopsis_2"></span><h4 data-comment-topic="synopsis-1ij8j9r" data-anchor="_synopsis_2">2.9.1. Synopsis</h4>
-<div class="paragraph"><p>We digitally sign various files with our GPG key so that you can check whether they’re legit, i.e. whether they really came from Phusion and haven’t been tampered with by a third party. We apply signing since the open source version 4.0.0 RC 4, or the Enterprise version 4.0.0 RC 1.</p></div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/install/crypto_verify_install.html">https://www.phusionpassenger.com/library/install/crypto_verify_install.html</a></p></div>
 </div>
 <div class="sect3">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_importing_the_phusion_software_signing_key"></span><h4 data-comment-topic="importing-the-phusion-software-signing-key-1u5hkcr" data-anchor="_importing_the_phusion_software_signing_key">2.9.2. Importing the Phusion Software Signing key</h4>
-<div class="paragraph"><p>Phusion’s GPG key for signing software is as follows:</p></div>
-<div class="literalblock">
-<div class="content monospaced">
-<pre>Phusion Software Signing (software-signing@phusion.nl)
-Short key ID: 0x0A212A8C
-Long key ID: 0x2AC745A50A212A8C
-Fingerprint: D5F0 8514 2693 9232 F437  AB72 2AC7 45A5 0A21 2A8C</pre>
-</div>
-</div>
-<div class="paragraph"><p>This key is stored at <a href="http://www.phusion.nl/about/gpg">the Phusion website</a> and at the key servers <a href="http://pool.sks-keyservers.net/pks/lookup?op=get&amp;search=0x2AC745A50A212A8C">sks-keyservers.net</a> and <a href="http://keyserver.ubuntu.com/pks/lookup?op=get&amp;search=0x2AC745A50A212A8C">keyserver.ubuntu.com</a>. You can import it to your keyring with one of these command:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>gpg --keyserver pool.sks-keyservers.net --search-keys 0x2AC745A50A212A8C
-# -OR-
-gpg --keyserver keyserver.ubuntu.com --search-keys 0x2AC745A50A212A8C</pre>
-</div>
-</div>
-<div class="paragraph"><p>The Phusion Software Signing key is only used for signing software. It’s never used for signing emails or for encrypting files, so please be suspicious if you encounter usage of this key outside the context of signing software, and alert us at <a href="mailto:support@phusion.nl">support@phusion.nl</a>. Include "notspam" in the message to bypass our spam filter.</p></div>
-<div class="paragraph"><p>The email address <a href="mailto:software-signing@phusion.nl">software-signing@phusion.nl</a> redirects to <a href="mailto:info@phusion.nl">info@phusion.nl</a> so it’s safe to send email there.</p></div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/install/crypto_verify_install.html">https://www.phusionpassenger.com/library/install/crypto_verify_install.html</a></p></div>
 </div>
 <div class="sect3">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_verifying_the_phusion_software_signing_key"></span><h4 data-comment-topic="verifying-the-phusion-software-signing-key-qor1n1" data-anchor="_verifying_the_phusion_software_signing_key">2.9.3. Verifying the Phusion Software Signing key</h4>
-<div class="paragraph"><p>The Phusion Software Signing key is also <strong>signed by the Phusion founders</strong>. Their keys are as follows:</p></div>
-<div class="literalblock">
-<div class="content monospaced">
-<pre>Hongli Lai (hongli@phusion.nl)
-Short key ID: 8C59158F
-Long key ID: CD70085E8C59158F
-Fingerprint: 218A 7255 83D0 2ECE F3A9 C2A7 CD70 085E 8C59 158F</pre>
-</div>
-</div>
-<div class="literalblock">
-<div class="content monospaced">
-<pre>Ninh Bui (ninh@phusion.nl)
-Short key ID: 69481265
-Long key ID: AE405F7869481265
-Fingerprint: A77C 9CEF 766D 0E7D A95B 8778 AE40 5F78 6948 1265</pre>
-</div>
-</div>
-<div class="paragraph"><p>Both keys are stored at both sks-servers.net and keyserver.ubuntu.com. Import them with:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>gpg --keyserver pool.sks-servers.net --search-keys 0xCD70085E8C59158F
-gpg --keyserver pool.sks-servers.net --search-keys 0xAE405F7869481265
-# -OR-
-gpg --keyserver keyserver.ubuntu.com --search-keys 0xCD70085E8C59158F
-gpg --keyserver keyserver.ubuntu.com --search-keys 0xAE405F7869481265</pre>
-</div>
-</div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/install/crypto_verify_install.html">https://www.phusionpassenger.com/library/install/crypto_verify_install.html</a></p></div>
 </div>
 <div class="sect3">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_verifying_the_gem_and_tarball"></span><h4 data-comment-topic="verifying-the-gem-and-tarball-i7tj7a" data-anchor="_verifying_the_gem_and_tarball">2.9.4. Verifying the gem and tarball</h4>
-<div class="paragraph"><p>You can find the open source version’s gem and tarball GPG signatures at <a href="https://www.phusionpassenger.com/file_releases">https://www.phusionpassenger.com/file_releases</a>. The Enterprise version’s GPG signatures can be found in the <a href="https://www.phusionpassenger.com/orders">Customer Area</a>. All signatures have the <em>.asc</em> extension. Once you have imported our key, you can verify the validity of a file against its signature as follows:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>$ gpg --verify passenger-x.x.x.tar.gz.asc passenger-x.x.x.tar.gz
-gpg: Signature made Mon Mar 11 09:45:46 2013 CET using RSA key ID 0A212A8C
-gpg: Good signature from "Phusion Software Signing &lt;software-signing@phusion.nl&gt;"</pre>
-</div>
-</div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/install/crypto_verify_install.html">https://www.phusionpassenger.com/library/install/crypto_verify_install.html</a></p></div>
 </div>
 <div class="sect3">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_verifying_git_signatures"></span><h4 data-comment-topic="verifying-git-signatures-dltpan" data-anchor="_verifying_git_signatures">2.9.5. Verifying Git signatures</h4>
-<div class="paragraph"><p>Tags in the <a href="https://github.com/phusion/passenger">Git repository for the open source version</a> are also tagged. You can verify a Git tag as follows:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>$ git tag --verify release-x.x.x
-object d886f34b5705e4314feccaf0d77b9a38416e15e0
-type commit
-tag release-4.0.0.rc5
-tagger Hongli Lai (Phusion) &lt;hongli@phusion.nl&gt; 1362993117 +0100
-
-This is a tag message.
-gpg: Signature made Mon Mar 11 10:12:02 2013 CET using RSA key ID 0A212A8C
-gpg: Good signature from "Phusion Software Signing &lt;software-signing@phusion.nl&gt;"</pre>
-</div>
-</div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/install/crypto_verify_install.html">https://www.phusionpassenger.com/library/install/crypto_verify_install.html</a></p></div>
 </div>
 <div class="sect3">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_verifying_debian_packages"></span><h4 data-comment-topic="verifying-deb-and-rpm-packages-uga0ho" data-anchor="_verifying_debian_packages">2.9.6. Verifying Debian packages</h4>
-<div class="paragraph"><p>Our <a href="#install_on_debian_ubuntu">APT repository</a> is signed by Phusion Automated Software Signing (<a href="mailto:auto-software-signing@phusion.nl">auto-software-signing@phusion.nl</a>). Packages are automatically checked upon installation.</p></div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/install/crypto_verify_install.html">https://www.phusionpassenger.com/library/install/crypto_verify_install.html</a></p></div>
 </div>
 <div class="sect3">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_verifying_rpm_packages"></span><h4 data-comment-topic="verifying-rpm-packages-1m745i5" data-anchor="_verifying_rpm_packages">2.9.7. Verifying RPM packages</h4>
-<div class="paragraph"><p>Our <a href="#installing_or_upgrading_on_red_hat">YUM repository</a> is signed by <a href="https://packagecloud.io">PackageCloud</a> (<a href="mailto:ops@packagecloud.io">ops@packagecloud.io</a>). PackageCloud is the RPM package hosting service that we use. You can find their key <a href="https://packagecloud.io/gpg.key">here</a>. Packages are automatically checked upon installation.</p></div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/install/crypto_verify_install.html">https://www.phusionpassenger.com/library/install/crypto_verify_install.html</a></p></div>
 </div>
 <div class="sect3">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_revocation"></span><h4 data-comment-topic="revocation-ukzeg9" data-anchor="_revocation">2.9.8. Revocation</h4>
-<div class="paragraph"><p>In the event our key is compromised, we will revoke the key and upload the revocation information to sks-servers.net and keyserver.ubuntu.com. However your system will not know about the revocation until you update the keys from the keyservers. You should update your keys regularly (e.g. once a week) by invoking:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>gpg --refresh-keys --keyserver pool.sks-servers.net
-# -OR-
-gpg --refresh-keys --keyserver keyserver.ubuntu.com</pre>
-</div>
-</div>
-<div class="paragraph"><p>If you installed Phusion Passenger through our APT repository, then you should update APT’s keyring from time to time as well:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>sudo apt-key adv --refresh-keys --keyserver keyserver.ubuntu.com</pre>
-</div>
-</div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/install/crypto_verify_install.html">https://www.phusionpassenger.com/library/install/crypto_verify_install.html</a></p></div>
 </div>
 </div>
 <div class="sect2">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_customizing_the_compilation_process"></span><h3 data-comment-topic="customizing-the-compilation-process-j4xj2t" data-anchor="_customizing_the_compilation_process">2.10. Customizing the compilation process</h3>
-<div class="paragraph"><p>The Phusion Passenger compilation process can be customized with environment variables. You can learn more about environment variables in <a href="#about_environment_variables">About environment variables</a>.</p></div>
 <div class="sect3">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_setting_the_compiler"></span><h4 data-comment-topic="setting-the-compiler-1fxfulc" data-anchor="_setting_the_compiler">2.10.1. Setting the compiler</h4>
-<div class="paragraph"><p>You can force the Phusion Passenger build system to use a specific C or C++ compiler by setting the <span class="monospaced">CC</span> and <span class="monospaced">CXX</span> environment variables. These may be set to any arbitrary shell commands.</p></div>
-<div class="paragraph"><p>For example, contributors who want to hack on Phusion Passenger may want to use Clang for faster compilation and <a href="http://ccache.samba.org/">ccache</a> for faster recompilation, and may want to enable more error-catching compilation flags:</p></div>
-<div class="listingblock">
-<div class="content">
-<!-- Generator: GNU source-highlight 2.11.1
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt><span style="font-weight: bold"><span style="color: #0000FF">export</span></span> <span style="color: #009900">CC</span><span style="color: #990000">=</span><span style="color: #FF0000">'ccache clang -fcolor-diagnostics -Qunused-arguments -fcatch-undefined-behavior -ftrapv'</span>
-<span style="font-weight: bold"><span style="color: #0000FF">export</span></span> <span style="color: #009900">CXX</span><span style="color: #990000">=</span><span style="color: #FF0000">'ccache clang++ -fcolor-diagnostics -Qunused-arguments -fcatch-undefined-behavior -ftrapv'</span></tt></pre>
-</div>
-</div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="./images/icons/note.png" alt="Note">
-</td>
-<td class="content">If you run the installer with <span class="monospaced">sudo</span> then environment variables may not be passed properly. Learn more at <a href="#env_vars_and_sudo">Environment variables and sudo</a>.</td>
-</tr></table>
-</div>
 </div>
 <div class="sect3">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_adding_additional_compiler_or_linker_flags"></span><h4 data-comment-topic="adding-additional-compiler-or-linker-flags-nxfour" data-anchor="_adding_additional_compiler_or_linker_flags">2.10.2. Adding additional compiler or linker flags</h4>
-<div class="paragraph"><p>On some systems, C/C++ libraries and headers that Phusion Passenger requires may be located in a non-standard directory. You can force the Phusion Passenger build system to look in those locations by injecting compiler and linker flags using the following environment variables:</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<span class="monospaced">EXTRA_PRE_CFLAGS</span>
-</dt>
-<dd>
-<p>
-        These flags are injected into all C compiler invocations that involve compiling C source files. This also covers compiler invocations that compile <strong>and</strong> link. The flags are injected at the beginning of the command string, even before <span class="monospaced">EXTRA_PRE_LDFLAGS</span>.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">EXTRA_CFLAGS</span>
-</dt>
-<dd>
-<p>
-        Similar to <span class="monospaced">EXTRA_PRE_CFLAGS</span>, but injected at the end of the command string, before <span class="monospaced">EXTRA_LDFLAGS</span>.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">EXTRA_PRE_CXXFLAGS</span>
-</dt>
-<dd>
-<p>
-        Similar to <span class="monospaced">EXTRA_PRE_CFLAGS</span>, but for C++ compiler invocations.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">EXTRA_CXXFLAGS</span>
-</dt>
-<dd>
-<p>
-        Similar to <span class="monospaced">EXTRA_CFLAGS</span>, but for C++ compiler invocations.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">EXTRA_PRE_LDFLAGS</span>
-</dt>
-<dd>
-<p>
-        These flags are injected into all C/C++ compiler invocations that involve linking. This includes compiler invocations that compile <strong>and</strong> link. The flags are injected at the beginning of the command string, but after <span class="monospaced">EXTRA_PRE_CFLAGS</span>/<span class="monospaced">EXTRA_PRE_CXXFLAGS</span>.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">EXTRA_PRE_C_LDFLAGS</span>
-</dt>
-<dd>
-<p>
-        These flags are injected into all C compiler invocations that involve linking, right after <span class="monospaced">EXTRA_PRE_LDFLAGS</span>.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">EXTRA_PRE_CXX_LDFLAGS</span>
-</dt>
-<dd>
-<p>
-        Similar to <span class="monospaced">EXTRA_PRE_CXX_LDFLAGS</span>, but for C++ compiler invocations.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">EXTRA_LDFLAGS</span>
-</dt>
-<dd>
-<p>
-        Similar to <span class="monospaced">EXTRA_PRE_LDFLAGS</span>, but injected at the very end of the command string, even after <span class="monospaced">EXTRA_CFLAGS</span> and <span class="monospaced">EXTRA_CXXFLAGS</span>.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">EXTRA_C_LDFLAGS</span>
-</dt>
-<dd>
-<p>
-        Similar to <span class="monospaced">EXTRA_LDFLAGS</span>, but only injected for C executable linking commands. Injected right after <span class="monospaced">EXTRA_LDFLAGS</span>.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">EXTRA_CXX_LDFLAGS</span>
-</dt>
-<dd>
-<p>
-        Similar to <span class="monospaced">EXTRA_LDFLAGS</span>, but only injected for C++ executable linking commands. Injected right after <span class="monospaced">EXTRA_LDFLAGS</span>.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">PASSENGER_THREAD_LOCAL_STORAGE</span>
-</dt>
-<dd>
-<p>
-        Setting this to 1 will enable the <span class="monospaced">PASSENGER_THREAD_LOCAL_STORAGE</span> macro, which forcefully disables the use of thread-local storage inside the Phusion Passenger codebase. Setting this environment variable is useful on systems that have broken support for thread-local storage, despite passing our build system’s check for proper thread-local storage support. At the time of writing, one user has reported that Ubuntu 12.04 32-bit has broken thread-local storage report although neither the reporter nor us were able to reproduce the problem on any other systems running Ubuntu 12.04 32-bit. Note that this flag has no effect on non-Phusion Passenger code.
-</p>
-</dd>
-</dl></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="./images/icons/note.png" alt="Note">
-</td>
-<td class="content">If you run the installer with <span class="monospaced">sudo</span> then environment variables may not be passed properly. Learn more at <a href="#env_vars_and_sudo">Environment variables and sudo</a>.</td>
-</tr></table>
-</div>
 </div>
 <div class="sect3">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="forcing_location_of_command_line_tools_and_dependencies"></span><h4 data-comment-topic="forcing-location-of-command-line-tools-and-dependencies-xajpg1" data-anchor="forcing_location_of_command_line_tools_and_dependencies">2.10.3. Forcing location of command line tools and dependencies</h4>
-<div class="paragraph"><p>The Phusion Passenger build system attempts to autodetect many things by locating relevant helper tools. For example, to find out which compiler flags it should use for compiling Apache modules, it locates the <span class="monospaced">apxs2</span> command and queries it. To find out which compiler flags it should use for libcurl, it queries the <span class="monospaced">curl-config</span> command. These commands may not be in <span class="monospaced">$PATH</span>, or even when they are you may want to use a different one.</p></div>
-<div class="paragraph"><p>You can force the build to find certain command line tools at certain locations by using the following environment variables:</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<span class="monospaced">HTTPD</span>
-</dt>
-<dd>
-<p>
-        The location of the <span class="monospaced">httpd</span> executable (the Apache server executable).
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">APXS2</span>
-</dt>
-<dd>
-<p>
-        The location of the <span class="monospaced">apxs2</span> executable (the Apache module developer tool). Only used by <span class="monospaced">passenger-install-apache2-module</span>.
-</p>
-<div class="paragraph"><p>This environment variable, together with <span class="monospaced">HTTPD</span>, are what you need to customize if you have multiple Apache installations on your system, or if your Apache is located in a non-standard location which Phusion Passenger cannot detect. By setting <span class="monospaced">APXS2</span> and <span class="monospaced">HTTP</span> to the right paths, you can force Phusion Passenger to be compiled against that specific Apache installation.</p></div>
-<div class="paragraph"><p>For example, if your Apache installation is located in <span class="monospaced">/opt/lamp/apache2</span>, then you can run the installer as follows:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>$ sudo bash
-# export HTTPD=/opt/lampp/apache2/bin/apache
-# export APXS2=/opt/lampp/apache2/bin/apxs
-# passenger-install-apache2-module</pre>
-</div>
 </div>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">APR_CONFIG</span>
-</dt>
-<dd>
-<p>
-        The location of the <span class="monospaced">apr-config</span> executable (the Apache Portable Runtime developer tool).
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">APU_CONFIG</span>
-</dt>
-<dd>
-<p>
-        The location of the <span class="monospaced">apu-config</span> executable (the Apache Portable Runtime Utility developer tool).
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">MAKE</span>
-</dt>
-<dd>
-<p>
-        The location of a <span class="monospaced">make</span> tool. It does not matter which implementation of <span class="monospaced">make</span> this is.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">GMAKE</span>
-</dt>
-<dd>
-<p>
-        The location of the GNU-compatible <span class="monospaced">make</span> tool.
-</p>
-</dd>
-</dl></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="./images/icons/tip.png" alt="Tip">
-</td>
-<td class="content">If you do not know what environment variables are, or how to use them, then please read <a href="#env_vars_and_sudo">Environment variables and sudo</a>.</td>
-</tr></table>
 </div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="./images/icons/note.png" alt="Note">
-</td>
-<td class="content">If you run the installer with <span class="monospaced">sudo</span> then environment variables may not be passed properly. Learn more at <a href="#env_vars_and_sudo">Environment variables and sudo</a>.</td>
-</tr></table>
+<div class="sect2">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="uninstalling"></span><h3 data-comment-topic="uninstalling-3hpprb" data-anchor="uninstalling">2.11. Uninstalling</h3>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/install/standalone/uninstall/">https://www.phusionpassenger.com/library/install/standalone/uninstall/</a></p></div>
 </div>
-</div>
-</div>
-<div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="uninstalling"></span><h3 data-comment-topic="uninstalling-3hpprb" data-anchor="uninstalling">2.11. Uninstalling</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-If you installed Phusion Passenger through Homebrew, then run <span class="monospaced">brew uninstall passenger</span>.
-</p>
-</li>
-<li>
-<p>
-If you installed Phusion Passenger via a Ruby gem, then run <span class="monospaced">gem uninstall passenger</span> (or, if you’re a <a href="https://www.phusionpassenger.com/enterprise">Phusion Passenger Enterprise</a> user, <span class="monospaced">gem uninstall passenger-enterprise-server</span>).
-  You <a href="#is_ruby_home_or_system_wide_installed">might have to run this as root</a>.
-</p>
-</li>
-<li>
-<p>
-If you installed Phusion Passenger via a source tarball, then remove the directory
-  in which you placed the extracted Phusion Passenger files. This directory is the
-  same as the one pointed to the by <span class="monospaced">PassengerRoot</span>/<span class="monospaced">passenger_root</span> configuration directive.
-</p>
-</li>
-<li>
-<p>
-If you installed Phusion Passenger through APT or YUM, then use them to uninstall Phusion Passenger.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="moving_phusion_passenger"></span><h3 data-comment-topic="moving-to-a-different-directory-b3lpy1" data-anchor="moving_phusion_passenger">2.12. Moving to a different directory</h3>
-<div class="paragraph"><p>If you installed Phusion Passenger through a tarball then you can move the Phusion Passenger directory to another location. This is not possible if you used any of the other installation methods.</p></div>
-<div class="paragraph"><p>First, move the directory to whereever you like:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>mv /opt/passenger/passenger-4.0.0 /usr/local/passenger-4.0.0</pre>
-</div>
-</div>
-<div class="paragraph"><p>If you used <a href="#tarball_generic_install">the tarball installation method</a> and you added Phusion Passenger’s <span class="monospaced">bin</span> subdirectory to <span class="monospaced">PATH</span>, then you must update your PATH with the new location. Open <span class="monospaced">/etc/bashrc</span> (or <span class="monospaced">/etc/bash.bashrc</span> on some systems) and change:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>export PATH=/opt/passenger/passenger-4.0.0/bin:$PATH</pre>
-</div>
-</div>
-<div class="paragraph"><p>to:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>export PATH=/usr/local/passenger-4.0.0/bin:$PATH</pre>
-</div>
-</div>
-<div class="paragraph"><p>Finally, restart all your shell sessions to activate the PATH change.</p></div>
+<div class="sect2">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="moving_phusion_passenger"></span><h3 data-comment-topic="moving-to-a-different-directory-b3lpy1" data-anchor="moving_phusion_passenger">2.12. Moving to a different directory</h3>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/install/standalone/moving.html">https://www.phusionpassenger.com/library/install/standalone/moving.html</a></p></div>
 </div>
 </div>
 </div>
 <div class="sect1">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_usage"></span><h2 data-comment-topic="usage-1eyt33o" data-anchor="_usage">3. Usage</h2>
 <div class="sectionbody">
-<div class="paragraph"><p>Go to your application’s root directory, and run:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>passenger start</pre>
-</div>
-</div>
+<div class="paragraph"><p>This documentation has moved. Please visit the walkthroughs at <a href="https://www.phusionpassenger.com/library/">https://www.phusionpassenger.com/library/</a> to learn how to use Passenger Standalone. Or visit <a href="https://www.phusionpassenger.com/library/deploy/standalone/deploy/">the new deployment documentation</a>.</p></div>
 </div>
 </div>
 <div class="sect1">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_configuration"></span><h2 data-comment-topic="configuration-10trfau" data-anchor="_configuration">4. Configuration</h2>
 <div class="sectionbody">
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/config/standalone/">https://www.phusionpassenger.com/library/config/standalone/</a></p></div>
 <div class="sect2">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_command_line_options"></span><h3 data-comment-topic="command-line-options-1njv6kt" data-anchor="_command_line_options">4.1. Command line options</h3>
-<div class="paragraph"><p>Most configuration is done by customizing the arguments passed to the <span class="monospaced">passenger</span> command. The most important ones are:</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<span class="monospaced">--port NUMBER</span>
-</dt>
-<dd>
-<p>
-        The port number that Phusion Passenger Standalone should listen on. If not given, port 3000 is assumed.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">--environment NAME</span>
-</dt>
-<dd>
-<p>
-        Customizes the value of the <span class="monospaced">RAILS_ENV</span>, <span class="monospaced">RACK_ENV</span>, <span class="monospaced">WSGI_ENV</span>, <span class="monospaced">NODE_ENV</span> and <span class="monospaced">PASSENGER_APP_ENV</span> environment variables. Some web frameworks, for example Rails and Connect.js, adjust their behavior according to the environment. The default value is <em>development</em>.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">--max-pool-size NUMBER</span>
-</dt>
-<dd>
-<p>
-        The maximum number of application processes to run. The maximum number that you can run depends on the amount of memory your server has. The article <a href="http://blog.phusion.nl/2013/03/12/tuning-phusion-passengers-concurrency-settings/">Tuning Phusion Passenger’s concurrency settings</a> explains how you can infer a good number for this option.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">--min-instances NUMBER</span>
-</dt>
-<dd>
-<p>
-        If you don’t want the number of application processes to scale dynamically, then use this option to set it to a value equal to <span class="monospaced">--max-pool-size</span>.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">--spawn-method NAME</span>
-</dt>
-<dd>
-<p>
-        When set to "smart" (the default), Phusion Passenger preloads your app and utilizes copy-on-write in order to save memory. You can disable this by setting this option to "direct". Preloading is only supported for Ruby apps. For apps written in other languages, it is as if "direct" is always used.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">--friendly-error-pages</span>
-</dt>
-<dd>
-<p>
-    Phusion Passenger can display a friendly error page whenever your application fails to start. The friendly error page presents the startup error message, some suggestions for solving the problem, a backtrace, and a dump of the environment variables. This feature is very useful during application development and useful for less experienced system administrators, but the page might reveal potentially sensitive information, depending on the application. For this reason, friendly error pages are turned off by default when <span class="monospaced">--environment</span> is set to <em>staging</em> or <em>production</em>, but enabled by default otherwise.
-</p>
-<div class="paragraph"><p>You can use <span class="monospaced">--friendly-error-pages</span> and <span class="monospaced">--no-friendly-error-pages</span> to explicitly enable or disable this feature, respectively.</p></div>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">--sticky-sessions</span>
-</dt>
-<dd>
-<p>
-    Enables <a href="Users%20guide%20Nginx.html#PassengerStickySessions">sticky sessions</a>. Required for SockJS, Socket.io, faye-websocket and Meteor JS applications.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">--sticky-sessions-cookie-name NAME</span>
-</dt>
-<dd>
-<p>
-    Allows customizing the sticky session cookie name.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">--ssl</span>
-</dt>
-<dd>
-<p>
-        Enables SSL support. If this is set, you must also set <span class="monospaced">--ssl-certificate</span> and <span class="monospaced">--ssl-certificate-key</span> to the SSL certificate and key files, respectively.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">--ssl-port</span>
-</dt>
-<dd>
-<p>
-        If <span class="monospaced">--ssl</span> is given, and you set this option, then Phusion Passenger Standalone will listen for HTTP on the regular <span class="monospaced">--port</span> number, <strong>as well as</strong> listen for HTTPS on the port you specified with this option. For example:
-</p>
-<div class="listingblock">
-<div class="content monospaced">
-<pre># Listen for HTTP on port 3000, HTTPS on port 3001.
-passenger start --ssl --ssl-certificate ... --ssl-certificate-key ... --ssl-port 3001</pre>
-</div>
-</div>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">--nginx-config-template</span>
-</dt>
-<dd>
-<p>
-        Specifies the Nginx configuration template file to use. See <a href="#advanced_configuration">Advanced configuration</a>.
-</p>
-</dd>
-</dl></div>
-<div class="paragraph"><p>See <span class="monospaced">--help</span> for all available options.</p></div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/config/standalone/reference/">https://www.phusionpassenger.com/library/config/standalone/reference/</a></p></div>
 </div>
 <div class="sect2">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="config_file"></span><h3 data-comment-topic="configuration-file-xng7yp" data-anchor="config_file">4.2. Configuration file</h3>
-<div class="paragraph"><p><strong>Introduced in version 4.0.24.</strong></p></div>
-<div class="paragraph"><p>It is possible to store some options in a configuration file <span class="monospaced">Passengerfile.json</span> in the application directory. Configuration in this file overrides command line options. The configuration file format is JSON.</p></div>
-<div class="paragraph"><p>In case Passenger Standalone is in <a href="#mass_deployment">mass deployment mode</a>, such a configuration file allows customizing options on a per-application basis.</p></div>
-<div class="paragraph"><p>The following configuration options are supported:</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<span class="monospaced">port</span>
-</dt>
-<dd>
-<p>
-        Equivalent to the <span class="monospaced">--port</span> command line option.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">environment</span>
-</dt>
-<dd>
-<p>
-        Equivalent to the <span class="monospaced">--environment</span> command line option.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">max_pool_size</span>
-</dt>
-<dd>
-<p>
-        Equivalent to the <span class="monospaced">--max-pool-size</span> command line option. But when in mass deployment mode, this option in the configuration file has no effect; the command line option should be used to customize this.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">min_instances</span>
-</dt>
-<dd>
-<p>
-        Equivalent to the <span class="monospaced">--min-instances</span> command line option.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">spawn_method</span>
-</dt>
-<dd>
-<p>
-        Equivalent to the <span class="monospaced">--spawn-method</span> command line option.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">sticky_sessions</span>
-</dt>
-<dd>
-<p>
-    Equivalent to the <span class="monospaced">--sticky-sessions</span> command line option.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">sticky_sessions_cookie_name</span>
-</dt>
-<dd>
-<p>
-    Equivalent to the <span class="monospaced">--sticky-sessions-cookie-name</span> command line option.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">ssl</span>
-</dt>
-<dd>
-<p>
-        Equivalent to the <span class="monospaced">--ssl</span> command line option. When given, you must also set <span class="monospaced">ssl_certificate</span> and <span class="monospaced">ssl_certificate_key</span> in the configuration file.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">ssl_port</span>
-</dt>
-<dd>
-<p>
-        Equivalent to the <span class="monospaced">--ssl-port</span> command line option.
-</p>
-<div class="paragraph"><p>When in <a href="#mass_deployment">mass deployment mode</a>, you will probably want to set a different <span class="monospaced">port</span> too. If you don’t, and you end up in a situation in which a port is used for both HTTP and HTTPS traffic, then the builtin Nginx core will abort with an error.</p></div>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">server_names</span> (Enterprise only)
-</dt>
-<dd>
-<p>
-        Only relevant in <a href="#mass_deployment">mass deployment mode</a>. This option specifies which server names (host names) should be routed to this application. This option must be an array of names, e.g. <span class="monospaced">"server_names": ["foo.com", "bar.com"]</span>. By default, the name of the application directory is used as the server name. For example, for an application located in /webapps/foobar.com, "foobar.com" is used as the server name.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">envvars</span> (since 5.0.0 RC 1)
-</dt>
-<dd>
-<p>
-        Environment variables to pass to the application. This option must be a key-value map, e.g. <span class="monospaced">"envvars": { "ADMIN_EMAIL": "root@phusion.nl", "SECRET_KEY": "12345" }</span>.
-</p>
-</dd>
-<dt class="hdlist1">
-<span class="monospaced">nginx_config_template</span>
-</dt>
-<dd>
-<p>
-        Equivalent to the <span class="monospaced">--nginx-config-template</span> command line option.
-</p>
-</dd>
-</dl></div>
-<div class="paragraph"><p>Here is an example configuration file:</p></div>
-<div class="listingblock">
-<div class="content">
-<!-- Generator: GNU source-highlight 2.11.1
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt><span style="color: #FF0000">{</span>
-        <span style="color: #FF0000">"port"</span><span style="color: #990000">:</span> <span style="color: #993399">8000</span><span style="color: #990000">,</span>
-        <span style="color: #FF0000">"environment"</span><span style="color: #990000">:</span> <span style="color: #FF0000">"production"</span><span style="color: #990000">,</span>
-        <span style="color: #FF0000">"ssl"</span><span style="color: #990000">:</span> <span style="font-weight: bold"><span style="color: #0000FF">true</span></span><span style="color: #990000">,</span>
-        <span style="color: #FF0000">"ssl_certificate"</span><span style="color: #990000">:</span> <span style="color: #FF0000">"/path-to-cert.crt"</span><span style="color: #990000">,</span>
-        <span style="color: #FF0000">"ssl_certificate_key"</span><span style="color: #990000">:</span> <span style="color: #FF0000">"/path-to-cert.key"</span>
-<span style="color: #FF0000">}</span></tt></pre>
-</div>
-</div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/config/standalone/reference/">the new configuration reference</a> or <a href="https://www.phusionpassenger.com/library/config/standalone/intro.html">the new configuration introduction document</a>.</p></div>
 </div>
 <div class="sect2">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="advanced_configuration"></span><h3 data-comment-topic="advanced-configuration-e3v4pk" data-anchor="advanced_configuration">4.3. Advanced configuration</h3>
-<div class="paragraph"><p><strong>Introduced in version 4.0.39.</strong></p></div>
-<div class="paragraph"><p>Phusion Passenger Standalone is built on the same technology that powers <a href="Users%20guide%20Nginx.html">Phusion Passenger for Nginx</a>, so any configuration option supported by Phusion Passenger for Nginx can be applied to Standalone as well. You can do this by editing the Standalone configuration template directly.</p></div>
-<div class="paragraph"><p>First, create a copy of the default Phusion Passenger Nginx configuration template file:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>cp $(passenger-config about resourcesdir)/templates/standalone/config.erb nginx.conf.erb</pre>
-</div>
-</div>
-<div class="paragraph"><p>Then open <span class="monospaced">nginx.conf.erb</span> and modify it as you see fit. The file is a normal Nginx configuration file, in the ERB template format.</p></div>
-<div class="paragraph"><p>Every time you start Standalone, you must pass the <span class="monospaced">--nginx-config-template</span> parameter, which tells Standalone to use your specific Nginx configuration template file. For example:</p></div>
-<div class="listingblock">
-<div class="content">
-<!-- Generator: GNU source-highlight 2.11.1
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt>passenger start --nginx-config-template nginx<span style="color: #990000">.</span>conf<span style="color: #990000">.</span>erb</tt></pre>
-</div>
-</div>
-<div class="paragraph"><p>Alternatively, if you don’t want to pass this parameter every time, you can also set the <span class="monospaced">nginx_config_template</span> option in <a href="#config_file">Passengerfile.json</a>.</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="./images/icons/note.png" alt="Note">
-</td>
-<td class="content">The original configuration template file may change from time to time, e.g. because new features are introduced into Phusion Passenger. If your configuration template file does not contain the required changes, then these new features may not work properly. In the worst case, Standalone might even malfunction. Therefore, every time you upgrade Phusion Passenger, you should check whether the original configuration template file has changed, and merge back any changes into your own file.</td>
-</tr></table>
-</div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/config/standalone/intro.html#nginx-configuration-template">https://www.phusionpassenger.com/library/config/standalone/intro.html#nginx-configuration-template</a></p></div>
 </div>
 </div>
 </div>
 <div class="sect1">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_using_passenger_standalone_in_production"></span><h2 data-comment-topic="using-passenger-standalone-in-production-1i7yjcz" data-anchor="_using_passenger_standalone_in_production">5. Using Passenger Standalone in production</h2>
 <div class="sectionbody">
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/deploy/standalone/">https://www.phusionpassenger.com/library/deploy/standalone/</a></p></div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="starting_at_system_boot"></span><h3 data-comment-topic="starting-passenger-standalone-at-system-boot-jpem2b" data-anchor="starting_at_system_boot">5.1. Starting Passenger Standalone at system boot</h3>
-<div class="paragraph"><p>The easiest way to have Passenger Standalone started during system boot is add it to the file <span class="monospaced">/etc/rc.local</span>. This script is called during system boot.</p></div>
-<div class="paragraph"><p>Here’s an example of what you may want to add to <span class="monospaced">/etc/rc.local</span>. If there is an <span class="monospaced">exit</span> command in <span class="monospaced">rc.local</span>, make sure you add these <em>before</em> the <span class="monospaced">exit</span> command.</p></div>
-<div class="listingblock">
-<div class="content">
-<!-- Generator: GNU source-highlight 2.11.1
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt><span style="font-style: italic"><span style="color: #9A1900"># If you installed Phusion Passenger from tarball, add its `bin` directory to PATH.</span></span>
-<span style="font-style: italic"><span style="color: #9A1900">#export PATH=/path-to-passenger/bin:$PATH</span></span>
-
-<span style="font-style: italic"><span style="color: #9A1900"># Change working directory to your webapp.</span></span>
-cd /path-to-your-webapp
-
-<span style="font-style: italic"><span style="color: #9A1900"># Start Passenger Standalone in daemonized mode. Passenger will be started as</span></span>
-<span style="font-style: italic"><span style="color: #9A1900"># root when run from this file, so we also tell it to drop its privileges to a</span></span>
-<span style="font-style: italic"><span style="color: #9A1900"># normal user. Replace 'someusername' with the user you want to run your</span></span>
-<span style="font-style: italic"><span style="color: #9A1900"># application under.</span></span>
-passenger start --daemonize --port <span style="color: #993399">80</span> --user someusername</tt></pre>
-</div>
-</div>
-<div class="paragraph"><p>To stop Passenger Standalone, run:</p></div>
-<div class="listingblock">
-<div class="content">
-<!-- Generator: GNU source-highlight 2.11.1
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt>cd /path-to-your-webapp
-
-<span style="font-style: italic"><span style="color: #9A1900"># If you use RVM, use 'rvmsudo' instead of 'sudo'</span></span>
-sudo passenger stop</tt></pre>
-</div>
-</div>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_starting_passenger_standalone_at_system_boot"></span><h3 data-comment-topic="starting-passenger-standalone-at-system-boot-jpem2b" data-anchor="_starting_passenger_standalone_at_system_boot">5.1. Starting Passenger Standalone at system boot</h3>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/deploy/standalone/deploy/ruby/#step-4-make-sure-passenger-standalone-starts-on-system-boot">https://www.phusionpassenger.com/library/deploy/standalone/deploy/ruby/#step-4-make-sure-passenger-standalone-starts-on-system-boot</a></p></div>
 </div>
 <div class="sect2">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="sharing_port"></span><h3 data-comment-topic="sharing-the-same-port-between-multiple-passenger-standalone-instances-3lcmc5" data-anchor="sharing_port">5.2. Sharing the same port between multiple Passenger Standalone instances</h3>
-<div class="paragraph"><p>If you have multiple applications on your server then it is desirable to have all of them listen on the same port (e.g. port 80), with the HTTP request’s host name determining which Passenger Standalone instance should handle the request. There are three ways to achieve this.</p></div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-The first way is to use the <a href="#mass_deployment">Mass deployment</a> feature, which allows Passenger Standalone to directly host multiple applications at the same time. Please refer to that section to learn more.
-</p>
-</li>
-<li>
-<p>
-The second way is to run multiple Passenger Standalone instances — one for each application — and to put all of them behind a <strong>reverse proxy</strong> or <strong>load balancer</strong>. The reverse proxy/load balancer can for example be Nginx, Apache or HAProxy. The reverse proxy/load balancer listens on port 80, determines which Passenger Standalone instance should handle the request, and forwards the request to that instance.
-</p>
-</li>
-<li>
-<p>
-The third way is to use <a href="Users%20guide%20Nginx.html">Phusion Passenger for Nginx</a> or <a href="Users%20guide%20Apache.html">Phusion Passenger for Apache</a>. These are two modes of Phusion Passenger that are distinct from the Standalone mode, which this document describes. In the Nginx and Apache modes, Phusion Passenger integrates directly into Nginx and Apache, and makes it very easy to host multiple applications directly on Nginx or Apache.
-</p>
-<div class="paragraph"><p>Compared method 2 — putting Passenger Standalone behind a reverse proxy or load balancer — the Nginx or Apache modes are easier to use and require less configuration. On the other hand, the Nginx modes requires reinstalling or recompiling Nginx, while the Apache mode requires that the Phusion Passenger Apache module is installed.</p></div>
-</li>
-</ol></div>
-<div class="paragraph"><p><strong>The rest of this subsection describes method 2.</strong></p></div>
-<span class="anchor_helper" id="_step_1_starting_all_applications"></span><h4 class="float" data-anchor="_step_1_starting_all_applications">Step 1: starting all applications</h4>
-<div class="paragraph"><p>Putting Passenger Standalone behind a reverse proxy requires three steps. First, you must start all Passenger Standalone instances that you want. Each one must be listening on a different port, because two applications can’t listen on the same port. Suppose that you have two applications, <span class="monospaced">/webapps/foo</span> and <span class="monospaced">/webapps/bar</span>. Here’s how you may start them:</p></div>
-<div class="listingblock">
-<div class="content">
-<!-- Generator: GNU source-highlight 2.11.1
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt><span style="font-style: italic"><span style="color: #9A1900"># Start foo on port 4000</span></span>
-cd /webapps/foo
-passenger start --daemonize --address <span style="color: #993399">127.0</span><span style="color: #990000">.</span><span style="color: #993399">0.1</span> --port <span style="color: #993399">4000</span>
-
-<span style="font-style: italic"><span style="color: #9A1900"># Start bar on port 4010</span></span>
-cd /webapps/bar
-passenger start --daemonize --address <span style="color: #993399">127.0</span><span style="color: #990000">.</span><span style="color: #993399">0.1</span> --port <span style="color: #993399">4010</span></tt></pre>
-</div>
-</div>
-<div class="paragraph"><p>Notice the fact that we pass <span class="monospaced">--address 127.0.0.1</span>, which tells Passenger Standalone to only listen for requests that originate from the local machine. This is because the reverse proxy/load balancer, not Passenger Standalone, is supposed to be responsible for receiving external HTTP requests. The reverse proxy/load balancer will be running on the same machine only, so limiting Passenger Standalone in this manner improves security.</p></div>
-<span class="anchor_helper" id="_step_2_install_and_configure_the_reverse_proxy_load_balancer"></span><h4 class="float" data-anchor="_step_2_install_and_configure_the_reverse_proxy_load_balancer">Step 2: install and configure the reverse proxy/load balancer</h4>
-<div class="paragraph"><p>The next step is to <strong>install a reverse proxy/load balancer</strong>, and to <strong>configure</strong> it to do the following:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-To listen on port 80.
-</p>
-</li>
-<li>
-<p>
-To forward requests to either <em>foo</em> or <em>bar</em>, depending on the request’s HTTP host name.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>You can use any reverse proxy/load balancer you want, but we’re going to show an example using <a href="http://www.nginx.org/">Nginx</a> because it’s a pretty popular choice. Install Nginx as follows:</p></div>
-<table class="tableblock frame-all grid-all" style="
-width:100%;
-">
-<col style="width:50%;">
-<col style="width:50%;">
-<tbody>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Debian, Ubuntu</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock"><span class="monospaced">sudo apt-get update</span><br>
-<span class="monospaced">sudo apt-get install nginx-extras</span></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Red Hat, CentOS, ScientificLinux, Amazon Linux</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Enable <a href="http://fedoraproject.org/wiki/EPEL">EPEL</a>, then run as root:<br>
-<span class="monospaced">yum install nginx</span></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Mac OS X (Homebrew)</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock"><span class="monospaced">brew install nginx</span></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Other operating systems</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Install Nginx from <a href="http://www.nginx.org/">the Nginx website</a>.</p></td>
-</tr>
-</tbody>
-</table>
-<div class="paragraph"><p>Open the Nginx configuration file:</p></div>
-<table class="tableblock frame-all grid-all" style="
-width:100%;
-">
-<col style="width:50%;">
-<col style="width:50%;">
-<tbody>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Debian, Ubuntu</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock"><span class="monospaced">/etc/nginx/nginx.conf</span></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Red Hat, CentOS, ScientificLinux, Amazon Linux</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock"><span class="monospaced">/etc/nginx/nginx.conf</span></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Mac OS X (Homebrew)</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock"><span class="monospaced">/usr/local/etc/nginx/nginx.conf</span></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Other operating systems</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">It depends on how you installed Nginx, but it’s usually <span class="monospaced">$PREFIX/conf/nginx.conf</span>, where <span class="monospaced">$PREFIX</span> is the prefix you installed Nginx to.</p></td>
-</tr>
-</tbody>
-</table>
-<div class="paragraph"><p>Add virtual host entries for your applications foo and bar. While making the virtual host entries, you must determine what host names foo and bar should respond to. Let’s say that foo should respond to <em>www.foo.com</em> and bar should respond to <em>www.bar.com</em>. Then the following entries will tell Nginx to listen on port 80, and to handle requests for the domains <em>www.foo.com</em> and <em>www.bar.com</em> differently.</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>http {
-    ...
-
-    # These are some "magic" Nginx configuration options that aid in making
-    # WebSockets work properly with Passenger Standalone. Please learn more
-    # at http://nginx.org/en/docs/http/websocket.html
-    map $http_upgrade $connection_upgrade {
-        default upgrade;
-        ''      close;
-    }
-
-    server {
-        listen 80;
-        server_name www.foo.com;
-
-        # Tells Nginx to serve static assets from this directory.
-        root /webapps/foo/public;
-
-        location / {
-            # Tells Nginx to forward all requests for www.foo.com
-            # to the Passenger Standalone instance listening on port 4000.
-            proxy_pass http://127.0.0.1:4000;
-
-            # These are "magic" Nginx configuration options that
-            # should be present in order to make the reverse proxying
-            # work properly. Also contains some options that make WebSockets
-            # work properly with Passenger Standalone. Please learn more at
-            # http://nginx.org/en/docs/http/ngx_http_proxy_module.html
-            proxy_http_version 1.1;
-            proxy_set_header Host $http_host;
-            proxy_set_header Upgrade $http_upgrade;
-            proxy_set_header Connection $connection_upgrade;
-            proxy_buffering off;
-        }
-    }
-
-    # We handle bar in a similar manner.
-    server {
-        listen 80;
-        server_name www.bar.com;
-
-        root /webapps/bar/public;
-
-        location / {
-            # bar is listening on port 4010 instead of 4000, we
-            # change the URL here.
-            proxy_pass http://127.0.0.1:4010;
-
-            proxy_http_version 1.1;
-            proxy_set_header Host $http_host;
-            proxy_set_header Upgrade $http_upgrade;
-            proxy_set_header Connection $connection_upgrade;
-            proxy_buffering off;
-        }
-    }
-}</pre>
-</div>
-</div>
-<div class="paragraph"><p>Once you’re done editing the Nginx configuration file, restart Nginx:</p></div>
-<table class="tableblock frame-all grid-all" style="
-width:100%;
-">
-<col style="width:50%;">
-<col style="width:50%;">
-<tbody>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Debian, Ubuntu</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock"><span class="monospaced">sudo /etc/init.d/nginx restart</span></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Red Hat, CentOS, ScientificLinux, Amazon Linux</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock"><span class="monospaced">sudo service nginx restart</span></p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Mac OS X (Homebrew)</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">1. Run <span class="monospaced">sudo kill $(cat /usr/local/var/run/nginx.pid)</span><br>
- 2. You you installed the Nginx launchd plist that Homebrew provides (see <span class="monospaced">brew info nginx</span> to learn more), then you don’t have to do anything, and launchd will automatically restart Nginx. Otherwise, you have to manually start Nginx again: <span class="monospaced">sudo /usr/local/bin/nginx</span>.</p></td>
-</tr>
-<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Other operating systems</p></td>
-<td class="tableblock halign-left valign-top">
-<p class="tableblock">It depends on how you installed Nginx, but it’s usually as follows:</p>
-<p class="tableblock"> 1. Lookup the PID of the Nginx master process using <span class="monospaced">ps aux</span>.<br>
- 2. Run <span class="monospaced">sudo kill &lt;PID&gt;</span><br>
- 3. Start Nginx again: <span class="monospaced">sudo $PREFIX/sbin/nginx</span>, where <span class="monospaced">$PREFIX</span> is the prefix you installed Nginx to.</p>
-</td>
-</tr>
-</tbody>
-</table>
-<span class="anchor_helper" id="_step_3_testing"></span><h4 class="float" data-anchor="_step_3_testing">Step 3: testing</h4>
-<div class="paragraph"><p>Nginx should now be listening on port 80, and should forward requests to foo and bar respectively. Let’s test it out by accessing <a href="http://www.foo.com">http://www.foo.com</a> and <a href="http://www.bar.com">http://www.bar.com</a>. But first, we need to ensure that any requests to <em>www.foo.com</em> and <em>www.bar.com</em>, that originate from the local machine, actually end up at the local host, and not at the IP address specified in the DNS records. To do this, edit <span class="monospaced">/etc/hosts</span> and add:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>127.0.0.1  www.foo.com www.bar.com</pre>
-</div>
-</div>
-<div class="paragraph"><p>Now visit <a href="http://www.foo.com">http://www.foo.com</a> and <a href="http://www.bar.com">http://www.bar.com</a>, and verify that it works.</p></div>
-<span class="anchor_helper" id="_step_4_making_all_apps_start_at_system_boot"></span><h4 class="float" data-anchor="_step_4_making_all_apps_start_at_system_boot">Step 4: making all apps start at system boot</h4>
-<div class="paragraph"><p>Once you restart the server, the reverse proxy/load balancer will no longer be able to serve <em>www.foo.com</em> or <em>www.bar.com</em> because the Passenger Standalone instances that host them are no longer running. You must therefore configure the system to start Passenger Standalone at system boot. Please refer to <a href="#starting_at_system_boot">Starting Passenger Standalone at system boot</a> for more information.</p></div>
-<div class="paragraph"><p>For example, you can put this in <span class="monospaced">/etc/rc.local</span> to make the system start foo and bar at system boot:</p></div>
-<div class="listingblock">
-<div class="content">
-<!-- Generator: GNU source-highlight 2.11.1
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt><span style="font-style: italic"><span style="color: #9A1900"># If you installed Phusion Passenger from tarball, add its `bin` directory to PATH.</span></span>
-<span style="font-style: italic"><span style="color: #9A1900">#export PATH=/path-to-passenger/bin:$PATH</span></span>
-
-cd /webapps/foo
-passenger start --daemonize --port <span style="color: #993399">4000</span> --user someusername1
-
-cd /webapps/bar
-passenger start --daemonize --port <span style="color: #993399">4010</span> --user someusername2</tt></pre>
-</div>
-</div>
-<span class="anchor_helper" id="_step_5_wrapping_up"></span><h4 class="float" data-anchor="_step_5_wrapping_up">Step 5: wrapping up</h4>
-<div class="paragraph"><p>Edit <span class="monospaced">/etc/hosts</span> and remove the entry that you added in step 3.</p></div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/deploy/standalone/reverse_proxy.html">https://www.phusionpassenger.com/library/deploy/standalone/reverse_proxy.html</a></p></div>
 </div>
 <div class="sect2">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_installing_passenger_standalone_behind_nginx"></span><h3 data-comment-topic="installing-passenger-standalone-behind-nginx-1xylsfk" data-anchor="_installing_passenger_standalone_behind_nginx">5.3. Installing Passenger Standalone behind Nginx</h3>
-<div class="paragraph"><p>This is described in <a href="#sharing_port">Sharing the same port between multiple Passenger Standalone instances</a>.</p></div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/deploy/standalone/reverse_proxy.html">https://www.phusionpassenger.com/library/deploy/standalone/reverse_proxy.html</a></p></div>
 </div>
 </div>
 </div>
 <div class="sect1">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="mass_deployment"></span><h2 data-comment-topic="mass-deployment-1xqriy4" data-anchor="mass_deployment">6. Mass deployment</h2>
 <div class="sectionbody">
-<div class="paragraph"><p><strong>This feature is only available in <a href="https://www.phusionpassenger.com/enterprise">Phusion Passenger Enterprise</a>. It was introduced in version 3.0.0. <a href="https://www.phusionpassenger.com/download">Buy Phusion Passenger Enterprise here.</a></strong></p></div>
-<div class="paragraph"><p>Mass deployment is a special mode in Phusion Passenger Standalone that allows you to deploy multiple web applications without having to create configuration entries for each one of them. Given a directory with multiple web applications, Passenger Standalone will automatically give each web application its own virtual host entry, and serve all of them from a single server. The virtual host’s server name is equal to the web application’s directory name. Whenever a new web application is added or removed, Passenger Standalone automatically reconfigures itself without administrator intervention. This makes the mass deployment mode especially useful when there are a large number of web applications.</p></div>
-<div class="paragraph"><p>For example, suppose we have a directory <span class="monospaced">/webapps</span> with three web applications: Ruby app, a Python app and a Node.js app.</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>/webapps
-  |
-  +-- rubyapp.com
-  |    |
-  |    +-- config.ru
-  |
-  +-- pythonapp.com
-  |    |
-  |    +-- passenger_wsgi.py
-  |
-  +-- nodeapp.com
-       |
-       +-- app.js</pre>
-</div>
-</div>
-<div class="paragraph"><p>You can activate Passenger Standalone in mass deployment mode by changing the working directory to <span class="monospaced">/webapps</span> and running <span class="monospaced">passenger start</span>:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>$ cd /webapps
-$ passenger start
-=============== Phusion Passenger Standalone web server started ===============
-PID file: /webapps/passenger.3000.pid
-Log file: /webapps/passenger.3000.log
-Environment: development
-
-Serving these applications on 0.0.0.0 port 3000:
- Host name                     Directory
-.-----------------------------------------------------------
- rubyapp.com                   /webapps/rubyapp.com
- pythonapp.com                 /webapps/pythonapp.com
- nodeapp.com                   /webapps/nodeapp.com
-.-----------------------------------------------------------</pre>
-</div>
-</div>
-<div class="paragraph"><p>If you for example remove <span class="monospaced">/webapps/rubyapp.com</span>, Passenger Standalone will reconfigure itself without that web application. Or if you add a new web applications <span class="monospaced">/webapps/newapp.org</span>, Passenger Standalone will reconfigure itself with that web application.</p></div>
-<div class="paragraph"><p>Any options that you pass to the <span class="monospaced">passenger</span> command will affect all deployed web applications. It is also possible to change options on a per-application basis through the use of <a href="#config_file">a <span class="monospaced">Passengerfile.json</span> file inside each application’s directory</a>.</p></div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/deploy/standalone/mass_deployment.html">https://www.phusionpassenger.com/library/deploy/standalone/mass_deployment.html</a></p></div>
 </div>
 </div>
 <div class="sect1">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="troubleshooting"></span><h2 data-comment-topic="troubleshooting-o7g75o" data-anchor="troubleshooting">7. Troubleshooting</h2>
 <div class="sectionbody">
-<div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_generic_troubleshooting_tips"></span><h3 data-comment-topic="generic-troubleshooting-tips-2vokcr" data-anchor="_generic_troubleshooting_tips">7.1. Generic troubleshooting tips</h3>
-<div class="paragraph"><p>One of the first things you should do upon encountering a problem, is to check
-Phusion Passenger Standalone log file. This is typically located in <span class="monospaced">log/passenger.[PORT NUMBER].log</span>. Most problems are logged to this log file.</p></div>
-<div class="paragraph"><p>If neither the logs nor this troubleshooting guide can help you, then please check out our <a href="#where_to_get_support">support resources</a>.</p></div>
-</div>
-<div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_upon_uploading_a_file_phusion_passenger_reports_client_body_temp_00000000xx_failed_2_no_such_file_or_directory"></span><h3 data-comment-topic="upon-uploading-a-file-phusion-passenger-reports-client-body-temp-00000000xx-failed-2-no-such-file-or-directory--d01goe" data-anchor="_upon_uploading_a_file_phusion_passenger_reports_client_body_temp_00000000xx_failed_2_no_such_file_or_directory">7.2. Upon uploading a file, Phusion Passenger reports "client_body_temp/00000000xx failed (2: No such file or directory)"</h3>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<strong>Symptoms</strong>
-</dt>
-<dd>
-<p>
-        When performing an HTTP POST call, the request sometimes fails, with Phusion Passenger reporting an error along the lines of:
-</p>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>/tmp/passenger-standalone.8583/client_body_temp/0000000022" failed (2: No such
-file or directory), client: 127.0.0.1, server: www.foo.com</pre>
-</div>
-</div>
-</dd>
-<dt class="hdlist1">
-<strong>Cause</strong>
-</dt>
-<dd>
-<p>
-        Phusion Passenger buffers HTTP POST bodies (file uploads) to a temporary directory, by default <span class="monospaced">/tmp/passenger-standalone.xxx</span>. This error means that Phusion Passenger that that directory has been removed, probably by some other program.
-</p>
-</dd>
-<dt class="hdlist1">
-<strong>Solution</strong>
-</dt>
-<dd>
-<p>
-        Tell Phusion Passenger to use a different directory to store its temporary files passing the <span class="monospaced">--temp-dir</span> command line option. For example:
-</p>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>mkdir $HOME/tmp
-cd /path-to-your-app
-passenger start --temp-dir=$HOME/tmp</pre>
-</div>
-</div>
-</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_i_get_command_not_found_when_running_a_phusion_passenger_command_through_sudo"></span><h3 data-comment-topic="i-get-command-not-found-when-running-a-phusion-passenger-command-through-sudo-14k8kde" data-anchor="_i_get_command_not_found_when_running_a_phusion_passenger_command_through_sudo">7.3. I get "command not found" when running a Phusion Passenger command through sudo</h3>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<strong>Symptoms</strong>
-</dt>
-<dd>
-<p>
-        Phusion Passenger commands can be found as a normal user, but not when run through sudo:
-</p>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>$ passenger-status
-...some output, but no "command not found" error...
-$ passenger-install-apache2-module
-...some output, but no "command not found" error...
-$ sudo passenger-status
-sudo: passenger-status: command not found
-$ sudo passenger-install-apache2-module
-sudo: passenger-install-apache2-module: command not found</pre>
-</div>
-</div>
-</dd>
-<dt class="hdlist1">
-<strong>Cause</strong>
-</dt>
-<dd>
-<p>
-        The operating system looks up commands using <a href="#the_path_env_var">the PATH environment variable</a>. However, sudo resets all environment variables to a default value, dictated by sudo. If Phusion Passenger was installed to a location that is not in the default sudo PATH value, then sudo will not be able to find the Phusion Passenger commands.
-</p>
-<div class="paragraph"><p>In addition, if you installed Phusion Passenger using a Ruby interpreter that was installed through RVM, then you <strong>must</strong> use rvmsudo instead of sudo. As a rule, when you’re an RVM user, always use rvmsudo instead of sudo.</p></div>
-</dd>
-<dt class="hdlist1">
-<strong>Solution</strong>
-</dt>
-<dd>
-<p>
-        Execute the command using its full path. You can use <span class="monospaced">which</span> as a normal user to lookup the full path:
-</p>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>$ which passenger-status
-/somewhere/bin/passenger-status</pre>
-</div>
-</div>
-<div class="paragraph"><p>Next, run full path of the command using either sudo or rvmsudo:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>$ sudo /somewhere/bin/passenger-status
-
-# -OR, if you're using RVM:-
-
-$ rvmsudo /somewhere/bin/passenger-status</pre>
-</div>
-</div>
-</dd>
-<dt class="hdlist1">
-<strong>Recommended reading</strong>
-</dt>
-<dd>
-<p>
-        When using sudo, you will probably run into similar "command not found" issues in the future, with components other than Phusion Passenger. We <strong>strongly recommend</strong> you to <a href="#about_environment_variables">learn about environment variables</a> so that you know what to do in the future.
-</p>
-</dd>
-</dl></div>
-</div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/admin/standalone/">https://www.phusionpassenger.com/library/admin/standalone/</a></p></div>
 </div>
 </div>
 <div class="sect1">
@@ -2985,141 +1350,11 @@ $ rvmsudo /somewhere/bin/passenger-status</pre>
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="relationship_with_ruby"></span><h3 data-comment-topic="phusion-passenger-and-its-relationship-with-ruby-1usvd0o" data-anchor="relationship_with_ruby">8.1. Phusion Passenger and its relationship with Ruby</h3>
 <div class="sect3">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_how_ruby_is_used"></span><h4 data-comment-topic="how-ruby-is-used-1saha86" data-anchor="_how_ruby_is_used">8.1.1. How Ruby is used</h4>
-<div class="paragraph"><p>Phusion Passenger’s core is written in C++ for performance and memory efficiency. It supports web applications written in any language. Phusion Passenger requires Ruby, its usage of Ruby is minimal in order to maximize performance and to minimize memory usage.</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Phusion Passenger’s installer, build system and administration tools are written in Ruby.
-</p>
-</li>
-<li>
-<p>
-Certain internally used tools, such as the crash handler (which generates a backtrace in case Phusion Passenger crash) and the prespawn script (used to implement
-<a href="#PassengerPreStart">passenger_pre_start</a>)
-are written in Ruby as well.
-</p>
-</li>
-<li>
-<p>
-Ruby web application support is implemented in Ruby.
-</p>
-</li>
-<li>
-<p>
-If you use <a href="#flying_passenger">Flying Passenger</a>, then the Flying Passenger daemon is written in Ruby. The daemon is a small (less than 500 lines of code) and offloads most tasks to the C++ core.
-</p>
-</li>
-<li>
-<p>
-If you use <a href="Users%20guide%20Standalone.html">Phusion Passenger Standalone</a>, then the frontend (the <span class="monospaced">passenger</span> command) is written in Ruby. The frontend is small (less than 1500 lines of code) and offloads most tasks to the C++ core.
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Other than the aforementioned aspects, Phusion Passenger does not use Ruby during normal operation. For example, if you run Python WSGI web applications on Phusion Passenger, then there will be (almost) no Ruby code running on the system.</p></div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/indepth/lightweight_ruby_dependency.html">https://www.phusionpassenger.com/library/indepth/lightweight_ruby_dependency.html</a></p></div>
 </div>
 <div class="sect3">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_when_the_system_has_multiple_ruby_interpreters"></span><h4 data-comment-topic="when-the-system-has-multiple-ruby-interpreters-acf6d" data-anchor="_when_the_system_has_multiple_ruby_interpreters">8.1.2. When the system has multiple Ruby interpreters</h4>
-<div class="paragraph"><p>Phusion Passenger may be installed with any Ruby interpreter. Once installed, you can run Phusion Passenger’s Ruby parts under any Ruby interpreter you want, even if that Ruby interpreter was not the one you originally installed Phusion Passenger with.</p></div>
-<div class="paragraph"><p>The reason for this is that Phusion Passenger does not dynamically link to Ruby: Phusion Passenger uses Ruby entirely out-of-process. Thus you can switch to any Ruby interpreter you want during runtime, without recompiling Phusion Passenger, and without worrying about what Ruby you used to install Phusion Passenger.</p></div>
-<div class="paragraph"><p>Phusion Passenger is also capable of running Ruby web applications under any Ruby interpreter you want. So it is not important which Ruby you use to install Phusion Passenger: it will work regardless. Please refer to the documentation for the
-<a href="#PassengerRuby">passenger_ruby</a>
-directive to learn how run different web applications under different Ruby interpreters.</p></div>
-<div class="paragraph">
-<div class="title">Caveat: RVM and RVM gemsets</div>
-<p>There is however one caveat if you happen to be using RVM or RVM gemsets. When you <span class="monospaced">gem install</span> Phusion Passenger using RVM, then RVM will install Phusion Passenger into the <strong>currently active RVM Ruby and gemset</strong>. This means that Phusion Passenger commands - such as <span class="monospaced">passenger</span>, <span class="monospaced">passenger-install-xxx-module</span> and <span class="monospaced">passenger-status</span> - are available in that same RVM Ruby and gemset only. When you switch Ruby interpreter, or when you switch gemset, the Phusion Passenger commands will no longer be available, and you will get a <span class="monospaced">command not found</span> error. Here’s an example which demonstrates the problem.</p>
-</div>
-<div class="listingblock">
-<div class="title">"Command not found" problem demonstration</div>
-<div class="content">
-<!-- Generator: GNU source-highlight 2.11.1
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt><span style="font-style: italic"><span style="color: #9A1900">## Install Phusion Passenger (open source edition) using Ruby 1.9.3</span></span>
-<span style="font-style: italic"><span style="color: #9A1900">## and the 'business' gemset</span></span>
-$ rvm use <span style="color: #993399">1.9</span><span style="color: #990000">.</span><span style="color: #993399">3</span>
-Using /home/phusion<span style="color: #990000">/.</span>rvm/gems/ruby-<span style="color: #993399">1.9</span><span style="color: #990000">.</span><span style="color: #993399">3</span>-p<span style="color: #993399">429</span>
-$ rvm gemset create business
-$ rvm gemset use business
-Using ruby-<span style="color: #993399">1.9</span><span style="color: #990000">.</span><span style="color: #993399">3</span>-p<span style="color: #993399">429</span> with gemset business
-$ curl -O https<span style="color: #990000">:</span>//s<span style="color: #993399">3</span><span style="color: #990000">.</span>amazonaws<span style="color: #990000">.</span>com/phusion-passenger/releases/gem_bootstrap<span style="color: #990000">.</span>sh
-$ <span style="font-weight: bold"><span style="color: #0000FF">eval</span></span> <span style="color: #FF0000">"`sh gem_bootstrap.sh`"</span>
-$ gem install passenger
-
-<span style="font-style: italic"><span style="color: #9A1900">## Verify that passenger works</span></span>
-$ passenger --version
-Phusion Passenger version <span style="color: #993399">4.0</span><span style="color: #990000">.</span><span style="color: #993399">14</span>
-
-<span style="font-style: italic"><span style="color: #9A1900">## Switch to a different RVM gemset. You will get a `command not found`</span></span>
-$ rvm gemset use default
-Using ruby-<span style="color: #993399">1.9</span><span style="color: #990000">.</span><span style="color: #993399">3</span>-p<span style="color: #993399">429</span> with gemset default
-$ passenger --version
-bash<span style="color: #990000">:</span> passenger<span style="color: #990000">:</span> <span style="font-weight: bold"><span style="color: #0000FF">command</span></span> not found
-
-<span style="font-style: italic"><span style="color: #9A1900">## Switch to a different Ruby interpreter. You will also get</span></span>
-<span style="font-style: italic"><span style="color: #9A1900">## a `command not found`</span></span>
-$ rvm use <span style="color: #993399">2.0</span><span style="color: #990000">.</span><span style="color: #993399">0</span>
-Using /home/phusion<span style="color: #990000">/.</span>rvm/gems/ruby-<span style="color: #993399">2.0</span><span style="color: #990000">.</span><span style="color: #993399">0</span>-p<span style="color: #993399">195</span>
-$ passenger --version
-bash<span style="color: #990000">:</span> passenger<span style="color: #990000">:</span> <span style="font-weight: bold"><span style="color: #0000FF">command</span></span> not found
-
-<span style="font-style: italic"><span style="color: #9A1900">## Switch back to the Ruby and gemset that you installed Phusion</span></span>
-<span style="font-style: italic"><span style="color: #9A1900">## Passenger with, and verify that it works again</span></span>
-$ rvm use <span style="color: #993399">1.9</span><span style="color: #990000">.</span><span style="color: #993399">3</span>
-Using /home/phusion<span style="color: #990000">/.</span>rvm/gems/ruby-<span style="color: #993399">2.0</span><span style="color: #990000">.</span><span style="color: #993399">0</span>-p<span style="color: #993399">195</span>
-$ rvm gemset use business
-Using ruby-<span style="color: #993399">1.9</span><span style="color: #990000">.</span><span style="color: #993399">3</span>-p<span style="color: #993399">429</span> with gemset business
-$ passenger --version
-Phusion Passenger version <span style="color: #993399">4.0</span><span style="color: #990000">.</span><span style="color: #993399">14</span></tt></pre>
-</div>
-</div>
-<div class="paragraph">
-<div class="title">Solutions</div>
-<p>There are several ways to solve this problem:</p>
-</div>
-<div class="olist arabic"><ol class="arabic">
-<li>
-<p>
-Permanently add Phusion Passenger’s command directory to your PATH, so that your shell can always find them even when you switch RVM Ruby or gemset. If you don’t know what PATH means, please read <a href="#about_environment_variable">About environment variables</a> first.
-</p>
-<div class="paragraph"><p>The drawback is that you have to redo this every time you upgrade Phusion Passenger, because the Phusion Passenger directory filename is dependent on the version number.</p></div>
-<div class="paragraph"><p>First, identify the location of the Phusion Passenger command directory, like this:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>$ echo `passenger-config --root`/bin
-/home/phusion/.rvm/gems/ruby-1.9.3-p429/gems/passenger-4.0.15/bin</pre>
-</div>
-</div>
-<div class="paragraph"><p>Next, add the directory that you’ve found to your current shell’s PATH:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>$ export PATH=/home/phusion/.rvm/gems/ruby-1.9.3-p429/gems/passenger-4.0.15/bin:$PATH</pre>
-</div>
-</div>
-<div class="paragraph"><p>Finally, make the change permanent by appending the above command to your bash startup file:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>$ echo 'export PATH=/home/phusion/.rvm/gems/ruby-1.9.3-p429/gems/passenger-4.0.15/bin:$PATH' &gt;&gt; ~/.bashrc</pre>
-</div>
-</div>
-</li>
-<li>
-<p>
-Switch back to the RVM Ruby and gemset that you installed Phusion Passenger with, before running any Phusion Passenger command.
-</p>
-</li>
-<li>
-<p>
-Prepend any Phusion Passenger command with <span class="monospaced">rvm-exec RUBY_NAME@GEMSET_NAME ruby -S</span>. If the relevant Phusion Passenger command also needs root privileges, then prepend <span class="monospaced">rvmsudo</span> before that. For example:
-</p>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>rvm-exec 1.9.3@business ruby -S passenger --version
-rvmsudo rvm-exec 1.9.3@business ruby -S passenger-install-apache2-module</pre>
-</div>
-</div>
-</li>
-</ol></div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/indepth/ruby/multiple_rubies.html">https://www.phusionpassenger.com/library/indepth/ruby/multiple_rubies.html</a></p></div>
 </div>
 </div>
 </div>
@@ -3127,411 +1362,46 @@ rvmsudo rvm-exec 1.9.3@business ruby -S passenger-install-apache2-module</pre>
 <div class="sect1">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="about_environment_variables"></span><h2 data-comment-topic="appendix-about-environment-variables-1ct91x3" data-anchor="about_environment_variables">9. Appendix: About environment variables</h2>
 <div class="sectionbody">
-<div class="paragraph"><p>Environment variables are named values that affect how the system works. For example they tell the system where to look for commands (the <span class="monospaced">PATH</span> variable) or where to look for libraries (<span class="monospaced">LD_LIBRARY_PATH</span>). Their names are often in all-uppercase. Sometimes people refer to an environment variable with a dollar sign <span class="monospaced">$</span> in front, but that’s the same thing: when people say "the $PATH environment variable" they mean "the PATH environment variable". This is because the dollar sign <span class="monospaced">$</span> is a shell syntax for refering to an environment variable, as you will learn later.</p></div>
-<div class="paragraph"><p>Environment variables are set on a <strong>per-process</strong> basis, but they are <strong>inherited</strong> by child processes. This means that if you set environment variables in process A, another already running process B will not see these new environment variables. But if A spawns a child process C, then C will have all environment variables that A had. If you once again change the environment variables in A, then C will not see the changes.</p></div>
-<div class="paragraph"><p>The per-process nature of environment variables some implications. When you set environment variables in your <span class="monospaced">bashrc</span> or other bash startup files…</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-…only newly spawned bash shells see them.
-</p>
-</li>
-<li>
-<p>
-…the web server usually does not see them, because the web server tends to be started from init scripts, not from bash.
-</p>
-</li>
-<li>
-<p>
-…cron jobs do not see them, because cron jobs' environment variables are entirely dictated by their crontabs.
-</p>
-</li>
-</ul></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="./images/icons/note.png" alt="Note">
-</td>
-<td class="content">Because this chapter is meant for beginners, it assumes that the reader uses the bash shell. This chapter does not describe instructions for zsh, csh or other shells. We assume that users of other shells are familiar with the Bourne shell syntax, and know how to apply the instructions in this chapter in their shells' native syntaxes.</td>
-</tr></table>
-</div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/indepth/environment_variables.html">https://www.phusionpassenger.com/library/indepth/environment_variables.html</a></p></div>
 <div class="sect2">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_working_with_environment_variables"></span><h3 data-comment-topic="working-with-environment-variables-11cmwlv" data-anchor="_working_with_environment_variables">9.1. Working with environment variables</h3>
-<div class="paragraph"><p>You can see all environment variables in your shell by running the following command:</p></div>
-<div class="listingblock">
-<div class="content">
-<!-- Generator: GNU source-highlight 2.11.1
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt>env</tt></pre>
-</div>
-</div>
-<div class="paragraph"><p>You can set an evironment variable with the syntax <span class="monospaced">export &lt;NAME&gt;=&lt;VALUE&gt;</span>. For example, to set the <span class="monospaced">APXS2</span> variable to the value <span class="monospaced">/usr/sbin/apxs2</span>:</p></div>
-<div class="listingblock">
-<div class="content">
-<!-- Generator: GNU source-highlight 2.11.1
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt><span style="font-weight: bold"><span style="color: #0000FF">export</span></span> <span style="color: #009900">APXS2</span><span style="color: #990000">=</span>/usr/sbin/apxs<span style="color: #993399">2</span></tt></pre>
-</div>
-</div>
-<div class="paragraph"><p>Any process that you run from your shell from that point on will have said environment variable:</p></div>
-<div class="listingblock">
-<div class="content">
-<!-- Generator: GNU source-highlight 2.11.1
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt><span style="font-weight: bold"><span style="color: #0000FF">export</span></span> <span style="color: #009900">APXS2</span><span style="color: #990000">=</span>/usr/sbin/apxs<span style="color: #993399">2</span>
-ruby -e <span style="color: #FF0000">'p ENV["APXS2"]'</span>
-<span style="font-style: italic"><span style="color: #9A1900"># =&gt; "/usr/sbin/apxs2"</span></span></tt></pre>
-</div>
-</div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="./images/icons/note.png" alt="Note">
-</td>
-<td class="content">
-<div class="title">The "export" keyword is important</div>
-<div class="paragraph"><p>You <strong>must</strong> set the <span class="monospaced">export</span> keyword. If you omit the <span class="monospaced">export</span> keyword then the environment variable will not be visible to other processes:</p></div>
-<div class="listingblock">
-<div class="content">
-<!-- Generator: GNU source-highlight 2.11.1
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt><span style="color: #009900">APXS2</span><span style="color: #990000">=</span>/usr/sbin/apxs<span style="color: #993399">2</span>
-ruby -e <span style="color: #FF0000">'p ENV["APXS2"]'</span>
-<span style="font-style: italic"><span style="color: #9A1900"># =&gt; nil</span></span></tt></pre>
-</div>
-</div>
-</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>You can reference an environment variable in your shell by typing the <span class="monospaced">$</span> sign followed by the environment variable’s name. For example, to see the value of the <span class="monospaced">PATH</span> variable:</p></div>
-<div class="listingblock">
-<div class="content">
-<!-- Generator: GNU source-highlight 2.11.1
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt>echo <span style="color: #009900">$PATH</span></tt></pre>
-</div>
-</div>
-<div class="paragraph"><p>You can also use this trick to extend the value of an environment variable:</p></div>
-<div class="listingblock">
-<div class="content">
-<!-- Generator: GNU source-highlight 2.11.1
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt><span style="font-weight: bold"><span style="color: #0000FF">export</span></span> <span style="color: #009900">PATH</span><span style="color: #990000">=</span>/usr/bin
-
-<span style="font-style: italic"><span style="color: #9A1900"># Prepends '/opt/local/bin', so that it becomes /opt/local/bin:/usr/bin</span></span>
-<span style="font-weight: bold"><span style="color: #0000FF">export</span></span> <span style="color: #009900">PATH</span><span style="color: #990000">=</span>/opt/local/bin<span style="color: #990000">:</span><span style="color: #009900">$PATH</span>
-<span style="font-style: italic"><span style="color: #9A1900"># Appends '/usr/local/bin', so that it becomes /opt/local/bin:/usr/bin:/usr/local/bin</span></span>
-<span style="font-weight: bold"><span style="color: #0000FF">export</span></span> <span style="color: #009900">PATH</span><span style="color: #990000">=</span><span style="color: #009900">$PATH</span><span style="color: #990000">:</span>/usr/local/bin</tt></pre>
-</div>
-</div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/indepth/environment_variables.html#working-with-environment-variables">https://www.phusionpassenger.com/library/indepth/environment_variables.html#working-with-environment-variables</a></p></div>
 </div>
 <div class="sect2">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="the_path_env_var"></span><h3 data-comment-topic="the-path-environment-variable-yzfn3k" data-anchor="the_path_env_var">9.2. The PATH environment variable</h3>
-<div class="paragraph"><p>The <span class="monospaced">PATH</span> environment variable dictates where the system looks for command. It is a colon-separated list of directories. If you get a "command not found" error while you know that the command is installed, then setting <span class="monospaced">PATH</span> will help. For example suppose that the command <span class="monospaced">frobnicator</span> is in <span class="monospaced">/opt/local/bin</span>:</p></div>
-<div class="listingblock">
-<div class="content">
-<!-- Generator: GNU source-highlight 2.11.1
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt>user@localhost bash$ frobnicator
-bash<span style="color: #990000">:</span> frobnicator<span style="color: #990000">:</span> <span style="font-weight: bold"><span style="color: #0000FF">command</span></span> not found</tt></pre>
-</div>
-</div>
-<div class="paragraph"><p>We verify that <span class="monospaced">/opt/local/bin</span> is not in <span class="monospaced">PATH</span>:</p></div>
-<div class="listingblock">
-<div class="content">
-<!-- Generator: GNU source-highlight 2.11.1
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt>user@localhost bash$ echo <span style="color: #009900">$PATH</span>
-/bin<span style="color: #990000">:</span>/usr/bin<span style="color: #990000">:</span>/usr/local/bin</tt></pre>
-</div>
-</div>
-<div class="paragraph"><p>We can run <span class="monospaced">frobnicator</span> through it’s full path…</p></div>
-<div class="listingblock">
-<div class="content">
-<!-- Generator: GNU source-highlight 2.11.1
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt>user@localhost bash$ /opt/local/bin/frobnicator
-<span style="font-style: italic"><span style="color: #9A1900"># =&gt; success!</span></span></tt></pre>
-</div>
-</div>
-<div class="paragraph"><p>…or we can add <span class="monospaced">/opt/local/bin</span> to <span class="monospaced">PATH</span>.</p></div>
-<div class="listingblock">
-<div class="content">
-<!-- Generator: GNU source-highlight 2.11.1
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt>user@localhost bash$ <span style="font-weight: bold"><span style="color: #0000FF">export</span></span> <span style="color: #009900">PATH</span><span style="color: #990000">=</span><span style="color: #009900">$PATH</span><span style="color: #990000">:</span>/opt/local/bin
-user@localhost bash$ frobnicator
-<span style="font-style: italic"><span style="color: #9A1900"># =&gt; success!</span></span></tt></pre>
-</div>
-</div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/indepth/environment_variables.html#the-path-environment-variable">https://www.phusionpassenger.com/library/indepth/environment_variables.html#the-path-environment-variable</a></p></div>
 <div class="sect3">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_adding_phusion_passenger_8217_s_administration_tools_to_path"></span><h4 data-comment-topic="adding-phusion-passenger-s-administration-tools-to-path-d7k5mh" data-anchor="_adding_phusion_passenger_8217_s_administration_tools_to_path">9.2.1. Adding Phusion Passenger’s administration tools to PATH</h4>
-<div class="paragraph"><p>If you get a "command not found" error when invoking one of the Phusion Passenger administration tools (e.g. <span class="monospaced">passenger-status</span> or <span class="monospaced">passenger-memory-stats</span> then that means the tools are not in <span class="monospaced">PATH</span>, so you need to add them.</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-If you <a href="#rubygems_generic_install">installed Phusion Passenger with RubyGems</a>, then the tools are in your RubyGems executable path. You can view the gem path using the command <span class="monospaced">gem env</span>:
-</p>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>$ gem env
-RubyGems Environment:
-  - RUBYGEMS VERSION: 1.8.15
-  - RUBY VERSION: 1.8.7 (2011-12-28 patchlevel 357) [i686-darwin10.8.0]
-  - INSTALLATION DIRECTORY: /opt/ruby-enterprise-1.8.7-2010.01/lib/ruby/gems/1.8
-  - RUBY EXECUTABLE: /opt/ruby-enterprise-1.8.7-2010.01/bin/ruby
-  - EXECUTABLE DIRECTORY: /opt/ruby-enterprise-1.8.7-2010.01/bin    &lt;--------- !!
-  - RUBYGEMS PLATFORMS:
-    - ruby
-    - x86-darwin-10
-  - GEM PATHS:
-     - /opt/ruby-enterprise-1.8.7-2010.01/lib/ruby/gems/1.8
-     - /Users/hongli/.gem/ruby/1.8
-  - GEM CONFIGURATION:
-     - :update_sources =&gt; true
-     - :verbose =&gt; true
-     - :benchmark =&gt; false
-     - :backtrace =&gt; false
-     - :bulk_threshold =&gt; 1000
-     - "gem" =&gt; "--no-ri --no-rdoc"
-  - REMOTE SOURCES:
-     - http://rubygems.org/</pre>
-</div>
-</div>
-<div class="paragraph"><p>As you can see, the RubyGems executable path in the example happens to be <span class="monospaced">/opt/ruby-enterprise-1.8.7-2010.01/bin</span>. So that directory must be added to <span class="monospaced">PATH</span>.</p></div>
-</li>
-<li>
-<p>
-If you <a href="#tarball_generic_install">installed Phusion Passenger using the tarball</a>, then the tools are in the <span class="monospaced">bin</span> subdirectory of the Phusion Passenger tarball directory that you extracted. For example, if you extracted <span class="monospaced">passenger-4.9.0.tar.gz</span> inside <span class="monospaced">/opt</span>, then the tools are located in <span class="monospaced">/opt/passenger-4.0.9/bin</span>. In that case, you need to add <span class="monospaced">/opt/passenger-4.0.9/bin</span> to your <span class="monospaced">PATH</span>.
-</p>
-</li>
-<li>
-<p>
-If you installed Phusion Passenger using native OS packages, then some Phusion Passenger administration tools are in <span class="monospaced">/usr/bin</span>, while others are in <span class="monospaced">/usr/sbin</span>. If you are not logged in as root, then <span class="monospaced">/usr/sbin</span> may not be in <span class="monospaced">PATH</span>, which would explain why you get a "command not found" when trying to invoke some of the tools. You should <span class="monospaced">/usr/sbin</span> to <span class="monospaced">PATH</span>.
-</p>
-</li>
-<li>
-<p>
-If you are unsure where your Phusion Passenger directory is then you can use the <span class="monospaced">find</span> command to look them up. Go to the root directory and invoke <span class="monospaced">find</span> with <span class="monospaced">sudo</span>:
-</p>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>$ cd /
-$ sudo find . -name passenger-status
-/usr/local/passenger/bin/passenger-status</pre>
-</div>
-</div>
-<div class="paragraph"><p>In this example, the administration tools happen to be in <span class="monospaced">/usr/local/passenger/bin</span>, so you must add that to <span class="monospaced">PATH</span>.</p></div>
-</li>
-</ul></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="./images/icons/note.png" alt="Note">
-</td>
-<td class="content">You may still get a "command not found" when invoking the tools through sudo, even after you’ve added the relevant directory to <span class="monospaced">PATH</span>. Please read <a href="#env_vars_and_sudo">Environment variables and sudo</a> to learn more.</td>
-</tr></table>
-</div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/indepth/environment_variables.html#adding-passenger-s-administration-tools-to-path">https://www.phusionpassenger.com/library/indepth/environment_variables.html#adding-passenger-s-administration-tools-to-path</a></p></div>
 </div>
 </div>
 <div class="sect2">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_making_environment_variables_permanent"></span><h3 data-comment-topic="making-environment-variables-permanent-mkq46d" data-anchor="_making_environment_variables_permanent">9.3. Making environment variables permanent</h3>
-<div class="paragraph"><p>When you exit your shell, the evironment variable changes are lost. There is no standard method to set environment variables system-wide, so you have to set them in different configuration files for different services.</p></div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/indepth/environment_variables.html#making-environment-variables-permanent">https://www.phusionpassenger.com/library/indepth/environment_variables.html#making-environment-variables-permanent</a></p></div>
 <div class="sect3">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_bash"></span><h4 data-comment-topic="bash-hmcscc" data-anchor="_bash">9.3.1. bash</h4>
-<div class="paragraph"><p>To make environment variables permanent for future bash sessions <strong>for the current user</strong>, add them to your <span class="monospaced">~/.bashrc</span>:</p></div>
-<div class="listingblock">
-<div class="content">
-<!-- Generator: GNU source-highlight 2.11.1
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt>echo <span style="color: #FF0000">'export FOO=bar'</span> <span style="color: #990000">&gt;&gt;</span> <span style="color: #990000">~/.</span>bashrc
-echo <span style="color: #FF0000">'export PATH=/usr/local/bin:$PATH'</span> <span style="color: #990000">&gt;&gt;</span> <span style="color: #990000">~/.</span>bashrc</tt></pre>
-</div>
-</div>
-<div class="paragraph"><p>To make them permanent for future bash sessions <strong>for all users</strong>, add them to <span class="monospaced">/etc/bashrc</span>.</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="./images/icons/note.png" alt="Note">
-</td>
-<td class="content">Depending on the system, the bashrc file may have a different filename. On Debian and Ubuntu, it’s <span class="monospaced">/etc/bash.bashrc</span>.
-NOTE: Make sure your <span class="monospaced">~/.bashrc</span> is actually included by your <span class="monospaced">~/.profile</span>, which might not be the case if you created the user with <span class="monospaced">useradd</span> instead of <span class="monospaced">adduser</span> for example</td>
-</tr></table>
-</div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/indepth/environment_variables.html#bash">https://www.phusionpassenger.com/library/indepth/environment_variables.html#bash</a></p></div>
 </div>
 <div class="sect3">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_apache"></span><h4 data-comment-topic="apache-15y3bm0" data-anchor="_apache">9.3.2. Apache</h4>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="./images/icons/note.png" alt="Note">
-</td>
-<td class="content">This subsection describes how to set environment variables on Apache itself, not on apps served through Phusion Passenger for Apache. The environment variables you set here will be passed to all apps, but you cannot customize them on a per-app basis. See also <a href="#env_vars_passenger_apps">Setting environment variables on Phusion Passenger-served apps</a>.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>On Debian and Ubuntu, with an Apache installed through apt, Apache environment variables are defined in the file <span class="monospaced">/etc/apache2/envvars</span>. This is a shell script so environment variables must be specified with the shell syntax.</p></div>
-<div class="paragraph"><p>On Red Hat, Fedora, CentOS and ScientificLinux, with an Apache installed through YUM, Apache environment variables are defined in <span class="monospaced">/etc/sysconfig/httpd</span>.</p></div>
-<div class="paragraph"><p>On OS X they are defined in <span class="monospaced">/System/Library/LaunchDaemons/org.apache.httpd.plist</span>, as explained <a href="http://stackoverflow.com/questions/6833939/path-environment-variable-for-apache2-on-mac">here on Stack Overflow</a>.</p></div>
-<div class="paragraph"><p>On other systems, or if you did not install Apache through the system’s package manager, the configuration file for environment variables is specific to the vendor that supplied Apache. There may not even be such a configuration file. You should contact the vendor for support.</p></div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/indepth/environment_variables.html#apache">https://www.phusionpassenger.com/library/indepth/environment_variables.html#apache</a></p></div>
 </div>
 <div class="sect3">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_nginx"></span><h4 data-comment-topic="nginx-uarf27" data-anchor="_nginx">9.3.3. Nginx</h4>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="./images/icons/note.png" alt="Note">
-</td>
-<td class="content">This subsection describes how to set environment variables on Nginx itself, not on apps served through Phusion Passenger for Nginx. The environment variables you set here will be passed to all apps, but you cannot customize them on a per-app basis. See also <a href="#env_vars_passenger_apps">Setting environment variables on Phusion Passenger-served apps</a>.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>If you installed Nginx through <a href="#install_on_debian_ubuntu">the Debian or Ubuntu packages</a>, then you can define environment variables in <span class="monospaced">/etc/default/nginx</span>. This is a shell script so you must use the <span class="monospaced">export FOO=bar</span> syntax.</p></div>
-<div class="paragraph"><p>Otherwise, environment variables are best set through the script which starts Nginx. For example, if you installed Nginx from source and you used
-then you should edit that script to define the environment variables. Those init scripts are regular shell scripts, so use the <span class="monospaced">export FOO=bar</span> syntax. Just make sure your set your environment variables before the script starts Nginx.</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="./images/icons/note.png" alt="Note">
-</td>
-<td class="content">Setting environment variables on Nginx has no effect on the <a href="#flying_passenger">Flying Passenger daemon</a> because the daemon is started seperately. You should set the environment variables in the shell right before starting the daemon.</td>
-</tr></table>
-</div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/indepth/environment_variables.html#nginx">https://www.phusionpassenger.com/library/indepth/environment_variables.html#nginx</a></p></div>
 </div>
 <div class="sect3">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_cron"></span><h4 data-comment-topic="cron-6272ar" data-anchor="_cron">9.3.4. cron</h4>
-<div class="paragraph"><p>To make environment variables permanent for cron jobs, add those variables to the relevant crontab. But note that inside crontabs you cannot refer to existing environment variables with the <span class="monospaced">$</span> syntax because crontabs are not shell scripts. You have to specify the entire value.</p></div>
-<div class="listingblock">
-<div class="title">What to put in "crontab -e"</div>
-<div class="content monospaced">
-<pre># Environment variable definitions
-FOO=bar
-APXS2=/usr/sbin/apxs2
-
-# **WRONG!** You cannot refer to existing variables with the `$` syntax!
-PATH=/usr/bin:$PATH
-# **WRONG!** You cannot use the 'export' keyword!
-export PATH=/usr/bin:/usr/local/bin
-# Correct:
-PATH=/usr/bin:/usr/local/bin
-
-# Jobs:
-# m h  dom mon dow   command
-  * *  *   *   *     frobnicator</pre>
-</div>
-</div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/indepth/environment_variables.html#cron">https://www.phusionpassenger.com/library/indepth/environment_variables.html#cron</a></p></div>
 </div>
 <div class="sect3">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="env_vars_passenger_apps"></span><h4 data-comment-topic="phusion-passenger-served-apps-127wbl2" data-anchor="env_vars_passenger_apps">9.3.5. Phusion Passenger-served apps</h4>
-<div class="paragraph"><p>You can pass environment variables to Phusion Passenger-served apps through various methods:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-When running Apache, use the <span class="monospaced">PassEnv</span> and <span class="monospaced">SetEnv</span> directives of <a href="http://httpd.apache.org/docs/2.4/mod/mod_env.html">mod_env</a>. This is supported starting from Phusion Passenger 4.0.
-</p>
-</li>
-<li>
-<p>
-When running Nginx, use the <a href="#PassengerEnvVar">passenger_env_var</a> directive.
-</p>
-</li>
-<li>
-<p>
-Through your <span class="monospaced">bashrc</span>. Starting from version 4.0, Phusion Passenger 4.0 spawns applications through bash and inherit all bash environment variables. Phusion Passenger Standalone tends to be started from the shell and thus inherits all environment variables set by the shell.
-</p>
-</li>
-<li>
-<p>
-Through Apache and Nginx, as described earlier in this chapter. Any environment variables that you set on Apache and Nginx itself are inherited by Phusion Passenger, and thus by Phusion Passenger-served apps as well.
-</p>
-</li>
-<li>
-<p>
-Through the application itself. Most programming languages provide APIs for setting environment variables. For example in Ruby you can write:
-</p>
-<div class="listingblock">
-<div class="content">
-<!-- Generator: GNU source-highlight 2.11.1
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt>ENV<span style="color: #990000">[</span><span style="color: #FF0000">'FOO'</span><span style="color: #990000">]</span> <span style="color: #990000">=</span> <span style="color: #FF0000">'bar'</span></tt></pre>
-</div>
-</div>
-<div class="paragraph"><p>In Python you can write:</p></div>
-<div class="listingblock">
-<div class="content">
-<!-- Generator: GNU source-highlight 2.11.1
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt><span style="font-weight: bold"><span style="color: #000080">import</span></span> os
-os<span style="color: #990000">.</span>environ<span style="color: #990000">[</span><span style="color: #FF0000">'FOO'</span><span style="color: #990000">]</span> <span style="color: #990000">=</span> <span style="color: #FF0000">'bar'</span></tt></pre>
-</div>
-</div>
-</li>
-</ul></div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/indepth/environment_variables.html#passenger-served-apps">https://www.phusionpassenger.com/library/indepth/environment_variables.html#passenger-served-apps</a></p></div>
 </div>
 </div>
 <div class="sect2">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="env_vars_and_sudo"></span><h3 data-comment-topic="environment-variables-and-sudo-znzmif" data-anchor="env_vars_and_sudo">9.4. Environment variables and sudo</h3>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="./images/icons/note.png" alt="Note">
-</td>
-<td class="content">RVM users should always use the <span class="monospaced">rvmsudo</span> command instead of <span class="monospaced">sudo</span>. However all information in this section apply to <span class="monospaced">rvmsudo</span> as well.</td>
-</tr></table>
-</div>
-<div class="paragraph"><p>The <span class="monospaced">sudo</span> command resets all environment variables before running the specified command, for security reasons. So if you set environment variables before running <span class="monospaced">sudo passenger-install-xxx-module</span>, <span class="monospaced">sudo passenger-status</span> or any other commands, then the environment variables are not correctly passed to the command. You can solve this by running sudo with <span class="monospaced">-E</span> (preserve environment variables):</p></div>
-<div class="listingblock">
-<div class="content">
-<!-- Generator: GNU source-highlight 2.11.1
-by Lorenzo Bettini
-http://www.lorenzobettini.it
-http://www.gnu.org/software/src-highlite -->
-<pre><tt>user@localhost bash$ <span style="font-weight: bold"><span style="color: #0000FF">export</span></span> <span style="color: #009900">APXS2</span><span style="color: #990000">=</span>/usr/sbin/apxs<span style="color: #993399">2</span>
-user@localhost bash$ sudo -E passenger-install-apache<span style="color: #993399">2</span>-module</tt></pre>
-</div>
-</div>
-<div class="paragraph"><p>Alternatively, you can obtain a root prompt with sudo first, and <strong>then</strong> set the environment variables, before running any further commands:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>user@localhost bash$ sudo -s
-Password: ...
-root@localhost bash# export APXS2=/usr/sbin/apxs2
-root@localhost bash# passenger-install-apache2-module</pre>
-</div>
-</div>
-<div class="paragraph"><p>Note that for security reasons, <span class="monospaced">sudo</span> <strong>always resets the <span class="monospaced">PATH</span> environment variable</strong>, even if you pass <span class="monospaced">-E</span>! You can get around this problem by obtaining a root prompt first, and then set the environment variables:</p></div>
-<div class="listingblock">
-<div class="content monospaced">
-<pre>user@localhost bash$ sudo -s
-Password: ...
-root@localhost bash# export PATH=$PATH:/opt/myruby/bin
-root@localhost bash# passenger-install-apache2-module</pre>
-</div>
-</div>
+<div class="paragraph"><p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/indepth/environment_variables.html#environment-variables-and-sudo">https://www.phusionpassenger.com/library/indepth/environment_variables.html#environment-variables-and-sudo</a></p></div>
 </div>
 </div>
 </div>