RubyGems - passenger - Versions diffs - 4.0.10 → 4.0.13 - Mend

passenger 4.0.10 → 4.0.13

Potentially problematic release.

This version of passenger might be problematic. Click here for more details.

Files changed (224) hide show

data.tar.gz.asc +7 -7
data/.gitignore +66 -0
data/.travis.yml +2 -5
data/CONTRIBUTORS +2 -1
data/NEWS +24 -0
data/README.md +5 -10
data/bin/passenger +1 -0
data/bin/passenger-config +29 -3
data/bin/passenger-install-nginx-module +1 -1
data/build/basics.rb +8 -2
data/build/debian.rb +22 -0
data/build/integration_tests.rb +16 -2
data/build/misc.rb +3 -0
data/build/packaging.rb +77 -29
data/build/preprocessor.rb +13 -10
data/build/test_basics.rb +6 -0
data/debian.template/locations.ini.template +13 -0
data/debian.template/ruby-passenger-dev.install.template +3 -0
data/debian.template/ruby-passenger-doc.install.template +2 -0
data/debian.template/ruby-passenger.install.template +12 -0
data/debian.template/rules.template +1 -0
data/dev/run_travis.sh +46 -14
data/doc/Architectural overview.html +25 -34
data/doc/Packaging.html +31 -23
data/doc/Packaging.txt.md +32 -23
data/doc/Security of user switching support.html +16 -18
data/doc/Users guide Apache.html +231 -239
data/doc/Users guide Nginx.html +219 -227
data/doc/Users guide Standalone.html +12 -15
data/doc/users_guide_snippets/installation.txt +3 -2
data/ext/common/ApplicationPool2/Implementation.cpp +6 -16
data/ext/common/Constants.h +1 -1
data/ext/common/ResourceLocator.h +6 -6
data/ext/common/UnionStation.h +11 -15
data/ext/common/Utils/ProcessMetricsCollector.h +7 -4
data/ext/common/agents/HelperAgent/AgentOptions.h +6 -0
data/ext/common/agents/HelperAgent/Main.cpp +5 -0
data/ext/common/agents/HelperAgent/RequestHandler.h +9 -1
data/ext/common/agents/LoggingAgent/Main.cpp +4 -0
data/ext/common/agents/Watchdog/Main.cpp +7 -0
data/ext/nginx/config +1 -1
data/ext/oxt/Readme.txt +15 -0
data/helper-scripts/download_binaries/extconf.rb +83 -0
data/lib/phusion_passenger.rb +78 -80
data/lib/phusion_passenger/abstract_installer.rb +22 -8
data/lib/phusion_passenger/console_text_template.rb +1 -1
data/lib/phusion_passenger/loader_shared_helpers.rb +2 -1
data/lib/phusion_passenger/native_support.rb +22 -9
data/lib/phusion_passenger/packaging.rb +7 -2
data/lib/phusion_passenger/platform_info.rb +28 -1
data/lib/phusion_passenger/platform_info/apache.rb +246 -26
data/lib/phusion_passenger/platform_info/apache_detector.rb +232 -0
data/lib/phusion_passenger/platform_info/depcheck_specs/ruby.rb +4 -0
data/lib/phusion_passenger/platform_info/linux.rb +7 -0
data/lib/phusion_passenger/public_api.rb +11 -2
data/lib/phusion_passenger/standalone/command.rb +11 -14
data/lib/phusion_passenger/standalone/runtime_installer.rb +313 -275
data/lib/phusion_passenger/standalone/runtime_locator.rb +163 -0
data/lib/phusion_passenger/standalone/start_command.rb +38 -46
data/lib/phusion_passenger/utils/json.rb +329 -0
data/lib/phusion_passenger/utils/tmpio.rb +1 -0
data/passenger.gemspec +4 -0
data/resources/mime.types +1 -0
data/resources/oss-binaries.phusionpassenger.com.crt +84 -0
data/resources/release.txt +0 -0
data/resources/templates/standalone/download_tool_missing.txt.erb +18 -0
data/rpm/README.rdoc +117 -0
data/rpm/config/apache-passenger.conf.in +19 -0
data/rpm/config/nginx-passenger.conf.in +10 -0
data/rpm/config/rubygem-passenger.te +10 -0
data/rpm/doc/README.nginx-alternatives +5 -0
data/rpm/doc/example_yum_repository_htaccess +5 -0
data/rpm/doc/footer.shtml +12 -0
data/rpm/doc/header.shtml +156 -0
data/rpm/nginx-alternatives.spec +97 -0
data/rpm/passenger-release.spec +91 -0
data/rpm/passenger.spec +667 -0
data/rpm/patches/passenger-force-native.patch +63 -0
data/rpm/release/RPM-GPG-KEY-stealthymonkeys +33 -0
data/rpm/release/build-release.sh +35 -0
data/rpm/release/build.rb +301 -0
data/rpm/release/create-mirrors.sh +16 -0
data/rpm/release/mirrors +1 -0
data/rpm/release/mock-repo/comps.xml +21 -0
data/rpm/release/mock-repo/rubygem-daemon_controller-0.2.5-1.noarch.rpm +0 -0
data/rpm/release/mock-repo/rubygem-file-tail-1.0.5-1.noarch.rpm +0 -0
data/rpm/release/mock-repo/rubygem-spruz-0.2.2-1.noarch.rpm +0 -0
data/rpm/release/mocksetup-first.sh +102 -0
data/rpm/release/mocksetup.sh +67 -0
data/test/integration_tests/apache2_tests.rb +1 -1
data/test/integration_tests/downloaded_binaries_tests.rb +76 -0
data/test/integration_tests/native_packaging_spec.rb +38 -6
data/test/integration_tests/source_packaging_test.rb +198 -0
data/test/integration_tests/standalone_tests.rb +275 -0
data/test/ruby/admin_tools_spec.rb +1 -1
data/test/ruby/rails4.0/loader_spec.rb +28 -0
data/test/ruby/rails4.0/preloader_spec.rb +34 -0
data/test/ruby/spec_helper.rb +5 -1
data/test/ruby/standalone/runtime_installer_spec.rb +399 -0
data/test/ruby/standalone/runtime_locator_spec.rb +214 -0
data/test/stub/apache2/httpd.conf.erb +18 -1
data/test/stub/rack/tmp/.gitignore +0 -0
data/test/stub/rails2.3/log/.gitignore +1 -0
data/test/stub/rails2.3/public/.gitignore +1 -0
data/test/stub/rails2.3/tmp/cache/.gitignore +1 -0
data/test/stub/rails2.3/tmp/pids/.gitignore +1 -0
data/test/stub/rails2.3/tmp/sessions/.gitignore +1 -0
data/test/stub/rails2.3/tmp/sockets/.gitignore +1 -0
data/test/stub/rails3.0/.gitignore +4 -0
data/test/stub/rails3.0/Gemfile +1 -1
data/test/stub/rails3.0/Gemfile.lock +1 -1
data/test/stub/rails3.0/lib/tasks/.gitkeep +0 -0
data/test/stub/rails3.0/log/.gitignore +0 -0
data/test/stub/rails3.0/public/stylesheets/.gitkeep +0 -0
data/test/stub/rails3.0/vendor/plugins/.gitkeep +0 -0
data/test/stub/rails3.1/.gitignore +15 -0
data/test/stub/rails3.1/Gemfile +1 -1
data/test/stub/rails3.1/Gemfile.lock +1 -1
data/test/stub/rails3.1/app/mailers/.gitkeep +0 -0
data/test/stub/rails3.1/app/models/.gitkeep +0 -0
data/test/stub/rails3.1/lib/assets/.gitkeep +0 -0
data/test/stub/rails3.1/lib/tasks/.gitkeep +0 -0
data/test/stub/rails3.1/log/.gitkeep +0 -0
data/test/stub/rails3.1/test/fixtures/.gitkeep +0 -0
data/test/stub/rails3.1/test/functional/.gitkeep +0 -0
data/test/stub/rails3.1/test/integration/.gitkeep +0 -0
data/test/stub/rails3.1/test/unit/.gitkeep +0 -0
data/test/stub/rails3.1/vendor/assets/stylesheets/.gitkeep +0 -0
data/test/stub/rails3.1/vendor/plugins/.gitkeep +0 -0
data/test/stub/rails3.2/.gitignore +15 -0
data/test/stub/rails3.2/app/mailers/.gitkeep +0 -0
data/test/stub/rails3.2/app/models/.gitkeep +0 -0
data/test/stub/rails3.2/lib/assets/.gitkeep +0 -0
data/test/stub/rails3.2/lib/tasks/.gitkeep +0 -0
data/test/stub/rails3.2/log/.gitkeep +0 -0
data/test/stub/rails3.2/test/fixtures/.gitkeep +0 -0
data/test/stub/rails3.2/test/functional/.gitkeep +0 -0
data/test/stub/rails3.2/test/integration/.gitkeep +0 -0
data/test/stub/rails3.2/test/unit/.gitkeep +0 -0
data/test/stub/rails3.2/vendor/assets/stylesheets/.gitkeep +0 -0
data/test/stub/rails3.2/vendor/plugins/.gitkeep +0 -0
data/test/stub/rails4.0/.gitignore +16 -0
data/test/stub/rails4.0/Gemfile +45 -0
data/test/stub/rails4.0/Gemfile.lock +126 -0
data/test/stub/rails4.0/README.rdoc +28 -0
data/test/stub/rails4.0/Rakefile +6 -0
data/test/stub/rails4.0/app/assets/images/.keep +0 -0
data/test/stub/rails4.0/app/assets/javascripts/application.js +16 -0
data/test/stub/rails4.0/app/assets/stylesheets/application.css +13 -0
data/test/stub/rails4.0/app/controllers/application_controller.rb +5 -0
data/test/stub/rails4.0/app/controllers/concerns/.keep +0 -0
data/test/stub/rails4.0/app/helpers/application_helper.rb +2 -0
data/test/stub/rails4.0/app/mailers/.keep +0 -0
data/test/stub/rails4.0/app/models/.keep +0 -0
data/test/stub/rails4.0/app/models/concerns/.keep +0 -0
data/test/stub/rails4.0/app/views/layouts/application.html.erb +14 -0
data/test/stub/rails4.0/bin/bundle +3 -0
data/test/stub/rails4.0/bin/rails +4 -0
data/test/stub/rails4.0/bin/rake +4 -0
data/test/stub/rails4.0/config.ru +4 -0
data/test/stub/rails4.0/config/application.rb +23 -0
data/test/stub/rails4.0/config/boot.rb +4 -0
data/test/stub/rails4.0/config/database.yml +25 -0
data/test/stub/rails4.0/config/environment.rb +5 -0
data/test/stub/rails4.0/config/environments/development.rb +29 -0
data/test/stub/rails4.0/config/environments/production.rb +80 -0
data/test/stub/rails4.0/config/environments/test.rb +36 -0
data/test/stub/rails4.0/config/initializers/backtrace_silencers.rb +7 -0
data/test/stub/rails4.0/config/initializers/filter_parameter_logging.rb +4 -0
data/test/stub/rails4.0/config/initializers/inflections.rb +16 -0
data/test/stub/rails4.0/config/initializers/mime_types.rb +5 -0
data/test/stub/rails4.0/config/initializers/passenger.rb +1 -0
data/test/stub/rails4.0/config/initializers/secret_token.rb +12 -0
data/test/stub/rails4.0/config/initializers/session_store.rb +3 -0
data/test/stub/rails4.0/config/initializers/wrap_parameters.rb +14 -0
data/test/stub/rails4.0/config/locales/en.yml +23 -0
data/test/stub/rails4.0/config/routes.rb +57 -0
data/test/stub/rails4.0/db/seeds.rb +7 -0
data/test/stub/rails4.0/lib/assets/.keep +0 -0
data/test/stub/rails4.0/lib/tasks/.keep +0 -0
data/test/stub/rails4.0/log/.keep +0 -0
data/test/stub/rails4.0/public/404.html +58 -0
data/test/stub/rails4.0/public/422.html +58 -0
data/test/stub/rails4.0/public/500.html +57 -0
data/test/stub/rails4.0/public/favicon.ico +0 -0
data/test/stub/rails4.0/public/robots.txt +5 -0
data/test/stub/rails4.0/test/controllers/.keep +0 -0
data/test/stub/rails4.0/test/fixtures/.keep +0 -0
data/test/stub/rails4.0/test/helpers/.keep +0 -0
data/test/stub/rails4.0/test/integration/.keep +0 -0
data/test/stub/rails4.0/test/mailers/.keep +0 -0
data/test/stub/rails4.0/test/models/.keep +0 -0
data/test/stub/rails4.0/test/test_helper.rb +15 -0
data/test/stub/rails4.0/vendor/assets/javascripts/.keep +0 -0
data/test/stub/rails4.0/vendor/assets/stylesheets/.keep +0 -0
data/test/stub/rails_apps/1.2/empty/.gitignore +3 -0
data/test/stub/rails_apps/1.2/empty/app/models/.gitignore +0 -0
data/test/stub/rails_apps/1.2/empty/db/.gitignore +0 -0
data/test/stub/rails_apps/1.2/empty/public/.htaccess +40 -0
data/test/stub/rails_apps/1.2/empty/public/stylesheets/.gitignore +0 -0
data/test/stub/rails_apps/2.0/empty/.gitignore +3 -0
data/test/stub/rails_apps/2.0/empty/app/models/.gitignore +0 -0
data/test/stub/rails_apps/2.0/empty/db/.gitignore +0 -0
data/test/stub/rails_apps/2.0/empty/public/.htaccess +40 -0
data/test/stub/rails_apps/2.0/empty/public/stylesheets/.gitignore +0 -0
data/test/stub/rails_apps/2.2/empty/.gitignore +3 -0
data/test/stub/rails_apps/2.2/empty/app/models/.gitignore +0 -0
data/test/stub/rails_apps/2.2/empty/db/.gitignore +0 -0
data/test/stub/rails_apps/2.2/empty/public/stylesheets/.gitignore +0 -0
data/test/stub/rails_apps/2.3/empty/.gitignore +3 -0
data/test/stub/rails_apps/2.3/empty/app/models/.gitignore +0 -0
data/test/stub/rails_apps/2.3/empty/db/.gitignore +0 -0
data/test/stub/rails_apps/2.3/empty/public/stylesheets/.gitignore +0 -0
data/test/stub/rails_apps/2.3/mycook/public/.htaccess +42 -0
data/test/stub/rails_apps/2.3/mycook/public/uploads/.gitignore +0 -0
data/test/stub/wsgi/tmp/.gitignore +0 -0
data/test/valgrind-osx.supp +7 -0
metadata +162 -8
metadata.gz.asc +7 -7
data/debian.template/locations.ini +0 -12
data/debian.template/ruby-passenger-dev.install +0 -3
data/debian.template/ruby-passenger-doc.install +0 -2
data/debian.template/ruby-passenger.install +0 -11
data/resources/templates/installer_common/freebsd9_broken_cxx_runtime.txt.erb +0 -19

@@ -1,9 +1,9 @@
 <!DOCTYPE html>
-<html lang="en">
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<meta name="generator" content="AsciiDoc 8.6.7">
-<title>Phusion Passenger users guide, Nginx version</title>
+<html lang="en">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<meta name="generator" content="AsciiDoc 8.6.7">
+<title>Phusion Passenger users guide, Nginx version</title>
 <style type="text/css">
 /* Shared CSS for AsciiDoc xhtml11 and html5 backends */
@@ -603,7 +603,7 @@ div.exampleblock > div.content, div.sidebarblock > div.content, div.listingblock
 div.verseblock { border-left-width: 0; margin-left: 3em; }
 div.quoteblock { border-left-width: 3px; margin-left: 0; margin-right: 0;}
 div.admonitionblock td.content { border-left: 3px solid #E8E8E8; }
-</style>
+</style>
 <script type="text/javascript">
 /*<![CDATA[*/
 var asciidoc = {  // Namespace.
@@ -797,8 +797,7 @@ install: function(toclevels) {
 }
 asciidoc.install();
 /*]]>*/
-</script>
-<style type="text/css">
+</script><style type="text/css">
 body {
 	margin: 1em auto 1em auto;
 	padding: 0 1em 0 1em;
@@ -1055,11 +1054,10 @@ pre {
 }
 </style>
-</head>
+</head>
 <body class="article">
 <div id="topbar" style="display: none">
 	<div class="title">
-		<!-- Don't put a space between the img and a. That will break the hover layout. -->
 		<img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAsAAAAKCAYAAAEV95QVAAAAAXNSR0IArs4c6QAAAAZiS0dEAP8A/wD/oL2nkwAAAAlwSFlzAAALEwAACxMBAJqcGAAAAAd0SU1FB9sGCRMSACDxkZwAAAAidEVYdENvbW1lbnQAQ3JlYXRlZCB3aXRoIEdJTVAgb24gYSBNYWOHqHdDAAAAZUlEQVQY032PSxbAIAjEIlfygL6ePF3UUvpzNjgSYWwqAMEhUQnANnsC7TQPeJpsVWzMuh2sog4vDTUbqP081zECrW4dtdaQGSIKlWluPyjK+VXxAz5XfcKufCzA130AfQHWB30HZxlPaP080xsAAAAASUVORK5CYII=" width="11" height="10" alt=""><a href="javascript:void(Mizuho.smoothlyScrollToToc())">Phusion Passenger users guide, Nginx version</a>
 	</div>
 	<a href="javascript:void(0)" id="current_section"></a>
@@ -1070,13 +1068,12 @@ pre {
 <div class="sectionbody">
 <div class="paragraph"><p><span class="image">
 <a class="image" href="http://www.phusion.nl/">
-<img src="images/phusion_banner.png" alt="images/phusion_banner.png">
-</a>
+<img src="images/phusion_banner.png" alt="images/phusion_banner.png"></a>
 </span></p></div>
 <div class="paragraph"><p>Phusion Passenger is an application server which can directly integrate into Nginx. It is designed to be easy to use, fast, stable and reliable and is used by <a href="http://trends.builtwith.com/Web-Server/Phusion-Passenger">hundreds of thousands of websites</a> all over the world.</p></div>
 <div class="paragraph"><p>Phusion Passenger is a so-called polyglot application server because it supports applications written in multiple programming languages. At this time, Ruby and Python are supported.</p></div>
 <div class="paragraph"><p>This users guide will teach you:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 How to install Nginx with Phusion Passenger support.
@@ -1284,7 +1281,7 @@ if it doesn’t work on your POSIX-compliant operating system.</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-2s9na5" data-anchor="_where_to_get_support">1.2. Where to get support</h3>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 <a href="http://groups.google.com/group/phusion-passenger">Discussion forum</a> - post a
@@ -1323,7 +1320,7 @@ Report security vulnerabilities to <a href="mailto:security@phusion.nl">security
 <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-1uu3sqp" data-anchor="_synopsis">2.1. Synopsis</h3>
 <div class="paragraph"><p>The Phusion Passenger installation process consists of two steps:</p></div>
-<div class="olist arabic"><ol class="arabic">
+<div class="olist arabic"><ol class="arabic">
 <li>
 <p>
 The <strong>obtainment step</strong>, where you download the Phusion Passenger files puts them somewhere on your system. This can be done through downloading the source tarball, installing the Ruby gem or installing a native OS package via APT or YUM.
@@ -1351,7 +1348,7 @@ The <strong>integration step</strong>, where you configure Phusion Passenger so
 </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>
+<div class="ulist"><ul>
 <li>
 <p>
 Are you using RVM? Run <span class="monospaced">rvmsudo -s</span>
@@ -1409,8 +1406,8 @@ Is <em>sudo</em> not installed on your system? Run <span class="monospaced">su -
 </div>
 </div>
 <span class="anchor_helper" id="add_rubygems_bin_dir_to_path"></span><h4 class="float" data-anchor="add_rubygems_bin_dir_to_path">Step 3: add the RubyGems bin directory to your $PATH</h4>
-<div class="paragraph"><p>If you all of the following are applicable to you:</p></div>
-<div class="ulist"><ul>
+<div class="paragraph"><p>If all of the following are applicable to you:</p></div>
+<div class="ulist"><ul>
 <li>
 <p>
 You are on Debian or Ubuntu,
@@ -1459,7 +1456,7 @@ chmod o+x /home/phusion</pre>
 <div class="paragraph"><p>If you’ve already installed Nginx before, but without Phusion Passenger support, then you <strong>should</strong> uninstall it first. You don’t have to, because you can also install another Nginx with Phusion Passenger support, in parallel to the existing Nginx. We merely recommend uninstalling the existing in order to avoid user confusion, but the choice is yours.</p></div>
 <div class="paragraph"><p>If you had previously installed Nginx with Phusion Passenger support, and you are upgrading, then you don’t have to uninstall your existing Nginx first. Instead we’ll overwrite it this step. But it is important that you recompile Nginx with the configure parameters that you used last time.</p></div>
 <div class="paragraph"><p>Here’s how you can uninstall the original Nginx:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 If you installed the existing Nginx through APT, run: <span class="monospaced">sudo apt-get remove nginx nginx-full nginx-light nginx-naxsi nginx-common</span>
@@ -1690,7 +1687,7 @@ sudo apt-get update</pre>
 <div class="paragraph"><p>You’ll then need to enable the Phusion Passenger module in Nginx by creating the following configuration file:</p></div>
 <div class="listingblock">
 <div class="content monospaced">
-<pre>sudo sh -c 'echo "passenger_root /usr/lib/phusion-passenger;" &gt; /etc/nginx/conf.d/passenger.conf'</pre>
+<pre>sudo sh -c 'echo "passenger_root /usr/lib/ruby/vendor_ruby/phusion_passenger/locations.ini;" &gt; /etc/nginx/conf.d/passenger.conf'</pre>
 </div>
 </div>
 <div class="paragraph"><p>Then restart Nginx to apply the changes:</p></div>
@@ -1779,7 +1776,7 @@ sudo apt-get update</pre>
 <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-1a58c2b" data-anchor="_upgrading_from_open_source_to_enterprise">2.6. 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">
+<div class="olist arabic"><ol class="arabic">
 <li>
 <p>
 <a href="#uninstalling">Uninstall the open source Phusion Passenger</a>.
@@ -1917,18 +1914,18 @@ http://www.gnu.org/software/src-highlite -->
 </div>
 </div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<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>
+</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-1jehjon" data-anchor="_adding_additional_compiler_or_linker_flags">2.9.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>
+<div class="dlist"><dl>
 <dt class="hdlist1">
 <span class="monospaced">EXTRA_PRE_CFLAGS</span>
 </dt>
@@ -1979,19 +1976,19 @@ http://www.gnu.org/software/src-highlite -->
 </dd>
 </dl></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<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>
+</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-certain-command-line-tools-1j93cki" data-anchor="_forcing_location_of_command_line_tools_and_dependencies">2.9.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>
+<div class="dlist"><dl>
 <dt class="hdlist1">
 <span class="monospaced">HTTPD</span>
 </dt>
@@ -2052,12 +2049,13 @@ http://www.gnu.org/software/src-highlite -->
 </dd>
 </dl></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<img src="./images/icons/tip.png" alt="Tip">
 </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>
+<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>.
+NOTE: 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>
@@ -2089,7 +2087,7 @@ line into your Nginx configuration file:</p></div>
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="nginx_init_script"></span><h3 data-comment-topic="creating-an-nginx-init-script-1kd8zg5" data-anchor="nginx_init_script">2.11. Creating an Nginx init script</h3>
 <div class="paragraph"><p>If you installed Nginx with one of the generic installation methods then you won’t have an init script to start, stop and restart Nginx with. A bare Nginx installation works with signals: you start it by invoking it from the command line, you stop it by sending SIGTERM to it and you gracefully restart it by sending SIGHUP to it.</p></div>
 <div class="paragraph"><p>If you prefer to use an init script then please refer to the following resources:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 <a href="http://wiki.nginx.org/Nginx-init-ubuntu">Init script for Ubuntu 8.04-9.10</a>
@@ -2169,7 +2167,7 @@ http {
 <div class="paragraph"><p>To uninstall Phusion Passenger, please first remove all Phusion Passenger
 configuration directives from your web server configuration file(s). After you’ve
 done this, you need to remove the Phusion Passenger files.</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <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>).
@@ -2220,14 +2218,14 @@ virtual host’s root (i.e. the application will be accessible from the root URL
 <em>http://www.mycook.com/</em>), or in a sub URI (i.e. the application will be
 accessible from a sub URL, such as <em>http://www.mycook.com/railsapplication</em>).</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">The default <span class="monospaced">RAILS_ENV</span> environment in which deployed Rails applications
 are run, is “production”. You can change this by changing the
 <a href="#RailsEnv">rails_env</a> configuration option.</td>
-</tr></table>
+</tr></table>
 </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="_deploying_to_a_virtual_host_8217_s_root"></span><h3 data-comment-topic="deploying-to-a-virtual-host-s-root-1mh24z5" data-anchor="_deploying_to_a_virtual_host_8217_s_root">3.1. Deploying to a virtual host’s root</h3>
@@ -2301,9 +2299,9 @@ option to the <em>server</em> block:</p></div>
 </div>
 <div class="paragraph"><p>Then restart Nginx. The application has now been deployed.</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/tip.png" alt="Tip">
+<img src="./images/icons/tip.png" alt="Tip">
 </td>
 <td class="content">
 <div class="paragraph"><p>You can deploy multiple Rails applications under a virtual host, by specifying
@@ -2319,7 +2317,7 @@ option to the <em>server</em> block:</p></div>
 </div>
 </div>
 </td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect2">
@@ -2327,7 +2325,7 @@ option to the <em>server</em> block:</p></div>
 <div class="paragraph"><p>Deploying a new version of a Ruby on Rails application is as simple as
 re-uploading the application files, and restarting the application.</p></div>
 <div class="paragraph"><p>There are two ways to restart the application:</p></div>
-<div class="olist arabic"><ol class="arabic">
+<div class="olist arabic"><ol class="arabic">
 <li>
 <p>
 By restarting Nginx.
@@ -2374,7 +2372,7 @@ a shell console, just like one would normally run migrations.</p></div>
 <div class="paragraph"><p>Phusion Passenger assumes that Rack application directories have a certain layout.
 Suppose that you have a Rack application in <em>/webapps/rackapp</em>. Then that
 folder must contain at least three entries:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 <em>config.ru</em>, a Rackup file for starting the Rack application. This file must contain
@@ -2410,14 +2408,14 @@ to the virtual host’s root (i.e. the application will be accessible from the r
 <em>http://www.rackapp.com/</em>), or in a sub URI (i.e. the application will be
 accessible from a sub URL, such as <em>http://www.rackapp.com/rackapp</em>).</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">The default <span class="monospaced">RACK_ENV</span> environment in which deployed Rack applications
 are run, is “production”. You can change this by changing the
 <a href="#RackEnv">rack_env</a> configuration option.</td>
-</tr></table>
+</tr></table>
 </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="_tutorial_example_writing_and_deploying_a_hello_world_rack_application"></span><h3 data-comment-topic="tutorial-example-writing-and-deploying-a-hello-world-rack-application-1wstx99" data-anchor="_tutorial_example_writing_and_deploying_a_hello_world_rack_application">4.1. Tutorial/example: writing and deploying a Hello World Rack application</h3>
@@ -2532,9 +2530,9 @@ option to the <em>server</em> block:</p></div>
 </div>
 <div class="paragraph"><p>Then restart Nginx. The application has now been deployed.</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/tip.png" alt="Tip">
+<img src="./images/icons/tip.png" alt="Tip">
 </td>
 <td class="content">
 <div class="paragraph"><p>You can deploy multiple Rack applications under a virtual host, by specifying
@@ -2550,7 +2548,7 @@ option to the <em>server</em> block:</p></div>
 </div>
 </div>
 </td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect2">
@@ -2558,7 +2556,7 @@ option to the <em>server</em> block:</p></div>
 <div class="paragraph"><p>Deploying a new version of a Rack application is as simple as
 re-uploading the application files, and restarting the application.</p></div>
 <div class="paragraph"><p>There are two ways to restart the application:</p></div>
-<div class="olist arabic"><ol class="arabic">
+<div class="olist arabic"><ol class="arabic">
 <li>
 <p>
 By restarting Nginx.
@@ -2681,7 +2679,7 @@ run Sinatra::Application</pre>
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_deploying_a_wsgi_python_application"></span><h2 data-comment-topic="deploying-a-wsgi-python-application-1or2efo" data-anchor="_deploying_a_wsgi_python_application">5. Deploying a WSGI (Python) application</h2>
 <div class="sectionbody">
 <div class="paragraph"><p>Phusion Passenger supports all WSGI-compliant Python web applications. Suppose that you have a WSGI application in <em>/webapps/wsgiapp</em>. Then that folder must contain at least three entries:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 <em>passenger_wsgi.py</em>, which Phusion Passenger will use as the main entry point for your application. This file must export a WSGI object called <span class="monospaced">application</span>.
@@ -2778,7 +2776,7 @@ root must point to your WSGI application’s <em>public</em> folder. You must al
 <div class="paragraph"><p>Deploying a new version of a WSGI application is as simple as
 re-uploading the application files, and restarting the application.</p></div>
 <div class="paragraph"><p>There are two ways to restart the application:</p></div>
-<div class="olist arabic"><ol class="arabic">
+<div class="olist arabic"><ol class="arabic">
 <li>
 <p>
 By restarting Nginx.
@@ -2819,12 +2817,12 @@ this option as well. Please read
 <a href="#moving_phusion_passenger">Moving Phusion Passenger to a different directory</a> for more information.</p></div>
 <div class="paragraph"><p>This required option may only occur once, in the <em>http</em> configuration block.</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">This option has no effect when you are using <a href="#flying_passenger">Flying Passenger</a>.</td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect2">
@@ -2832,7 +2830,7 @@ this option as well. Please read
 <div class="paragraph"><p>The <span class="monospaced">passenger_ruby</span> option allows one to specify the Ruby interpreter to use. Similarly, the <span class="monospaced">passenger_python</span> option is for specifying the Python interpreter.</p></div>
 <div class="paragraph"><p>In versions prior to 4.0.0, only a single Ruby version was supported for the entire Nginx instance, so <span class="monospaced">passenger_ruby</span> may only occur in the global server configuration. Also, the <span class="monospaced">passenger_python</span> option was not supported.</p></div>
 <div class="paragraph"><p>Since version 4.0.0, the <span class="monospaced">passenger_python</span> option was added. Also, Phusion Passenger supports multiple Ruby or Python interpreters in the same Nginx instance. And so, since version 4.0.0, this option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -2974,7 +2972,7 @@ is the parent directory of the <em>public</em> directory. This option allows one
 specify the application’s root independently from the Nginx <em>root</em>, which
 is useful if the <em>public</em> directory lives in a non-standard place.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -3014,9 +3012,9 @@ In an <em>if</em> configuration scope.
 <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="PassengerSpawnMethod"></span><h3 data-comment-topic="passenger-spawn-method-string--1sc6njl" data-anchor="PassengerSpawnMethod">6.5. passenger_spawn_method &lt;string&gt;</h3>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/tip.png" alt="Tip">
+<img src="./images/icons/tip.png" alt="Tip">
 </td>
 <td class="content">
 <div class="title">"What spawn method should I use?"</div>
@@ -3031,12 +3029,12 @@ understand it, as it’s mostly a technical detail. You can basically follow thi
 <div class="paragraph"><p>However, we do recommend you to try to understand it. The <em>smart</em> spawn
 method brings many benefits.</p></div>
 </td>
-</tr></table>
+</tr></table>
 </div>
 <div class="paragraph"><p>Internally, Phusion Passenger spawns multiple Ruby application processes in order to handle
 requests. But there are multiple ways with which processes can be spawned, each having
 its own set of pros and cons. Supported spawn methods are:</p></div>
-<div class="dlist"><dl>
+<div class="dlist"><dl>
 <dt class="hdlist1">
 <em>smart</em>
 </dt>
@@ -3080,7 +3078,7 @@ to <em>smart</em>. The old <em>smart</em> spawning has been removed in favor of
 </div>
 </div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -3114,7 +3112,7 @@ of a new application process could take a while, and any requests that
 come in during this time will be blocked until this first application
 process has spawned.</p></div>
 <div class="paragraph"><p>But when rolling restarts are enabled, Phusion Passenger Enterprise will:</p></div>
-<div class="olist arabic"><ol class="arabic">
+<div class="olist arabic"><ol class="arabic">
 <li>
 <p>
 Spawn a new process in the background.
@@ -3133,7 +3131,7 @@ Step 1 and 2 are repeated until all processes have been replaced.
 </ol></div>
 <div class="paragraph"><p>This way, visitors will not experience any delays when you are restarting your application. This allows you to, for example, upgrade your application often without degrading user experience.</p></div>
 <div class="paragraph"><p>Rolling restarts have a few caveat however that you should be aware of:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 Upgrading an application sometimes involves upgrading the database schema.
@@ -3153,7 +3151,7 @@ Because there’s no telling which process will serve a request, users may
 </li>
 </ul></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -3183,7 +3181,7 @@ In an <em>if</em> configuration scope.
 <div class="paragraph"><p>Enables or disables resistance against deployment errors.</p></div>
 <div class="paragraph"><p>Suppose you’ve upgraded your application and you’ve issues a command to restart it (by touching restart.txt), but the application code contains an error that prevents Phusion Passenger from successfully spawning a process (e.g. a syntax error). Phusion Passenger would normally display an error message in response to this.</p></div>
 <div class="paragraph"><p>By enabling deployment error resistance, Phusion Passenger Enterprise would instead do this:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 It passes the request to one of the existing application processes (that belong to the previous version of the application). The visitor will not see a Phusion Passenger process spawning error message.
@@ -3203,7 +3201,7 @@ It sets an internal flag so that no processes for this application will be spawn
 <div class="paragraph"><p>This way, visitors will suffer minimally from deployment errors. Phusion Passenger will attempt to restart the application again next time restart.txt is touched.</p></div>
 <div class="paragraph"><p>Enabling deployment error resistance only works if <a href="#PassengerRollingRestarts">rolling restart</a> is also enabled.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -3255,12 +3253,12 @@ sudo -E passenger-status
 </div>
 </div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">This option has no effect when you are using <a href="#flying_passenger">Flying Passenger</a>. Instead, you should configure this by passing the <span class="monospaced">--temp-dir</span> command line option to the Flying Passenger daemon.</td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect2">
@@ -3292,7 +3290,7 @@ for an example.</p></div>
 <div class="paragraph"><p>It is allowed to specify this option multiple times. Do this to deploy multiple
 applications in different sub-URIs under the same virtual host.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -3330,7 +3328,7 @@ read the application process’s response while discarding all the read data. Th
 EPIPE errors but it’ll also mean the backend process will be unavailable for new requests
 until it is done sending its response.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -3382,7 +3380,7 @@ passenger_set_cgi_param HTTP_X_FORWARDED_FOR 127.0.0.2;</pre>
 </div>
 </div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -3420,7 +3418,7 @@ anyway, similar to how <em>proxy_pass_header</em> works.</p></div>
 </div>
 </div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -3448,7 +3446,7 @@ In an <em>if</em> configuration scope.
 <div class="paragraph"><p>When turned on, application-generated responses are buffered by Nginx. Buffering will
 happen in memory and also on disk if the response is larger than a certain threshold.</p></div>
 <div class="paragraph"><p>Before we proceed with explaining this configuration option, we want to state the following to avoid confusion. If you use Phusion Passenger for Nginx, there are in fact two response buffering systems active:</p></div>
-<div class="olist arabic"><ol class="arabic">
+<div class="olist arabic"><ol class="arabic">
 <li>
 <p>
 The Nginx response buffering system. <span class="monospaced">passenger_buffer_response</span> turns this on or off.
@@ -3508,7 +3506,7 @@ after which it receives the entire response at once.
 When <span class="monospaced">passenger_buffer_response</span> is turned off, it works as expected: the client
 receives an "entry X" message every second for 10 seconds.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -3552,12 +3550,12 @@ They can be used to modify the maximum allowed HTTP header size.</p></div>
 <div class="paragraph"><p>This option may only occur once, in the <em>http</em> configuration block.
 The default value is <em>on</em>.</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">This option has no effect when you are using <a href="#flying_passenger">Flying Passenger</a>. You can disable user switching for Flying Passenger by starting the Flying Passenger daemon as a non-root user.</td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect3">
@@ -3568,7 +3566,7 @@ by default run the web application as the owner of the file <em>config/environme
 that behavior and explicitly set a user to run the web application as, regardless
 of the ownership of <em>environment.rb</em>/<em>config.ru</em>.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -3602,7 +3600,7 @@ as, regardless of the ownership of <em>environment.rb</em>/<em>config.ru</em>.</
 <div class="paragraph"><p><em>&lt;group name&gt;</em> may also be set to the special value <em>!STARTUP_FILE!</em>, in which case
 the web application’s group will be set to <em>environment.rb</em>/<em>config.ru</em>'s group.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -3634,12 +3632,12 @@ run as, if user switching fails or is disabled.</p></div>
 <div class="paragraph"><p>This option may only occur once, in the <em>http</em> configuration block.
 The default value is <em>nobody</em>.</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">This option has no effect when you are using <a href="#flying_passenger">Flying Passenger</a>. There is currently no way to set this option when using Flying Passenger, but if you want to disable user switching for Flying Passenger then you can do so by starting the Flying Passenger daemon as a non-root user.</td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect3">
@@ -3651,12 +3649,12 @@ run as, if user switching fails or is disabled.</p></div>
 The default value is the primary group of the user specifified by
 <a href="#PassengerDefaultUser">passenger_default_user</a>.</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">This option has no effect when you are using <a href="#flying_passenger">Flying Passenger</a>. There is currently no way to set this option when using Flying Passenger, but if you want to disable user switching for Flying Passenger then you can do so by starting the Flying Passenger daemon as a non-root user.</td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect3">
@@ -3676,7 +3674,7 @@ X-Powered-By: Phusion Passenger</pre>
 </div>
 </div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -3710,7 +3708,7 @@ but the page might reveal potentially sensitive information, depending on the
 application. Experienced system administrators who are using Phusion Passenger
 on serious production servers should consider turning this feature off.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -3747,12 +3745,12 @@ but improves the ability to handle concurrent HTTP requests.</p></div>
 <div class="paragraph"><p>This option may only occur once, in the <em>http</em> configuration block.
 The default value is <em>6</em>.</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">This option has no effect when you are using <a href="#flying_passenger">Flying Passenger</a>. Instead, you should configure this by passing the <span class="monospaced">--max-pool-size</span> command line option to the Flying Passenger daemon.</td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect3">
@@ -3763,7 +3761,7 @@ non-zero value if you want to avoid potentially long startup times after a websi
 has been <a href="#idle_process">idle</a> for an extended period.</p></div>
 <div class="paragraph"><p>Please note that this option does <strong>not</strong> pre-start application processes during Nginx
 startup. It just makes sure that when the application is first accessed:</p></div>
-<div class="olist arabic"><ol class="arabic">
+<div class="olist arabic"><ol class="arabic">
 <li>
 <p>
 at least the given number of processes will be spawned.
@@ -3806,7 +3804,7 @@ simultanously. Phusion Passenger will start 12 more application processes. After
 timeout of 10 seconds have passed, Phusion Passenger will clean up 12 application
 processes, keeping 3 processes around.</p></div>
 <div class="paragraph"><p>The passenger_min_instances option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -3841,7 +3839,7 @@ means that there is no limit placed on the number of processes a single applicat
 may spawn, i.e. only the global limit of <a href="#PassengerMaxPoolSize">passenger_max_pool_size</a>
 will be enforced.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -3865,9 +3863,9 @@ In an <em>if</em> configuration scope.
 </ul></div>
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>0</em>.</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/tip.png" alt="Tip">
+<img src="./images/icons/tip.png" alt="Tip">
 </td>
 <td class="content">
 <div class="title">Practical usage example</div>
@@ -3878,7 +3876,7 @@ to 10. The e-commerce website is more important to you. You can then set
 than 3 processes, even if it suddenly gets a lot of traffic. Your e-commerce website
 on the other hand will be free to spawn up to 10 processes if it gets a lot of traffic.</p></div>
 </td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect3">
@@ -3915,12 +3913,12 @@ applications, each which must be available at all times.</p></div>
 <div class="paragraph"><p>This option may only occur once, in the <em>http</em> configuration block.
 The default value is <em>300</em>.</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">This option has no effect when you are using <a href="#flying_passenger">Flying Passenger</a>. Instead, you should configure this by passing the <span class="monospaced">--pool-idle-time</span> command line option to the Flying Passenger daemon.</td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect3">
@@ -3938,7 +3936,7 @@ you’re using the <em>smart</em> or <em>smart-lv2</em> <a href="#RailsSpawnMeth
 system has enough memory, is it recommended that you set this option to a high
 value or to <em>0</em>.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -3962,19 +3960,19 @@ In an <em>if</em> configuration scope.
 </ul></div>
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>300</em> (5 minutes).</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">This option has no effect when you are using <a href="#flying_passenger">Flying Passenger</a>. Instead, you should configure this by passing the <span class="monospaced">--max-preloader-idle-time</span> command line option to the Flying Passenger daemon.</td>
-</tr></table>
+</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="PassengerConcurrencyModel"></span><h4 data-comment-topic="passenger-concurrency-model-process-thread--brcvkk" data-anchor="PassengerConcurrencyModel">6.13.7. passenger_concurrency_model &lt;process|thread&gt;</h4>
 <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 4.0.0. <a href="https://www.phusionpassenger.com/download">Buy Phusion Passenger Enterprise here.</a></strong></p></div>
 <div class="paragraph"><p>Specifies the I/O concurrency model that should be used for application processes. Phusion Passenger supports two concurrency models:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 <em>process</em> - single-threaded, multi-processed I/O concurrency. Each application process only has a single thread and can only handle 1 request at a time. This is the concurrency model that Ruby applications traditionally used. It has excellent compatiblity (can work with applications that are not designed to be thread-safe) but is unsuitable workloads in which the application has to wait for a lot of external I/O (e.g. HTTP API calls), and uses more memory because each process has a large memory overhead.
@@ -3987,7 +3985,7 @@ In an <em>if</em> configuration scope.
 </li>
 </ul></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -4016,7 +4014,7 @@ In an <em>if</em> configuration scope.
 <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 4.0.0. <a href="https://www.phusionpassenger.com/download">Buy Phusion Passenger Enterprise here.</a></strong></p></div>
 <div class="paragraph"><p>Specifies the number of threads that Phusion Passenger should spawn per application process. This option only has effect if <a href="#PassengerConcurrencyModel">passenger_concurrency_model</a> is <em>thread</em>.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -4051,7 +4049,7 @@ reached.</p></div>
 it down after a certain number of requests, all of its memory is guaranteed
 to be freed by the operating system.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -4075,9 +4073,9 @@ In an <em>if</em> configuration scope.
 </ul></div>
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>0</em>.</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/caution.png" alt="Caution">
+<img src="./images/icons/caution.png" alt="Caution">
 </td>
 <td class="content">
 <div class="paragraph"><p>The <a href="#PassengerMaxRequests">passenger_max_requests</a> directive should be considered
@@ -4085,7 +4083,7 @@ as a workaround for misbehaving applications. It is advised that you fix the
 problem in your application rather than relying on these directives as a
 measure to avoid memory leaks.</p></div>
 </td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect3">
@@ -4098,7 +4096,7 @@ restarted upon the next request. A value of 0 means that there is no time limit.
 <div class="paragraph"><p>This option is useful for preventing your application from freezing for an
 indefinite period of time.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -4146,9 +4144,9 @@ to 10 seconds. You can then configure Phusion Passenger as follows:</p>
 or if a request to any other URI takes more than 2 seconds,
 then the corresponding application process will be forced to shutdown.</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/caution.png" alt="Caution">
+<img src="./images/icons/caution.png" alt="Caution">
 </td>
 <td class="content">
 <div class="paragraph"><p>The <a href="#PassengerMaxRequestTime">passenger_max_request_time</a> directive should be
@@ -4156,18 +4154,18 @@ considered as a workaround for misbehaving applications. It is advised that you
 fix the problem in your application rather than relying on these directives as a
 measure to avoid freezing applications.</p></div>
 </td>
-</tr></table>
+</tr></table>
 </div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">
 <div class="paragraph"><p>This option is currently only available for Ruby apps. It is not yet available
 for Python and Node.js.</p></div>
 </td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect3">
@@ -4181,7 +4179,7 @@ will not be checked.</p></div>
 <div class="paragraph"><p>This option is useful if your application is leaking memory. By shutting
 it down, all of its memory is guaranteed to be freed by the operating system.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -4205,9 +4203,9 @@ In an <em>if</em> configuration scope.
 </ul></div>
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>0</em>.</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">
 <div class="title">A word about permissions</div>
@@ -4218,12 +4216,12 @@ not obtainable through <span class="monospaced">ps</span>. You should ensure tha
 correctly and that the <span class="monospaced">/proc</span> filesystem is accessible by the
 <span class="monospaced">PassengerHelperAgent</span> process.</p></div>
 </td>
-</tr></table>
+</tr></table>
 </div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/caution.png" alt="Caution">
+<img src="./images/icons/caution.png" alt="Caution">
 </td>
 <td class="content">
 <div class="paragraph"><p>The <a href="#PassengerMaxRequests">passenger_max_requests</a> and
@@ -4232,7 +4230,7 @@ as workarounds for misbehaving applications. It is advised that you fix the
 problem in your application rather than relying on these directives as a
 measure to avoid memory leaks.</p></div>
 </td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect3">
@@ -4243,14 +4241,14 @@ web application might experience a small delay as Phusion Passenger is starting
 the web application on demand. If that is undesirable, then this directive can be
 used to pre-started application processes during Nginx startup.</p></div>
 <div class="paragraph"><p>A few things to be careful of:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 This directive accepts the <strong>URL</strong> of the web application you want to pre-start,
   not a on/off value! This might seem a bit weird, but read on for rationale. As
   for the specifics of the URL:
 </p>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 The domain part of the URL must be equal to the value of the <em>server_name</em>
@@ -4283,12 +4281,12 @@ You will probably want to combine this option with
 <div class="paragraph"><p>This option may only occur in the <em>http</em> configuration block. It may be specified
 any number of times.</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">This option is currently not available when using <a href="#flying_passenger">Flying Passenger</a>.</td>
-</tr></table>
+</tr></table>
 </div>
 <div class="sect4">
 <h5 id="_example_1_basic_usage">Example 1: basic usage</h5>
@@ -4466,7 +4464,7 @@ the request ending up at a different web server in the cluster.</p></div>
 write to the Nginx error log file. A higher log level value means that more
 information will be logged.</p></div>
 <div class="paragraph"><p>Possible values are:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 <em>0</em>: Show only errors and warnings.
@@ -4500,12 +4498,12 @@ web server error log. This option allows one to specify the file that debugging
 error messages should be written to instead.</p></div>
 <div class="paragraph"><p>This option may only occur once, in the <em>http</em> configuration block.</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">This option has no effect when you are using <a href="#flying_passenger">Flying Passenger</a>. Instead, you should configure this by passing the <span class="monospaced">--log-file</span> command line option to the Flying Passenger daemon.</td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect3">
@@ -4523,7 +4521,7 @@ gem 'debugger', :platforms =&gt; :ruby_19</pre>
 </div>
 <div class="paragraph"><p>Once debugging is turned on, you can use the command <span class="monospaced">passenger-irb --debug &lt;PID&gt;</span> to attach an rdebug console to the application process with the given PID. Attaching will succeed once the application process executes a <span class="monospaced">debugger</span> command.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -4554,7 +4552,7 @@ In an <em>if</em> configuration scope.
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="RailsEnv"></span><h4 data-comment-topic="rails-env-string--jlh7v9" data-anchor="RailsEnv">6.15.1. rails_env &lt;string&gt;</h4>
 <div class="paragraph"><p>This option allows one to specify the default <span class="monospaced">RAILS_ENV</span> value.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -4585,7 +4583,7 @@ In an <em>if</em> configuration scope.
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="RackEnv"></span><h4 data-comment-topic="rack-env-string--tqmrt0" data-anchor="RackEnv">6.16.1. rack_env &lt;string&gt;</h4>
 <div class="paragraph"><p>This option allows one to specify the default <span class="monospaced">RACK_ENV</span> value.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 In the <em>http</em> configuration block.
@@ -4675,14 +4673,14 @@ we see that all the Apache and Nginx worker processes only take less than 1 MB m
 This is a lot less than the 50-80 MB-ish memory usage as shown in the <em>VMSize</em> column
 (which is what a lot of people think is the real memory usage, but is actually not).</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">Private dirty RSS reporting only works on Linux. Unfortunately other operating systems
 don’t provide facilities for determining processes' private dirty RSS. On non-Linux systems,
 the Resident Set Size is reported instead.</td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect2">
@@ -4704,7 +4702,7 @@ inactive = 1
 </div>
 </div>
 <div class="paragraph"><p>The <em>general information</em> section shows the following information:</p></div>
-<div class="dlist"><dl>
+<div class="dlist"><dl>
 <dt class="hdlist1">
 max
 </dt>
@@ -4748,7 +4746,7 @@ time). The value of <em>inactive</em> equals <span class="monospaced">count - ac
 </dl></div>
 <div class="paragraph"><p>The <em>domains</em> section shows, for each application directory, information about running
 application instances:</p></div>
-<div class="dlist"><dl>
+<div class="dlist"><dl>
 <dt class="hdlist1">
 Sessions
 </dt>
@@ -4815,13 +4813,13 @@ This is the case with Ruby on Rails. So if you kill a Ruby on Rails application
 running it in a <em>production</em> environment). If you don’t see a backtrace there, check
 the web server error log.</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">It is safe to kill application instances, even in live environments. Phusion Passenger
 will restart killed application instances, as if nothing bad happened.</td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect2">
@@ -4830,7 +4828,7 @@ will restart killed application instances, as if nothing bad happened.</td>
 the request to the most suitable application process, but sometimes it is desirable to
 be able to directly access the individual application processes. Use cases include, but
 are not limited to:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 One wants to debug a memory leak or memory bloat problem that only seems to appear on
@@ -4918,12 +4916,12 @@ and they’re explained further down in this section.</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="_requirements"></span><h4 data-comment-topic="requirements-15ozqdj" data-anchor="_requirements">8.1.1. Requirements</h4>
 <div class="paragraph"><p>User switching is only enabled when all of the following conditions are met:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 When not using <a href="#flying_passenger">Flying Passenger</a> (this is probably the case):
 </p>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 The
@@ -4942,7 +4940,7 @@ The web server’s control process must have root privileges. This is the case o
 <p>
 When using <a href="#flying_passenger">Flying Passenger</a>:
 </p>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 The Flying Passenger daemon must be run with root privileges.
@@ -4957,49 +4955,49 @@ The Flying Passenger daemon must be run with root privileges.
 <div class="paragraph"><p>When not using Flying Passenger, the following table illustrates the effect for different combinations of the requirements.</p></div>
 <table class="tableblock frame-all grid-all" style="
 width:100%;
-">
-<col style="width:33%;">
-<col style="width:33%;">
-<col style="width:33%;">
-<tbody>
-<tr>
+">
+<col style="width:33%;">
+<col style="width:33%;">
+<col style="width:33%;">
+<tbody>
+<tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock"></p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock"><strong>passenger_user_switching on</strong></p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock"><strong>passenger_user_switching off</strong></p></td>
-</tr>
-<tr>
+</tr>
+<tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Web server has root privileges</strong></p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">User switching enabled.</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">User switching disabled. Apps are run as
   <a href="#PassengerDefaultUser">passenger_default_user</a> and
   <a href="#PassengerDefaultGroup">passenger_default_group</a>.</p></td>
-</tr>
-<tr>
+</tr>
+<tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Web server has no root privileges</strong></p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">User switching disabled. Apps are run as the web server’s user.</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">User switching disabled. Apps are run as the web server’s user.</p></td>
-</tr>
-</tbody>
-</table>
+</tr>
+</tbody>
+</table>
 <div class="paragraph"><p>When using Flying Passenger, the effect is as follows:</p></div>
 <table class="tableblock frame-all grid-all" style="
 width:100%;
-">
-<col style="width:50%;">
-<col style="width:50%;">
-<tbody>
-<tr>
+">
+<col style="width:50%;">
+<col style="width:50%;">
+<tbody>
+<tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Daemon run with root privileges</strong></p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">User switching enabled.</p></td>
-</tr>
-<tr>
+</tr>
+<tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock"><strong>Daemon run without root privileges</strong></p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">User switching disabled. Apps are run as the daemon’s user.</p></td>
-</tr>
-</tbody>
-</table>
+</tr>
+</tbody>
+</table>
 <div class="paragraph"><p>When user switching is enabled, the following rules are followed to determine what user an application should be run as. The first matching rule is the rule that will be followed.</p></div>
-<div class="olist arabic"><ol class="arabic">
+<div class="olist arabic"><ol class="arabic">
 <li>
 <p>
 If
@@ -5025,7 +5023,7 @@ Otherwise, the application is run as the owner of the startup file.
 <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="_caveats_amp_troubleshooting"></span><h4 data-comment-topic="caveats-troubleshooting-mbw582" data-anchor="_caveats_amp_troubleshooting">8.1.3. Caveats &amp; troubleshooting</h4>
 <div class="paragraph"><p>If your application regularly encounters permission errors or fails to find certain files, then this is an indication that your application is started as a user that you did not intent it to be run as. Other symptoms include:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 The application fails to start because Bundler complains that it cannot find gems. This probably indicates that Bundler does not have read access to the directory that contains Bundler-installed gems.
@@ -5082,7 +5080,7 @@ Requests in top-level queue : 0
 <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="reducing_memory_usage"></span><h3 data-comment-topic="reducing-memory-consumption-of-ruby-on-rails-applications-by-33--1o3z66q" data-anchor="reducing_memory_usage">8.2. Copy-on-write memory support (reducing memory consumption of Ruby applications)</h3>
 <div class="paragraph"><p>Phusion Passenger automatically leverages operating system virtual memory copy-on-write features in order to reduce the memory usage of Ruby applications. Experience has shown that this reduces memory usage by 33% on average. For this mechanism to work, a Ruby interpreter with a copy-on-write friendly garbage collector is required. The following Ruby interpreters have copy-on-write friendly garbage collectors:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 MRI Ruby &gt;= 2.0. Versions prior to 2.0 did not have a copy-on-write friendly garbage collector.
@@ -5136,7 +5134,7 @@ end</pre>
 The support consists of loading your application under the environment defined by your
 Gemfile. In other words, Phusion Passenger loads your application as if <em>bundle exec</em> was used.</p></div>
 <div class="paragraph"><p>The Bundler support works as follows:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 If you have a <em>.bundle/environment.rb</em> in your application root, then Phusion
@@ -5201,9 +5199,9 @@ application’s root folder. Unlike <em>restart.txt</em>, Phusion Passenger does
 check for this file’s timestamp: Phusion Passenger will always restart the
 application, as long as <em>always_restart.txt</em> exists.</p></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">If you’re just developing a Rails application then you probably don’t need
 this feature. If you set
@@ -5213,7 +5211,7 @@ then Rails will automatically reload your application code after each request.
 <em>always_restart.txt</em> is mostly useful when you’re using a web framework that
 doesn’t support code reloading by itself, of when you’re working on a web framework
 yourself.</td>
-</tr></table>
+</tr></table>
 </div>
 </div>
 <div class="sect2">
@@ -5261,7 +5259,7 @@ please refer to
 <div class="paragraph"><p>The Out-of-Band Work feature allows you to run arbitrary long-running tasks outside normal request cycles. This works by letting current requests to the process finish, then telling the process to perform the out-of-band work, then resuming passing requests to the process after said work is finished.</p></div>
 <div class="paragraph"><p>A specific (and perhaps primary) use case of of Out-of-Band Work is <strong>Out-of-Band Garbage Collection</strong>. The garbage collector is run outside normal request cycles so that garbage collection runs inside normal request cycles can finish a lot faster. This can potentially save tens to hundreds of milliseconds of latency in requests.</p></div>
 <div class="paragraph"><p>Because Out-of-Band Work is implemented at the Phusion Passenger inter-process request routing level, and not by, say, spawning a thread inside the application process, Out-of-Band Work has the following useful properties:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 It works well even with tasks that can pause all threads. The MRI Ruby garbage collector is a stop-the-world mark-and-sweep garbage collector.
@@ -5274,7 +5272,7 @@ Phusion Passenger can spawn more processes as necessary, in order to prevent sit
 </li>
 </ul></div>
 <div class="paragraph"><p>Applications can use Out-of-Band Work as follows:</p></div>
-<div class="olist arabic"><ol class="arabic">
+<div class="olist arabic"><ol class="arabic">
 <li>
 <p>
 Request out-of-band work by outputting the <span class="monospaced">X-Passenger-Request-OOB-Work</span> header during a request. It does not matter what the value is. At this time, it is not possible to request out-of-band work from outside requests.
@@ -5326,7 +5324,7 @@ http://www.gnu.org/software/src-highlite -->
 </div>
 <div class="paragraph"><p>It should be noted that, although the application uses the Phusion Passenger API, it is <a href="#add_passenger_to_gemfile"><strong>not</strong> necessary to add Phusion Passenger to the Gemfile</a>.</p></div>
 <div class="paragraph"><p>References:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 <a href="http://blog.phusion.nl/2013/01/22/phusion-passenger-4-technology-preview-out-of-band-work/">The Phusion Blog article which first introduced this feature.</a>
@@ -5340,7 +5338,7 @@ http://www.gnu.org/software/src-highlite -->
 <div class="paragraph"><p>Flying Passenger allows one to decouple Phusion Passenger’s life time from the web server’s life time, so that the web server can be independently restarted from Phusion Passenger, and from any of the application processes served by Phusion Passenger.</p></div>
 <div class="paragraph"><p>Normally, Phusion Passenger starts together with the web server, and shuts down together with the web server. The advantages of this default behavior is that it makes Phusion Passenger easy to administer: one only has to deal with the web server process and can expect all relevant processes to be cleaned up after a web server shut down. However this also brings about a disadvantage: every time one restarts the web server (e.g. to make a minor configuration change), Phusion Passenger and all its application processes also get restarted.</p></div>
 <div class="paragraph"><p>This problem is solved by <em>Flying Passenger</em>, which is an advanced mode of operation in Phusion Passenger that allows the web server to be indepedently restarted from Phusion Passenger. When this mode is enabled:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 One must start Phusion Passenger separately from the web server, namely by starting the Flying Passenger daemon. This daemon must - to an extent - be separately configured and managed from the web server.
@@ -5509,7 +5507,7 @@ exec /path-to/flying-passenger \
 <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="flying_passenger_caveats"></span><h4 data-comment-topic="caveats-and-limitations-15wakf" data-anchor="flying_passenger_caveats">8.9.5. Caveats and limitations</h4>
 <div class="paragraph"><p>Beware of the following caveats and limitations when using Flying Passenger:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 The Nginx executable <strong>must</strong> be compiled with the same version of Phusion Passenger as the Flying Passenger daemon. Failing to meet this requirement may result in cryptic errors, or may result in certain features not working, until you’ve fixed the situation. When upgrading Phusion Passenger, you must restart both Nginx and the Flying Passenger daemon.
@@ -5529,7 +5527,7 @@ When you add a new application to the web server configuration, Flying Passenger
 <p>
 When you remove an application from the web server configuration, Flying Passenger will not detect the removal and will not shut down the associated application processes. Killing the application processes will also not help, because Flying Passenger will restart them per the (now-removed, but still in the Flying Passenger daemon’s memory) <a href="#PassengerMinInstances">passenger_min_instances</a> settings. At the moment, there are two ways to get rid of those processes:
 </p>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 Before removing the application from the web server configuration, explicitly set its <span class="monospaced">passenger_min_instances</span> to 0. Next, send a request to it, which will cause the Flying Passenger daemon to take over the new <span class="monospaced">passenger_min_instances 0</span> option. You can then proceed with removing the application from the web server configuration, and restarting the web server. Finally, kill the PIDs associated to those application processes and remove the application configuration.
@@ -5562,7 +5560,7 @@ This check occurs after checking whether the original mapped filename exists (as
 of static asset serving). All this is done without the need for special mod_rewrite
 rules.</p></div>
 <div class="paragraph"><p>For example, suppose that the browser requests <em>/foo/bar</em>.</p></div>
-<div class="olist arabic"><ol class="arabic">
+<div class="olist arabic"><ol class="arabic">
 <li>
 <p>
 Phusion Passenger will first check whether this URI maps to a static file, i.e.
@@ -5603,7 +5601,7 @@ whether the following file exists:</p></div>
 </div>
 <div class="paragraph"><p>If you’re not a programmer and don’t understand the above pseudo-code snippet, it means
 that Phusion Passenger will:</p></div>
-<div class="olist arabic"><ol class="arabic">
+<div class="olist arabic"><ol class="arabic">
 <li>
 <p>
 Extract the parent directory filename from the value of the “root” directive.
@@ -5638,14 +5636,12 @@ Phusion Passenger will look for <em>config.ru</em> instead of <em>config/environ
 Attribution-Share Alike 3.0 Unported License</a>.</p></div>
 <div class="paragraph"><p><span class="image">
 <a class="image" href="http://creativecommons.org/licenses/by-sa/3.0/">
-<img src="images/by_sa.png" alt="images/by_sa.png">
-</a>
+<img src="images/by_sa.png" alt="images/by_sa.png"></a>
 </span></p></div>
 <div class="paragraph"><p>Phusion Passenger is brought to you by <a href="http://www.phusion.nl/">Phusion</a>.</p></div>
 <div class="paragraph"><p><span class="image">
 <a class="image" href="http://www.phusion.nl/">
-<img src="images/phusion_banner.png" alt="images/phusion_banner.png">
-</a>
+<img src="images/phusion_banner.png" alt="images/phusion_banner.png"></a>
 </span></p></div>
 <div class="paragraph"><p>Phusion Passenger is a trademark of Hongli Lai &amp; Ninh Bui.</p></div>
 </div>
@@ -5755,20 +5751,18 @@ programmers jargon, Phusion Passenger calls fork(), but not exec().</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="_the_smart_spawning_method"></span><h3 data-comment-topic="the-smart-spawning-method-7nhgtj" data-anchor="_the_smart_spawning_method">12.2. The smart spawning method</h3>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">Smart spawning is supported for all Ruby applications but not for WSGI applications.</td>
-</tr></table>
+</tr></table>
 </div>
 <div class="paragraph"><p>While direct spawning works well, it’s not as efficient as it could be
 because each worker process has its own private copy of the Rails application
 as well as the Rails framework. This wastes memory as well as startup time.</p></div>
 <div class="paragraph"><p><span class="image">
-<img src="images/direct_spawning.png" alt="Worker processes and direct spawning">
-</span><br>
-<em>Figure: Worker processes and direct spawning. Each worker process has its
+<img src="images/direct_spawning.png" alt="Worker processes and direct spawning"></span><br><em>Figure: Worker processes and direct spawning. Each worker process has its
 own private copy of the application code and Rails framework code.</em></p></div>
 <div class="paragraph"><p>It is possible to make the different worker processes share the memory occupied
 by application and Rails framework code, by utilizing so-called
@@ -5792,15 +5786,13 @@ processes will share as much common
 memory as possible. That is, they will all share the same application and Rails
 framework code.</p></div>
 <div class="paragraph"><p><span class="image">
-<img src="images/smart.png" alt="images/smart.png">
-</span><br>
-<em>Figure: Worker processes and the smart spawn method. All worker processes,
+<img src="images/smart.png" alt="images/smart.png"></span><br><em>Figure: Worker processes and the smart spawn method. All worker processes,
 as well as the ApplicationSpawner, share the same application code and Rails
 framework code.</em></p></div>
 <div class="paragraph"><p>The <em>smart</em> method allows different worker processes that belong to the same
 application to share memory.</p></div>
 <div class="paragraph"><p>Notes:</p></div>
-<div class="ulist"><ul>
+<div class="ulist"><ul>
 <li>
 <p>
 Vendored Rails frameworks cannot be shared by different applications, even if
@@ -6034,7 +6026,7 @@ has no effect.</p></div>
 <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>
+<div class="ulist"><ul>
 <li>
 <p>
 …only newly spawned bash shells see them.
@@ -6052,12 +6044,12 @@ has no effect.</p></div>
 </li>
 </ul></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<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>
+</tr></table>
 </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-1kmvq8w" data-anchor="_working_with_environment_variables">13.1. Working with environment variables</h3>
@@ -6094,9 +6086,9 @@ ruby -e <span style="color: #FF0000">'p ENV["APXS2"]'</span>
 </div>
 </div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">
 <div class="title">The "export" keyword is important</div>
@@ -6113,7 +6105,7 @@ ruby -e <span style="color: #FF0000">'p ENV["APXS2"]'</span>
 </div>
 </div>
 </td>
-</tr></table>
+</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">
@@ -6191,7 +6183,7 @@ user@localhost bash$ frobnicator
 <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-1flz2tu" data-anchor="_adding_phusion_passenger_8217_s_administration_tools_to_path">13.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>
+<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>:
@@ -6249,12 +6241,12 @@ $ sudo find . -name passenger-status
 </li>
 </ul></div>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<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>
+</tr></table>
 </div>
 </div>
 </div>
@@ -6276,23 +6268,23 @@ echo <span style="color: #FF0000">'export PATH=/usr/local/bin:$PATH'</span> <spa
 </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>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<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>.</td>
-</tr></table>
+</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="_apache"></span><h4 data-comment-topic="apache-9hqtyj" data-anchor="_apache">13.3.2. Apache</h4>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<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>
+</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>
@@ -6302,24 +6294,24 @@ echo <span style="color: #FF0000">'export PATH=/usr/local/bin:$PATH'</span> <spa
 <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-157dpwy" data-anchor="_nginx">13.3.3. Nginx</h4>
 <div class="admonitionblock">
-<table><tr>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<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>
+</tr></table>
 </div>
 <div class="paragraph"><p>If you installed Nginx through <a href="#install_on_debian_ubuntu">the Brightbox 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
 &lt;&lt;nginx_init_script,the Nginx init script described earlier in this manual,
 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>
+<table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note">
+<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>
+</tr></table>
 </div>
 </div>
 <div class="sect3">
@@ -6348,7 +6340,7 @@ PATH=/usr/bin:/usr/local/bin
 <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-uiewl5" data-anchor="env_vars_passenger_apps">13.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>
+<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.
@@ -7105,5 +7097,5 @@ Mizuho.topicListReceived = $.proxy(function(result) {
 $(document).ready(Mizuho.initializeCommenting);
 </script>
-</body>
+</body>
 </html>