passenger 4.0.60 → 5.0.0.beta1

data/doc/Users guide Apache.txt

@@ -28,154 +28,7 @@ include::users_guide_snippets/support_information.txt[]
 include::users_guide_snippets/installation.txt[]
 
 
-== Deploying a Ruby on Rails 1.x or 2.x (but NOT Rails >= 3.x) application ==
-
-Suppose you have a Ruby on Rails application in '/webapps/mycook', and you own
-the domain 'www.mycook.com'. You can either deploy your application to the
-virtual host's root (i.e. the application will be accessible from the root URL,
-'http://www.mycook.com/'), or in a sub URI (i.e. the application will be
-accessible from a sub URL, such as 'http://www.mycook.com/railsapplication').
-
-NOTE: The default `RAILS_ENV` environment in which deployed Rails applications
-are run, is ``production''. You can change this by changing the
-<<rails_env,'RailsEnv'>> configuration option.
-
-=== Deploying to a virtual host's root ===
-
-Add a virtual host entry to your Apache configuration file. Make sure that the
-following conditions are met:
-
-- The virtual host's document root must point to your Ruby on Rails application's
-  'public' folder.
-- The Apache per-directory permissions must allow access to this folder.
-- MultiViews must be disabled for this folder.
-
-For example:
--------------------------------------------
-<VirtualHost *:80>
-    ServerName www.mycook.com
-    DocumentRoot /webapps/mycook/public
-    <Directory /webapps/mycook/public>
-        Allow from all
-        Options -MultiViews
-        # Uncomment this if you're on Apache >= 2.4:
-        #Require all granted
-    </Directory>
-</VirtualHost>
--------------------------------------------
-
-You may also need to tweak your file/folder permissions. Make sure that the
-following folders are readable and executable by Apache:
-
- * this 'public' folder.
- * the application's 'config' folder.
- * all parent folders. That is, /webapps/mycook and /webapps must also be readable and executable by Apache.
-
-Then restart Apache. The application has now been deployed.
-
-[[deploying_rails_to_sub_uri]]
-=== Deploying to a sub URI ===
-
-Suppose that you already have a virtual host:
-
--------------------------------------------
-<VirtualHost *:80>
-    ServerName www.phusion.nl
-    DocumentRoot /websites/phusion
-    <Directory /websites/phusion>
-        Allow from all
-        Options -MultiViews
-        # Uncomment this if you're on Apache >= 2.4:
-        #Require all granted
-    </Directory>
-</VirtualHost>
--------------------------------------------
-
-And you want your Rails application, located in `/websites/rails`, to be accessible from the URL
-'http://www.phusion.nl/subapp'.
-
-To do this, you need to perform the following:
-
- 1. Set `Alias {SUBURI} {PATH TO YOUR APPLICATION'S PUBLIC DIRECTORY}`.
- 2. Create a `<Location /{SUBURI}>` block.
- 3. Inside the Location block, set `PassengerBaseURI /{SUBURI}`.
- 4. Inside the Location block, set `PassengerAppRoot {PATH TO YOUR APPLICATION ROOT}`.
- 5. Create a `<Directory {PATH TO YOUR APPLICATION'S PUBLIC DIRECTORY}>` block.
- 6. Inside the Directory block, set `Allow from all`, and (if you're on Apache >= 2.4) `Require all granted`.
- 7. Inside the Directory block, disable MultiViews.
-
-Here is an example:
-
--------------------------------------------
-<VirtualHost *:80>
-    ServerName www.phusion.nl
-    DocumentRoot /websites/phusion
-    <Directory /websites/phusion>
-        Allow from all
-        Options -MultiViews
-        # Uncomment this if you're on Apache >= 2.4:
-        #Require all granted
-    </Directory>
-    
-    # These have been added:
-    Alias /subapp /websites/rails/public
-    <Location /subapp>
-        PassengerBaseURI /subapp
-        PassengerAppRoot /websites/rails
-    </Location>
-    <Directory /websites/rails/public>
-        Allow from all
-        Options -MultiViews
-        # Uncomment this if you're on Apache >= 2.4:
-        #Require all granted
-    </Directory>
-</VirtualHost>
--------------------------------------------
-
-Then restart Apache. The application has now been deployed to the sub-URI.
-
-NOTE: If you're deploying to a sub-URI then please make sure that your view
-templates correctly handles references to sub-URI static assets! Otherwise
-you may find broken links to images, CSS files, JavaScripts, etc. Please read
-<<sub_uri_deployment_uri_fix,How to fix broken images/CSS/JavaScript URIs in sub-URI deployments>>
-for more information.
-
-=== Redeploying (restarting the Ruby on Rails application) ===
-
-Deploying a new version of a Ruby on Rails application is as simple as
-re-uploading the application files, and restarting the application.
-
-There are two ways to restart the application:
-
-1. By restarting Apache.
-2. By creating or modifying the file 'tmp/restart.txt' in the Rails
-   application's <<application_root,root folder>>. Phusion Passenger will
-   automatically restart the application during the next request.
-
-For example, to restart our example MyCook application, we type this in the
-command line:
--------------------------------------------
-touch /webapps/mycook/tmp/restart.txt
--------------------------------------------
-
-Please note that, unlike earlier versions of Phusion Passenger, 'restart.txt'
-is not automatically deleted. Phusion Passenger checks whether the timestamp
-of this file has changed in order to determine whether the application should
-be restarted.
-
-=== Migrations ===
-
-Phusion Passenger is not related to Ruby on Rails migrations in any way. To
-run migrations on your deployment server, please login to your deployment
-server (e.g. with 'ssh') and type `rake db:migrate RAILS_ENV=production` in
-a shell console, just like one would normally run migrations.
-
-=== Capistrano integration ===
-
-See <<capistrano,Capistrano recipe>>.
-
-
-== Deploying a Rack-based Ruby application (including Rails >= 3) ==
+== Deploying a Rack-based Ruby application ==
 
 Phusion Passenger supports arbitrary Ruby web applications that follow the
 link:http://rack.rubyforge.org/[Rack] interface.
@@ -746,6 +599,8 @@ Phusion Passenger for Apache sets the default value to **production**. If you're
 
 If you want to set other environment variables, please refer to <<env_vars_passenger_apps,Setting environment variables for Phusion Passenger-served apps>>.
 
+Setting this option also adds the application environment name to the default <<PassengerAppGroupName,application group name>>, so that you can run multiple versions of your application with different application environment names.
+
 This option may occur in the following places:
 
  * In the global server configuration.
@@ -791,6 +646,78 @@ Example:
 </VirtualHost>
 -----------------------------
 
+[[PassengerAppGroupName]]
+==== PassengerAppGroupName <name>
+Sets the name of the application group that the current application should belong to. Its default value is the <<PassengerRoot,application root>>, plus (if it is set), the <<PassengerAppEnv,application environment name>>.
+
+Phusion Passenger stores and caches most application spawning settings -- such as environment variables, process limits, etc -- on a per-app-group-name basis. This means that if you want to start two versions of your application, with each version having different environment variables, then you must assign them under different application group names.
+
+For example, consider a situation in which you are running multiple versions of the same app, with each version intended for a different customer. You use the `CUSTOMER_NAME` environment variable to tell the app which customer that version should serve.
+
+------------------------------------
+# WRONG example! Doesn't work!
+
+<VirtualHost *:80>
+    ServerName customer1.foo.com
+    DocumentRoot /webapps/foo/public
+    SetEnv CUSTOMER_NAME customer1
+</VirtualHost>
+
+<VirtualHost *:80>
+    ServerName customer2.foo.com
+    DocumentRoot /webapps/foo/public
+    SetEnv CUSTOMER_NAME customer2
+</VirtualHost>
+------------------------------------
+
+This example doesn't work, because Phusion Passenger thinks that they are the same application. When a user visits customer1.foo.com, Phusion Passenger will start a process with `CUSTOMER_NAME=customer1`. When another user visits customer2.foo.com, Phusion Passenger will route the request to the application process that was started earlier. Because environment variables are only set during application process startup, the second user will be served the website for customer 1.
+
+To make this work, assign unique application group names:
+
+------------------------------------
+<VirtualHost *:80>
+    ServerName customer1.foo.com
+    DocumentRoot /webapps/foo/public
+    SetEnv CUSTOMER_NAME customer1
+    PassengerAppGroupName foo_customer1
+</VirtualHost>
+
+<VirtualHost *:80>
+    ServerName customer2.foo.com
+    DocumentRoot /webapps/foo/public
+    SetEnv CUSTOMER_NAME customer2
+    PassengerAppGroupName foo_customer2
+</VirtualHost>
+------------------------------------
+
+Note that it is not necessary to set `PassengerAppGroupName` if you want to run two versions of your application under different <<PassengerAppEnv,application environment names>>, because the application environment name is included in the default application group name. For example, consider a situation in which you want to run a production and a staging version of your application. The following configuration will work fine:
+
+------------------------------------
+<VirtualHost *:80>
+    ServerName bar.com
+    DocumentRoot /webapps/bar/public
+    # Phusion Passenger implicitly sets:
+    # PassengerAppGroupName /webapps/bar
+</VirtualHost>
+
+<VirtualHost *:80>
+    ServerName staging.bar.com
+    DocumentRoot /webapps/bar/public
+    PassengerAppEnv staging
+    # Phusion Passenger implicitly sets:
+    # PassengerAppGroupName '/webapps/bar (staging)'
+</VirtualHost>
+------------------------------------
+
+This option may occur in the following places:
+
+ * In the global server configuration.
+ * In a virtual host configuration block.
+ * In a `<Directory>` or `<Location>` block.
+ * In '.htaccess', if `AllowOverride Options` is on.
+
+In each place, it may be specified at most once.
+
 [[PassengerAppType]]
 ==== PassengerAppType <name>
 :version: 4.0.25
@@ -800,8 +727,7 @@ By default, Phusion Passenger autodetects the type of the application, e.g. whet
 
 Allowed values are:
 
- * `rack` - Ruby on Rails >= 3.0 and Ruby Rack
- * `classic-rails` - Ruby on Rails 1.x and 2.0
+ * `rack` - Ruby and Rails
  * `wsgi` - Python
  * `node` - Node.js, or Meteor JS in bundled mode
  * `meteor` - Meteor JS in non-bundled mode
@@ -1360,11 +1286,13 @@ In each place, it may be specified at most once. The default value is '90'.
 :version: 4.0.0
 include::users_guide_snippets/enterprise_only.txt[]
 
-Specifies the I/O concurrency model that should be used for application processes. Phusion Passenger supports two concurrency models:
+Specifies the I/O concurrency model that should be used for Ruby application processes. Phusion Passenger supports two concurrency models:
 
  * 'process' - 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 for 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.
  * 'thread' - multi-threaded, multi-processed I/O concurrency. Each application process has multiple threads (customizable via <<PassengerThreadCount,PassengerThreadCount>>). This model provides much better I/O concurrency and uses less memory because threads share memory with each other within the same process. However, using this model may cause compatibility problems if the application is not designed to be thread-safe.
 
+This option has no effect on non-Ruby applications.
+
 This option may occur in the following places:
 
  * In the global server configuration.
@@ -1379,7 +1307,9 @@ In each place, it may be specified at most once. The default value is 'process'.
 :version: 4.0.0
 include::users_guide_snippets/enterprise_only.txt[]
 
-Specifies the number of threads that Phusion Passenger should spawn per application process. This option only has effect if <<PassengerConcurrencyModel,PassengerConcurrencyModel>> is 'thread'.
+Specifies the number of threads that Phusion Passenger should spawn per Ruby application process. This option only has effect if <<PassengerConcurrencyModel,PassengerConcurrencyModel>> is 'thread'.
+
+This option has no effect on non-Ruby applications.
 
 This option may occur in the following places:
 
@@ -1517,8 +1447,7 @@ measure to avoid memory leaks.
 By default, Phusion Passenger performs several filesystem checks (or, in
 programmers jargon, 'stat() calls') each time a request is processed:
 
-- It checks whether 'config/environment.rb', 'config.ru' or 'passenger_wsgi.py'
-  is present, in order to autodetect Rails, Rack and WSGI applications.
+- It checks which the application <<PassengerStartupFile,startup files>> are present, in order to autodetect the application type.
 - It checks whether 'restart.txt' has changed or whether 'always_restart.txt'
   exists, in order to determine whether the application should be restarted.
 
@@ -1533,14 +1462,7 @@ seconds. Setting it to a value of '0' means that no throttling will take place,
 or in other words, that the above list of filesystem checks will be performed on
 every request.
 
-This option may occur in the following places:
-
- * In the global server configuration.
- * In a virtual host configuration block.
- * In a `<Directory>` or `<Location>` block.
- * In '.htaccess', if `AllowOverride Limits` is on.
-
-In each place, it may be specified at most once. The default value is '0'.
+This option may be specified once, in the global server configuration. The default value is '10'.
 
 [[PassengerPreStart]]
 ==== PassengerPreStart <url> ====
@@ -1844,7 +1766,7 @@ http://www.foo.com/chatroom/ajax_update_poll only.
 :version: 4.0.26
 include::users_guide_snippets/since_version.txt[]
 
-When turned on, HTTP request uploads (HTTP POST request bodies) will be buffered before sending the request to the application. Enabling upload buffering protects the application from slow clients, but will also prevent the ability to track upload progress.
+When turned on, HTTP client request bodies <<PassengerDataBufferDir,will be buffered>> before they are sent the request to the application. This buffering protects the application from slow clients, but also prevents the ability to track upload progress.
 
 If you want to allow your application to track upload progress, it is recommended that you disable upload buffering for specific URIs only. For example:
 
@@ -2119,15 +2041,16 @@ information will be logged.
 
 Possible values are:
 
-- '0': Show only errors and warnings.
-- '1': Show the most important debugging information. This might be useful for
-       system administrators who are trying to figure out the cause of a
-       problem.
-- '2': Show more debugging information. This is typically only useful for developers.
-- '3': Show even more debugging information.
+- '0' (crit): Show only critical errors which would cause Phusion Passenger to abort.
+- '1' (error): Also show non-critical errors -- errors that do not cause Phusion Passenger to abort.
+- '2' (warn): Also show warnings. These are not errors, and Phusion Passenger continues to operate correctly, but they might be an indication that something is wrong with the system.
+- '3' (notice): Also show important informational messages. These give you a high-level overview of what Phusion Passenger is doing.
+- '4' (info): Also show less important informational messages. These messages show more details about what Phusion Passenger is doing. They're high-level enough to be readable by users.
+- '5' (debug): Also show the most important debugging information. Reading this information requires some system or programming knowledge, but the information shown is typically high-level enough to be understood by experienced system administrators.
+- '6' (debug2): Show more debugging information. This is typically only useful for developers.
+- '7' (debug3): Show even more debugging information.
 
-This option may only occur once, in the global server configuration.
-The default is '0'.
+This option may only occur once, in the global server configuration. The default is '3'.
 
 ==== PassengerDebugLogFile <filename> ====
 By default Phusion Passenger debugging and error messages are written to the global
@@ -2164,65 +2087,66 @@ In each place, it may be specified at most once. The default value is 'off'.
 
 === Advanced options
 
-[[PassengerTempDir]]
-==== PassengerTempDir <directory>
-Specifies the directory that Phusion Passenger should use for storing temporary
-files. This includes things such as Unix socket files, buffered file uploads
-(see also <<PassengerUploadBufferDir,PassengerUploadBufferDir>>), etc.
+[[PassengerInstanceRegistryDir]]
+==== PassengerInstanceRegistryDir <directory>
+:version: 5.0.0
+include::users_guide_snippets/since_version.txt[]
+
+Specifies the directory that Phusion Passenger should use for registering its current instance.
+
+When Phusion Passenger starts up, it creates a temporary directory inside the 'instance registry directory'. This temporary directory is called the 'instance directory'. It contains all sorts of files that are important to that specific running Phusion Passenger instance, such as Unix domain socket files so that all the different Phusion Passenger processes can communicate with each other. Command line tools such as `passenger-status` use the files in this directory in order to query Phusion Passenger's status.
+
+It is therefore important that, while Phusion Passenger is working, the instance directory is never removed or tampered with. However, the default path for the instance registry directory is the system's temporary directory, and some systems may run background jobs that periodically clean this directory. If this happens, and the files inside the instance directory are removed, then it will cause Phusion Passenger to malfunction: Phusion Passenger won't be able to communicate with its own processes, and you will see all kinds of connection errors in the log files. This malfunction can only be recovered from by restarting Apache. You can prevent such cleaning background jobs from interfering by setting this option to a different directory.
 
-This option may be specified once, in the global server configuration. The
-default temp directory that Phusion Passenger uses is '/tmp'.
+This option is also useful if Apache is not allowed to write to the system's temporary directory (which is the case on some systems with strict SELinux policies) or if the partition that the temporary directory lives on doesn't have enough disk space.
 
-This option is especially useful if Apache is not allowed to write to /tmp
-(which is the case on some systems with strict SELinux policies) or if the
-partition that /tmp lives on doesn't have enough disk space.
+The instance directory is automatically removed when Apache shuts down.
 
-.Command line tools
-Some Phusion Passenger command line administration tools, such as
-`passenger-status`, must know what Phusion Passenger's temp directory is
-in order to function properly. You can pass the directory through the
-`PASSENGER_TMPDIR` environment variable, or the `TMPDIR` environment variable
-(the former will be used if both are specified).
+This option may be specified once, in the global server configuration. The default value is the value of the `$TMPDIR` environment variable. Or, if `$TMPDIR` is not set, `/tmp`.
 
-For example, if you set 'PassengerTempDir' to '/my_temp_dir', then invoke
-`passenger-status` after you've set the `PASSENGER_TMPDIR` or `TMPDIR`
-environment variable, like this:
+:option: `--instance-registry-dir`
+include::users_guide_snippets/alternative_for_flying_passenger.txt[]
+
+.Note regarding command line tools
+Some Phusion Passenger command line administration tools, such as `passenger-status`, must know what Phusion Passenger's instance registry directory is in order to function properly. You can pass the directory through the `PASSENGER_INSTANCE_REGISTRY_DIR` or the `TMPDIR` environment variable.
+
+For example, if you set 'PassengerInstanceRegistryDir' to '/my_temp_dir', then invoke `passenger-status` after you've set the `PASSENGER_INSTANCE_REGISTRY_DIR`, like this:
 
 ----------------------------------------------------------
-export PASSENGER_TMPDIR=/my_temp-dir
+export PASSENGER_INSTANCE_REGISTRY_DIR=/my_temp-dir
 sudo -E passenger-status
-# The -E option tells 'sudo' to preserve environment variables.
 ----------------------------------------------------------
 
-[[PassengerUploadBufferDir]]
-==== PassengerUploadBufferDir <directory>
-Phusion Passenger buffers large file uploads to disk in order prevent slow file
-uploads from blocking web applications. By default, a subdirectory in the
-system's temporary files directory (or a subdirectory in the directory specified
-in <<PassengerTempDir,PassengerTempDir>>, if set) is automatically created for
-storing these buffered file uploads.
-
-This configuration directive allows you to specify a different directory for storing
-buffered file uploads. If you've specified such a directory (as opposed to using
-Phusion Passenger's default) then you *must* ensure that this directory exists.
-
-This configuration directive is also useful if you're using apache2-mpm-itk.
-The buffered file upload directory that Phusion Passenger creates by default has
-very strict permissions: it can only be accessed by the Apache worker processes.
-However, Phusion Passenger assumes that all Apache worker processes are running
-as the same user. apache2-mpm-itk breaks this assumption by running multiple
-Apache worker processes as different users. So if you're using apace2-mpm-itk,
-you should set this option to a directory that is writable by all Apache worker
-processes, such as '/tmp'.
-
-You may specify 'PassengerUploadBufferDir' in the following places:
+Notes regarding the above example:
 
- * In the global server configuration.
- * In a virtual host configuration block.
- * In a `<Directory>` or `<Location>` block.
- * In '.htaccess', if `AllowOverrides Options` is enabled.
+ * The -E option tells 'sudo' to preserve environment variables.
+ * If Phusion Passenger is installed through an RVM Ruby, then you must use `rvmsudo` instead of `sudo`.
 
-In each place, it may be specified at most once.
+[[PassengerDataBufferDir]]
+==== PassengerDataBufferDir <directory>
+:version: 5.0.0
+include::users_guide_snippets/since_version.txt[]
+
+By default, Phusion Passenger buffers the following things to disk:
+
+ * Large HTTP client request bodies. This prevents slow HTTP clients from blocking web applications by sending request bodies very slowly. Read <<PassengerBufferUpload,PassengerBufferUpload>> to learn more.
+ * Large web application responses. This prevents slow HTTP clients from blocking web applications by reading responses very slowly. This feature is also known as 'real-time disk-backed response buffering'.
+
+By default, such buffers are stored in the directory given by the `$TMPDIR` environment variable, or (if `$TMPDIR` is not set) the `/tmp` directory. This configuration directive allows you to specify a different directory.
+
+Changing this option is especially useful in the following cases:
+
+ * If Apache is not allowed to write to the system's temporary directory. This is the case on some systems with strict SELinux policies.
+ * If the partition that the default directory lives on doesn't have enough disk space.
+
+If you've specified such a directory (as opposed to using Phusion Passenger's default) then you *must* ensure that this directory exists.
+
+You can disable client request body buffering by turning <<PassengerBufferUpload,PassengerBufferUpload>> off. It is not possible to turn off real-time disk-backed response buffering.
+
+This option may be specified once, in the global server configuration.
+
+:option: `--data-buffer-dir`
+include::users_guide_snippets/alternative_for_flying_passenger.txt[]
 
 === Deprecated or removed options ===
 

data/doc/Users guide Nginx.idmap.txt

@@ -76,335 +76,335 @@
 
 2.15. Moving to a different directory	=>	moving-to-a-different-directory-gif3wo
 
-3. Deploying a Ruby on Rails 1.x or 2.x (but NOT Rails >= 3) application	=>	deploying-a-ruby-on-rails-1-x-or-2-x-but-not-rails-3-application-b69gqa
+3. Deploying a Rack-based Ruby application	=>	deploying-a-rack-based-ruby-application-including-rails-3--12benx3
 
-3.1. Deploying to a virtual host’s root	=>	deploying-to-a-virtual-host-s-root-1mh24z5
+3.1. Tutorial/example: writing and deploying a Hello World Rack application	=>	tutorial-example-writing-and-deploying-a-hello-world-rack-application-1wstx99
 
-3.2. Deploying to a sub URI	=>	deploying-to-a-sub-uri-1il2qj7
+3.2. Deploying to a virtual host’s root	=>	deploying-to-a-virtual-host-s-root-1mh24z5
 
-3.3. Redeploying (restarting the Ruby on Rails application)	=>	redeploying-restarting-the-ruby-on-rails-application--1eso761
+3.3. Deploying to a sub URI	=>	deploying-to-a-sub-uri-1il2qj7
 
-3.4. Migrations	=>	migrations-9yyb8w
+3.4. Redeploying (restarting the Rack application)	=>	redeploying-restarting-the-rack-application--xnbfam
 
-3.5. Capistrano integration	=>	capistrano-integration-1ktunm6
+3.5. Rackup specifications for various web frameworks	=>	rackup-specifications-for-various-web-frameworks-1a2cs41
 
-4. Deploying a Rack-based Ruby application (including Rails >= 3)	=>	deploying-a-rack-based-ruby-application-including-rails-3--12benx3
+3.5.1. Camping	=>	camping-16vz2yb
 
-4.1. Tutorial/example: writing and deploying a Hello World Rack application	=>	tutorial-example-writing-and-deploying-a-hello-world-rack-application-1wstx99
+3.5.2. Halcyon	=>	halcyon-1benlfl
 
-4.2. Deploying to a virtual host’s root	=>	deploying-to-a-virtual-host-s-root-f02erj
+3.5.3. Mack	=>	mack-1ezijq6
 
-4.3. Deploying to a sub URI	=>	deploying-to-a-sub-uri-37q0ou
+3.5.4. Merb	=>	merb-ddsh55
 
-4.4. Redeploying (restarting the Rack application)	=>	redeploying-restarting-the-rack-application--xnbfam
+3.5.5. Ramaze	=>	ramaze-1p2zod
 
-4.5. Rackup specifications for various web frameworks	=>	rackup-specifications-for-various-web-frameworks-1a2cs41
+3.5.6. Sinatra	=>	sinatra-a7u9ag
 
-4.5.1. Camping	=>	camping-16vz2yb
+4. Deploying a WSGI (Python) application	=>	deploying-a-wsgi-python-application-1or2efo
 
-4.5.2. Halcyon	=>	halcyon-1benlfl
+4.1. Tutorial/example: writing and deploying a Hello World WSGI application	=>	tutorial-example-writing-and-deploying-a-hello-world-wsgi-application-k5ron2
 
-4.5.3. Mack	=>	mack-1ezijq6
+4.2. Deploying to a virtual host’s root	=>	deploying-to-a-virtual-host-s-root-f02erj
 
-4.5.4. Merb	=>	merb-ddsh55
+4.3. Deploying to a sub URI	=>	deploying-to-a-sub-uri-37q0ou
 
-4.5.5. Ramaze	=>	ramaze-1p2zod
+4.4. Redeploying (restarting the WSGI application)	=>	redeploying-restarting-the-wsgi-application--10zdh2k
 
-4.5.6. Sinatra	=>	sinatra-a7u9ag
+4.5. Sample passenger_wsgi.py for Django	=>	sample-passenger-wsgi-py-for-django-1cvndls
 
-5. Deploying a WSGI (Python) application	=>	deploying-a-wsgi-python-application-1or2efo
+5. Deploying a Node.js application	=>	deploying-a-node-js-application-15wbczd
 
-5.1. Tutorial/example: writing and deploying a Hello World WSGI application	=>	tutorial-example-writing-and-deploying-a-hello-world-wsgi-application-k5ron2
+6. Deploying a Meteor application	=>	deploying-a-meteor-application-1b51wl9
 
-5.2. Deploying to a virtual host’s root	=>	deploying-to-a-virtual-host-s-root-1chcpbj
+7. Configuring Phusion Passenger	=>	configuring-phusion-passenger-1g1svey
 
-5.3. Deploying to a sub URI	=>	deploying-to-a-sub-uri-5v6zmg
+7.1. passenger_root <directory>	=>	passenger-root-directory--bqvhhz
 
-5.4. Redeploying (restarting the WSGI application)	=>	redeploying-restarting-the-wsgi-application--10zdh2k
+7.2. Deployment options	=>	deployment-options-1a1vxsp
 
-5.5. Sample passenger_wsgi.py for Django	=>	sample-passenger-wsgi-py-for-django-1cvndls
+7.2.1. passenger_enabled <on|off>	=>	passenger-enabled-on-off--1rpb2t7
 
-6. Deploying a Node.js application	=>	deploying-a-node-js-application-15wbczd
+7.2.2. passenger_base_uri <uri>	=>	passenger-base-uri-uri--1xtuo50
 
-7. Deploying a Meteor application	=>	deploying-a-meteor-application-1b51wl9
+7.2.3. passenger_document_root <path>	=>	passenger-document-root-path--1pge8kd
 
-8. Configuring Phusion Passenger	=>	configuring-phusion-passenger-1g1svey
+7.3. Application loading options	=>	application-loading-options-f3skts
 
-8.1. passenger_root <directory>	=>	passenger-root-directory--bqvhhz
+7.3.1. passenger_ruby <filename>	=>	passenger-ruby-filename--1gnok5k
 
-8.2. Deployment options	=>	deployment-options-1a1vxsp
+7.3.2. passenger_python <filename>	=>	passenger-python-filename--14p554
 
-8.2.1. passenger_enabled <on|off>	=>	passenger-enabled-on-off--1rpb2t7
+7.3.3. passenger_nodejs <filename>	=>	passenger-nodejs-filename--16hzjsv
 
-8.2.2. passenger_base_uri <uri>	=>	passenger-base-uri-uri--1xtuo50
+7.3.4. passenger_app_env <string>	=>	passenger-app-env-string--qjeimp
 
-8.2.3. passenger_document_root <path>	=>	passenger-document-root-path--1pge8kd
+7.3.5. rails_env <string>	=>	rails-env-string--jlh7v9
 
-8.3. Application loading options	=>	application-loading-options-f3skts
+7.3.6. rack_env <string>	=>	rack-env-string--tqmrt0
 
-8.3.1. passenger_ruby <filename>	=>	passenger-ruby-filename--1gnok5k
+7.3.7. passenger_app_root <path/to/root>	=>	passenger-app-root-path-to-root--1dbudc6
 
-8.3.2. passenger_python <filename>	=>	passenger-python-filename--14p554
+7.3.8. passenger_app_group_name <name>	=>	passenger-app-group-name-name--11jrx8u
 
-8.3.3. passenger_nodejs <filename>	=>	passenger-nodejs-filename--16hzjsv
+7.3.9. passenger_app_type <name>	=>	passenger-app-type-name--g9zccv
 
-8.3.4. passenger_app_env <string>	=>	passenger-app-env-string--qjeimp
+7.3.10. passenger_startup_file <filename>	=>	passenger-startup-file-filename--y4gy1m
 
-8.3.5. rails_env <string>	=>	rails-env-string--jlh7v9
+7.3.11. passenger_spawn_method <string>	=>	passenger-spawn-method-string--1sc6njl
 
-8.3.6. rack_env <string>	=>	rack-env-string--tqmrt0
+7.3.12. passenger_env_var <name> <value>	=>	passenger-env-var-name-value--y8e7wh
 
-8.3.7. passenger_app_root <path/to/root>	=>	passenger-app-root-path-to-root--1dbudc6
+7.3.13. passenger_load_shell_envvars <on|off>	=>	passenger-load-shell-envvars-on-off--fw5u4l
 
-8.3.8. passenger_app_type <name>	=>	passenger-app-type-name--g9zccv
+7.3.14. passenger_rolling_restarts <on|off>	=>	passenger-rolling-restarts
 
-8.3.9. passenger_startup_file <filename>	=>	passenger-startup-file-filename--y4gy1m
+7.3.15. passenger_resist_deployment_errors <on|off>	=>	passenger-resist-deployment-errors-on-off--k9yf1
 
-8.3.10. passenger_spawn_method <string>	=>	passenger-spawn-method-string--1sc6njl
+7.4. Security options	=>	security-options-1bv93g4
 
-8.3.11. passenger_load_shell_envvars <on|off>	=>	passenger-load-shell-envvars-on-off--fw5u4l
+7.4.1. passenger_user_switching <on|off>	=>	passenger-user-switching-on-off--1p37u3l
 
-8.3.12. passenger_rolling_restarts <on|off>	=>	passenger-rolling-restarts
+7.4.2. passenger_user <username>	=>	passenger-user-username--b06ur7
 
-8.3.13. passenger_resist_deployment_errors <on|off>	=>	passenger-resist-deployment-errors-on-off--k9yf1
+7.4.3. passenger_group <group name>	=>	passenger-user-group-name--1fco4j7
 
-8.4. Security options	=>	security-options-1bv93g4
+7.4.4. passenger_default_user <username>	=>	passenger-default-user-username--1h6cdmf
 
-8.4.1. passenger_user_switching <on|off>	=>	passenger-user-switching-on-off--1p37u3l
+7.4.5. Passenger_default_group <group name>	=>	passenger-default-group-group-name--1qxn2qa
 
-8.4.2. passenger_user <username>	=>	passenger-user-username--b06ur7
+7.4.6. passenger_show_version_in_header <on|off>	=>	passenger-show-version-in-header-on-off--2h49av
 
-8.4.3. passenger_group <group name>	=>	passenger-user-group-name--1fco4j7
+7.4.7. passenger_friendly_error_pages <on|off>	=>	passenger-friendly-error-pages-on-off--1ti1a0e
 
-8.4.4. passenger_default_user <username>	=>	passenger-default-user-username--1h6cdmf
+7.5. Resource control and optimization options	=>	resource-control-and-optimization-options-xd7evs
 
-8.4.5. Passenger_default_group <group name>	=>	passenger-default-group-group-name--1qxn2qa
+7.5.1. passenger_max_pool_size <integer>	=>	passenger-max-pool-size-integer--3jzefs
 
-8.4.6. passenger_show_version_in_header <on|off>	=>	passenger-show-version-in-header-on-off--2h49av
+7.5.2. passenger_min_instances <integer>	=>	passenger-min-instances-integer--uclykt
 
-8.4.7. passenger_friendly_error_pages <on|off>	=>	passenger-friendly-error-pages-on-off--1ti1a0e
+7.5.3. passenger_max_instances <integer>	=>	passenger-max-instances
 
-8.5. Resource control and optimization options	=>	resource-control-and-optimization-options-xd7evs
+7.5.4. passenger_max_instances_per_app <integer>	=>	passenger-max-instances-per-app-integer--1xhbbne
 
-8.5.1. passenger_max_pool_size <integer>	=>	passenger-max-pool-size-integer--3jzefs
+7.5.5. passenger_pool_idle_time <integer>	=>	passenger-pool-idle-time-integer--xcw65o
 
-8.5.2. passenger_min_instances <integer>	=>	passenger-min-instances-integer--uclykt
+7.5.6. passenger_max_preloader_idle_time <integer>	=>	rails-app-spawner-idle-time-integer--1xjqe4b
 
-8.5.3. passenger_max_instances <integer>	=>	passenger-max-instances
+7.5.7. passenger_start_timeout <seconds>	=>	passenger-start-timeout-seconds--8xn504
 
-8.5.4. passenger_max_instances_per_app <integer>	=>	passenger-max-instances-per-app-integer--1xhbbne
+7.5.8. passenger_concurrency_model <process|thread>	=>	passenger-concurrency-model-process-thread--brcvkk
 
-8.5.5. passenger_pool_idle_time <integer>	=>	passenger-pool-idle-time-integer--xcw65o
+7.5.9. passenger_thread_count <number>	=>	passenger-thread-count-number--1kd6ffy
 
-8.5.6. passenger_max_preloader_idle_time <integer>	=>	rails-app-spawner-idle-time-integer--1xjqe4b
+7.5.10. passenger_max_requests <integer>	=>	passenger-max-requests-integer--sgzint
 
-8.5.7. passenger_start_timeout <seconds>	=>	passenger-start-timeout-seconds--8xn504
+7.5.11. passenger_max_request_time <seconds>	=>	passenger-max-request-time-seconds--1htog2g
 
-8.5.8. passenger_concurrency_model <process|thread>	=>	passenger-concurrency-model-process-thread--brcvkk
+7.5.12. passenger_memory_limit <integer>	=>	passenger-memory-limit-integer--1ry7dwx
 
-8.5.9. passenger_thread_count <number>	=>	passenger-thread-count-number--1kd6ffy
+7.5.13. passenger_stat_throttle_rate <integer>	=>	passenger-stat-throttle-rate-integer--xzjbry
 
-8.5.10. passenger_max_requests <integer>	=>	passenger-max-requests-integer--sgzint
+7.5.14. passenger_pre_start <url>	=>	passenger-pre-start-url--npldeb
 
-8.5.11. passenger_max_request_time <seconds>	=>	passenger-max-request-time-seconds--1htog2g
+7.6. Connection handling options	=>	connection-handling-options-8jgq90
 
-8.5.12. passenger_memory_limit <integer>	=>	passenger-memory-limit-integer--1ry7dwx
+7.6.1. passenger_set_header <HTTP header name> <value>	=>	passenger-set-cgi-param-cgi-environment-name-value--rx9gc0
 
-8.5.13. passenger_pre_start <url>	=>	passenger-pre-start-url--npldeb
+7.6.2. passenger_max_request_queue_size <number>	=>	passenger-max-request-queue-size-number--i0te1b
 
-8.6. Connection handling options	=>	connection-handling-options-8jgq90
+7.6.3. passenger_request_queue_overflow_status_code <code>	=>	passenger-request-queue-overflow-status-code-code--1wcwuxl
 
-8.6.1. passenger_set_cgi_param <CGI environment name> <value>	=>	passenger-set-cgi-param-cgi-environment-name-value--rx9gc0
+7.6.4. passenger_sticky_sessions <on|off>	=>	passenger-sticky-sessions-on-off--lwvbxs
 
-8.6.2. passenger_max_request_queue_size <number>	=>	passenger-max-request-queue-size-number--i0te1b
+7.6.5. passenger_sticky_sessions_cookie_name	=>	passenger-sticky-sessions-cookie-name-8hrox9
 
-8.6.3. passenger_request_queue_overflow_status_code <code>	=>	passenger-request-queue-overflow-status-code-code--1wcwuxl
+7.6.6. passenger_ignore_client_abort <on|off>	=>	passenger-ignore-client-abort
 
-8.6.4. passenger_sticky_sessions <on|off>	=>	passenger-sticky-sessions-on-off--lwvbxs
+7.6.7. passenger_intercept_errors <on|off>	=>	passenger-intercept-errors-1uvcb9x
 
-8.6.5. passenger_sticky_sessions_cookie_name	=>	passenger-sticky-sessions-cookie-name-8hrox9
+7.6.8. passenger_pass_header <header name>	=>	passenger-pass-header-header-name--1cg31je
 
-8.6.6. passenger_ignore_client_abort <on|off>	=>	passenger-ignore-client-abort
+7.6.9. passenger_ignore_headers <header names…>	=>	passenger-ignore-headers-header-names--12zg5oh
 
-8.6.7. passenger_intercept_errors <on|off>	=>	passenger-intercept-errors-1uvcb9x
+7.6.10. passenger_headers_hash_bucket_size <size>	=>	passenger-headers-hash-bucket-size-size--zx1rwf
 
-8.6.8. passenger_pass_header <header name>	=>	passenger-pass-header-header-name--1cg31je
+7.6.11. passenger_headers_hash_max_size <size>	=>	passenger-headers-hash-max-size-size--1vl0i9u
 
-8.6.9. passenger_ignore_headers <header names…>	=>	passenger-ignore-headers-header-names--12zg5oh
+7.6.12. passenger_buffer_response <on|off>	=>	passenger-buffer-response
 
-8.6.10. passenger_buffer_response <on|off>	=>	passenger-buffer-response
+7.6.13. passenger_buffer_size	=>	passenger-buffer-size-1jfkq87
 
-8.6.11. passenger_buffer_size	=>	passenger-buffer-size-1jfkq87
+7.6.14. passenger_buffers	=>	passenger-busy-buffers
 
-8.6.12. passenger_buffers	=>	passenger-busy-buffers
+7.6.15. passenger_busy_buffer_size	=>	passenger-busy-buffer-size-124sj61
 
-8.6.13. passenger_busy_buffer_size	=>	passenger-busy-buffer-size-124sj61
+7.7. Logging and debugging options	=>	logging-and-debugging-options-14e91ni
 
-8.7. Logging and debugging options	=>	logging-and-debugging-options-14e91ni
+7.7.1. passenger_log_level <integer>	=>	passenger-log-level-integer--17snhon
 
-8.7.1. passenger_log_level <integer>	=>	passenger-log-level-integer--17snhon
+7.7.2. passenger_debug_log_file <filename>	=>	passenger-debug-log-file-filename--21ubaj
 
-8.7.2. passenger_debug_log_file <filename>	=>	passenger-debug-log-file-filename--21ubaj
+7.7.3. passenger_debugger <on|off>	=>	passenger-debugger-on-off--1wkuq85
 
-8.7.3. passenger_debugger <on|off>	=>	passenger-debugger-on-off--1wkuq85
+7.8. Advanced options	=>	advanced-options-hnuhqz
 
-8.8. Advanced options	=>	advanced-options-hnuhqz
+7.8.1. passenger_instance_registry_dir <directory>	=>	passenger-instance-registry-dir-directory--1jl6zij
 
-8.8.1. passenger_temp_dir <directory>	=>	passenger-temp-dir-directory--1t3opri
+7.8.2. passenger_data_buffer_dir <directory>	=>	passenger-data-buffer-dir-directory--1isg9cm
 
-8.8.2. passenger_fly_with <socket filename>	=>	passenger-fly-with-socket-filename--1amd1xn
+7.8.3. passenger_fly_with <socket filename>	=>	passenger-fly-with-socket-filename--1amd1xn
 
-8.9. Deprecated options	=>	deprecated-options-1dtzo0g
+7.9. Deprecated options	=>	deprecated-options-1dtzo0g
 
-8.9.1. rails_spawn_method	=>	rails-spawn-method-17vdnpt
+7.9.1. rails_spawn_method	=>	rails-spawn-method-17vdnpt
 
-9. Troubleshooting	=>	troubleshooting-1pt0c76
+8. Troubleshooting	=>	troubleshooting-1pt0c76
 
-9.1. Generic troubleshooting tips	=>	generic-troubleshooting-tips-xhe4nu
+8.1. Generic troubleshooting tips	=>	generic-troubleshooting-tips-xhe4nu
 
-9.2. Why does the first request take a long time?	=>	why-does-the-first-request-take-a-long-time--1knj9fp
+8.2. Why does the first request take a long time?	=>	why-does-the-first-request-take-a-long-time--1knj9fp
 
-9.3. Upon accessing the web app, Nginx reports a "Permission denied" error	=>	upon-accessing-the-web-app-nginx-reports-a-permission-denied-error-1wgatlk
+8.3. Upon accessing the web app, Nginx reports a "Permission denied" error	=>	upon-accessing-the-web-app-nginx-reports-a-permission-denied-error-1wgatlk
 
-9.4. I get "command not found" when running a Phusion Passenger command through sudo	=>	i-get-command-not-found-when-running-a-phusion-passenger-command-through-sudo-10fzwno
+8.4. I get "command not found" when running a Phusion Passenger command through sudo	=>	i-get-command-not-found-when-running-a-phusion-passenger-command-through-sudo-10fzwno
 
-9.5. The application thinks its not on SSL even though it is	=>	the-application-thinks-its-not-on-ssl-even-though-it-is-1e2m21h
+8.5. The application thinks its not on SSL even though it is	=>	the-application-thinks-its-not-on-ssl-even-though-it-is-1e2m21h
 
-9.6. Ruby on Rails-specific troubleshooting	=>	ruby-on-rails-specific-troubleshooting-n8u5u1
+8.6. Ruby on Rails-specific troubleshooting	=>	ruby-on-rails-specific-troubleshooting-n8u5u1
 
-9.6.1. The "About your application’s environment" link does not work	=>	the-about-your-application-s-environment-link-does-not-work-9p7b2g
+8.6.1. The "About your application’s environment" link does not work	=>	the-about-your-application-s-environment-link-does-not-work-9p7b2g
 
-9.6.2. The Rails application reports that it’s unable to start because of a permission error	=>	the-rails-application-reports-that-it-s-unable-to-start-because-of-a-permission-error-58ww8s
+8.6.2. The Rails application reports that it’s unable to start because of a permission error	=>	the-rails-application-reports-that-it-s-unable-to-start-because-of-a-permission-error-58ww8s
 
-9.6.3. The Rails application’s log file is not being written to	=>	the-rails-application-s-log-file-is-not-being-written-to-9m2i5h
+8.6.3. The Rails application’s log file is not being written to	=>	the-rails-application-s-log-file-is-not-being-written-to-9m2i5h
 
-10. Analysis and system maintenance	=>	analysis-and-system-maintenance-1nnlnj8
+9. Analysis and system maintenance	=>	analysis-and-system-maintenance-1nnlnj8
 
-10.1. Inspecting memory usage	=>	inspecting-memory-usage-1k6y8v0
+9.1. Inspecting memory usage	=>	inspecting-memory-usage-1k6y8v0
 
-10.2. Inspecting Phusion Passenger’s internal status	=>	inspecting-phusion-passenger-s-internal-status-v36wbc
+9.2. Inspecting Phusion Passenger’s internal status	=>	inspecting-phusion-passenger-s-internal-status-v36wbc
 
-10.3. Debugging frozen applications	=>	debugging-frozen-applications-qoctl8
+9.3. Debugging frozen applications	=>	debugging-frozen-applications-qoctl8
 
-10.4. Accessing individual application processes	=>	accessing-individual-application-processes-1qe4fqk
+9.4. Accessing individual application processes	=>	accessing-individual-application-processes-1qe4fqk
 
-10.5. Attaching an IRB console to an application process	=>	attaching-an-irb-console-to-an-application-process-d36enw
+9.5. Attaching an IRB console to an application process	=>	attaching-an-irb-console-to-an-application-process-d36enw
 
-11. Tips	=>	tips-n4c22d
+10. Tips	=>	tips-n4c22d
 
-11.1. User Switching (security feature)	=>	user-switching-security--zmsy9o
+10.1. User Switching (security feature)	=>	user-switching-security--zmsy9o
 
-11.1.1. Requirements	=>	requirements-15ozqdj
+10.1.1. Requirements	=>	requirements-15ozqdj
 
-11.1.2. Effects	=>	effects-nd2m44
+10.1.2. Effects	=>	effects-nd2m44
 
-11.1.3. Caveats & troubleshooting	=>	caveats-troubleshooting-mbw582
+10.1.3. Caveats & troubleshooting	=>	caveats-troubleshooting-mbw582
 
-11.1.4. Finding out what user an application is running as	=>	finding-out-what-user-an-application-is-running-as-1ni7zk6
+10.1.4. Finding out what user an application is running as	=>	finding-out-what-user-an-application-is-running-as-1ni7zk6
 
-11.2. Copy-on-write memory support (reducing memory consumption of Ruby applications)	=>	reducing-memory-consumption-of-ruby-on-rails-applications-by-33--1o3z66q
+10.2. Copy-on-write memory support (reducing memory consumption of Ruby applications)	=>	reducing-memory-consumption-of-ruby-on-rails-applications-by-33--1o3z66q
 
-11.3. Capistrano recipe	=>	capistrano-recipe-pfn4qu
+10.3. Capistrano recipe	=>	capistrano-recipe-pfn4qu
 
-11.4. Bundler support	=>	bundler-support-19v1h43
+10.4. Bundler support	=>	bundler-support-19v1h43
 
-11.4.1. Does Phusion Passenger itself need to be added to the Gemfile?	=>	does-phusion-passenger-itself-need-to-be-added-to-the-gemfile--xn1a11
+10.4.1. Does Phusion Passenger itself need to be added to the Gemfile?	=>	does-phusion-passenger-itself-need-to-be-added-to-the-gemfile--xn1a11
 
-11.5. Installing multiple Ruby on Rails versions	=>	installing-multiple-ruby-on-rails-versions-1bp1fff
+10.5. Installing multiple Ruby on Rails versions	=>	installing-multiple-ruby-on-rails-versions-1bp1fff
 
-11.6. Making the application restart after each request	=>	making-the-application-restart-after-each-request-vimy48
+10.6. Making the application restart after each request	=>	making-the-application-restart-after-each-request-vimy48
 
-11.7. How to fix broken images/CSS/JavaScript URIs in sub-URI deployments	=>	how-to-fix-broken-images-css-javascript-uris-in-sub-uri-deployments-11mzwt6
+10.7. How to fix broken images/CSS/JavaScript URIs in sub-URI deployments	=>	how-to-fix-broken-images-css-javascript-uris-in-sub-uri-deployments-11mzwt6
 
-11.8. Out-of-Band Work and Out-of-Band Garbage Collection	=>	out-of-band-work-and-out-of-band-garbage-collection-v89lu2
+10.8. Out-of-Band Work and Out-of-Band Garbage Collection	=>	out-of-band-work-and-out-of-band-garbage-collection-v89lu2
 
-11.9. Hooks	=>	hooks-qrxle1
+10.9. Hooks	=>	hooks-qrxle1
 
-11.9.1. Example	=>	example-1orara9
+10.9.1. Example	=>	example-1orara9
 
-11.9.2. Environment	=>	environment-10uhg8m
+10.9.2. Environment	=>	environment-10uhg8m
 
-11.9.3. Blocking and concurrency	=>	blocking-and-concurrency-g5njp1
+10.9.3. Blocking and concurrency	=>	blocking-and-concurrency-g5njp1
 
-11.9.4. Error handling	=>	error-handling-m78oxs
+10.9.4. Error handling	=>	error-handling-m78oxs
 
-11.9.5. Compatibility	=>	compatibility-132b3ns
+10.9.5. Compatibility	=>	compatibility-132b3ns
 
-11.9.6. Available hooks	=>	available-hooks-11w1prq
+10.9.6. Available hooks	=>	available-hooks-11w1prq
 
-11.10. Flying Passenger	=>	flying-passenger-137qg5e
+10.10. Flying Passenger	=>	flying-passenger-137qg5e
 
-11.10.1. Requirements	=>	requirements-194ysj6
+10.10.1. Requirements	=>	requirements-194ysj6
 
-11.10.2. Basic usage	=>	basic-usage-1qtgvwx
+10.10.2. Basic usage	=>	basic-usage-1qtgvwx
 
-11.10.3. Configuring Flying Passenger	=>	configuring-flying-passenger-n558np
+10.10.3. Configuring Flying Passenger	=>	configuring-flying-passenger-n558np
 
-11.10.4. Managing the Flying Passenger daemon	=>	managing-the-flying-passenger-daemon-vjmzdh
+10.10.4. Managing the Flying Passenger daemon	=>	managing-the-flying-passenger-daemon-vjmzdh
 
-11.10.5. Using Flying Passenger with MRI 1.8 or JRuby	=>	using-flying-passenger-with-mri-1-8-or-jruby-pxho35
+10.10.5. Using Flying Passenger with MRI 1.8 or JRuby	=>	using-flying-passenger-with-mri-1-8-or-jruby-pxho35
 
-11.10.6. Caveats and limitations	=>	caveats-and-limitations-15wakf
+10.10.6. Caveats and limitations	=>	caveats-and-limitations-15wakf
 
-12. Under the hood	=>	under-the-hood-8uney
+11. Under the hood	=>	under-the-hood-8uney
 
-12.1. Page caching support	=>	page-caching-support-nafhf6
+11.1. Page caching support	=>	page-caching-support-nafhf6
 
-12.2. Phusion Passenger and its relationship with Ruby	=>	phusion-passenger-and-its-relationship-with-ruby-1hub1pa
+11.2. Phusion Passenger and its relationship with Ruby	=>	phusion-passenger-and-its-relationship-with-ruby-1hub1pa
 
-12.2.1. How Ruby is used	=>	how-ruby-is-used-j7g2a4
+11.2.1. How Ruby is used	=>	how-ruby-is-used-j7g2a4
 
-12.2.2. When the system has multiple Ruby interpreters	=>	when-the-system-has-multiple-ruby-interpreters-fwn3t
+11.2.2. When the system has multiple Ruby interpreters	=>	when-the-system-has-multiple-ruby-interpreters-fwn3t
 
-12.3. How Phusion Passenger detects whether a virtual host is a web application	=>	how-phusion-passenger-detects-whether-a-virtual-host-is-a-web-application-13qbmhn
+11.3. How Phusion Passenger detects whether a virtual host is a web application	=>	how-phusion-passenger-detects-whether-a-virtual-host-is-a-web-application-13qbmhn
 
-13. Appendix A: About this document	=>	appendix-a-about-this-document-zfvixm
+12. Appendix A: About this document	=>	appendix-a-about-this-document-zfvixm
 
-14. Appendix B: Terminology	=>	appendix-b-terminology-wzv5ro
+13. Appendix B: Terminology	=>	appendix-b-terminology-wzv5ro
 
-14.1. Application root	=>	application-root-1fd6bqv
+13.1. Application root	=>	application-root-1fd6bqv
 
-14.2. Idle process	=>	idle-process-13byfw9
+13.2. Idle process	=>	idle-process-13byfw9
 
-14.3. Inactive process	=>	inactive-process-1d2h0po
+13.3. Inactive process	=>	inactive-process-1d2h0po
 
-15. Appendix C: Spawning methods explained	=>	appendix-c-spawning-methods-explained-tcp8e6
+14. Appendix C: Spawning methods explained	=>	appendix-c-spawning-methods-explained-tcp8e6
 
-15.1. The most straightforward and traditional way: direct spawning	=>	the-most-straightforward-and-traditional-way-conservative-spawning-civ29z
+14.1. The most straightforward and traditional way: direct spawning	=>	the-most-straightforward-and-traditional-way-conservative-spawning-civ29z
 
-15.2. The smart spawning method	=>	the-smart-spawning-method-7nhgtj
+14.2. The smart spawning method	=>	the-smart-spawning-method-7nhgtj
 
-15.2.1. How it works	=>	how-it-works-f9umga
+14.2.1. How it works	=>	how-it-works-f9umga
 
-15.2.2. Summary of benefits	=>	summary-of-benefits-qovyvk
+14.2.2. Summary of benefits	=>	summary-of-benefits-qovyvk
 
-15.3. Smart spawning caveat #1: unintentional file descriptor sharing	=>	smart-spawning-gotcha-1-unintentional-file-descriptor-sharing-cebw6q
+14.3. Smart spawning caveat #1: unintentional file descriptor sharing	=>	smart-spawning-gotcha-1-unintentional-file-descriptor-sharing-cebw6q
 
-15.3.1. Example 1: Memcached connection sharing (harmful)	=>	example-1-memcached-connection-sharing-harmful--1wfs3ad
+14.3.1. Example 1: Memcached connection sharing (harmful)	=>	example-1-memcached-connection-sharing-harmful--1wfs3ad
 
-15.3.2. Example 2: Log file sharing (not harmful)	=>	example-2-log-file-sharing-not-harmful--ox4yfy
+14.3.2. Example 2: Log file sharing (not harmful)	=>	example-2-log-file-sharing-not-harmful--ox4yfy
 
-15.4. Smart spawning caveat #2: the need to revive threads	=>	smart-spawning-gotcha-2-the-need-to-revive-threads-1ey176o
+14.4. Smart spawning caveat #2: the need to revive threads	=>	smart-spawning-gotcha-2-the-need-to-revive-threads-1ey176o
 
-16. Appendix D: About environment variables	=>	appendix-d-about-environment-variables-1t2cuff
+15. Appendix D: About environment variables	=>	appendix-d-about-environment-variables-1t2cuff
 
-16.1. Working with environment variables	=>	working-with-environment-variables-1kmvq8w
+15.1. Working with environment variables	=>	working-with-environment-variables-1kmvq8w
 
-16.2. The PATH environment variable	=>	the-path-environment-variable-vlp05e
+15.2. The PATH environment variable	=>	the-path-environment-variable-vlp05e
 
-16.2.1. Adding Phusion Passenger’s administration tools to PATH	=>	adding-phusion-passenger-s-administration-tools-to-path-1flz2tu
+15.2.1. Adding Phusion Passenger’s administration tools to PATH	=>	adding-phusion-passenger-s-administration-tools-to-path-1flz2tu
 
-16.3. Making environment variables permanent	=>	making-environment-variables-permanent-1wjyhzt
+15.3. Making environment variables permanent	=>	making-environment-variables-permanent-1wjyhzt
 
-16.3.1. bash	=>	bash-19xsxec
+15.3.1. bash	=>	bash-19xsxec
 
-16.3.2. Apache	=>	apache-9hqtyj
+15.3.2. Apache	=>	apache-9hqtyj
 
-16.3.3. Nginx	=>	nginx-157dpwy
+15.3.3. Nginx	=>	nginx-157dpwy
 
-16.3.4. cron	=>	cron-1nuc9cz
+15.3.4. cron	=>	cron-1nuc9cz
 
-16.3.5. Phusion Passenger-served apps	=>	phusion-passenger-served-apps-uiewl5
+15.3.5. Phusion Passenger-served apps	=>	phusion-passenger-served-apps-uiewl5
 
-16.4. Environment variables and sudo	=>	environment-variables-and-sudo-10lphxn
+15.4. Environment variables and sudo	=>	environment-variables-and-sudo-10lphxn