passenger 4.0.20 → 4.0.21

data/doc/Users guide Apache.idmap.txt

@@ -22,19 +22,19 @@
 
 2.1. Synopsis	=>	synopsis-l0om5d
 
-2.2. Generic installation, upgrade and downgrade method: via RubyGems	=>	installing-via-the-gem-39jw1u
+2.2. Installing or upgrading on Mac OS X with Homebrew	=>	installing-or-upgrading-on-mac-os-x-with-homebrew-1pia1cx
 
-2.3. Generic installation, upgrade and downgrade method: via tarball	=>	installing-via-the-source-tarball-1cgxrqc
+2.3. Installing or upgrading on Debian or Ubuntu	=>	installing-or-upgrading-on-ubuntu-1xg22xs
 
-2.4. Installing or upgrading on Debian or Ubuntu	=>	installing-or-upgrading-on-ubuntu-1xg22xs
+2.3.1. Adding our APT repository	=>	adding-our-apt-repository-1l8plxk
 
-2.4.1. Adding our APT repository	=>	adding-our-apt-repository-1l8plxk
+2.3.2. Installing packages	=>	installing-packages-1jxn722
 
-2.4.2. Installing packages	=>	installing-packages-1jxn722
+2.4. Installing or upgrading on Red Hat, Fedora, CentOS or ScientificLinux	=>	installing-or-upgrading-on-red-hat-fedora-centos-or-scientificlinux-1y5ie8b
 
-2.5. Installing or upgrading on Red Hat, Fedora, CentOS or ScientificLinux	=>	installing-or-upgrading-on-red-hat-fedora-centos-or-scientificlinux-1y5ie8b
+2.5. Generic installation, upgrade and downgrade method: via RubyGems	=>	installing-via-the-gem-39jw1u
 
-2.6. Installing or upgrading on Mac OS X with Homebrew	=>	installing-or-upgrading-on-mac-os-x-with-homebrew-1pia1cx
+2.6. Generic installation, upgrade and downgrade method: via tarball	=>	installing-via-the-source-tarball-1cgxrqc
 
 2.7. Upgrading from open source to Enterprise	=>	upgrading-from-open-source-to-enterprise-b17h8g
 
@@ -242,47 +242,35 @@
 
 7. Troubleshooting	=>	troubleshooting-2ihihi
 
-7.1. Operating system-specific problems	=>	operating-system-specific-problems-327gbk
+7.1. Generic troubleshooting tips	=>	generic-troubleshooting-tips-130iuhe
 
-7.1.1. MacOS X: The installer cannot locate MAMP’s Apache	=>	macos-x-the-installer-cannot-locate-mamp-s-apache-or908n
+7.2. Why does the first request take a long time?	=>	why-does-the-first-request-take-a-long-time--12mg452
 
-7.2. Problems during installation	=>	problems-during-installation-q1vlsu
+7.3. OS X: The installer cannot locate MAMP’s Apache	=>	macos-x-the-installer-cannot-locate-mamp-s-apache-or908n
 
-7.2.1. Ruby development headers aren’t installed	=>	ruby-development-headers-aren-t-installed-1yqrom8
+7.4. Apache reports a "403 Forbidden" error	=>	apache-reports-a-403-forbidden-error-140tb4p
 
-7.2.2. Apache development headers aren’t installed	=>	apache-development-headers-aren-t-installed-x2473y
+7.5. Static assets such as images and stylesheets aren’t being displayed	=>	static-assets-such-as-images-and-stylesheets-aren-t-being-displayed-uaptpi
 
-7.2.3. APR development headers aren’t installed	=>	apr-development-headers-aren-t-installed-13bk976
+7.6. The Apache error log says that the spawn manager script does not exist, or that it does not have permission to execute it	=>	the-apache-error-log-says-that-the-spawn-manager-script-does-not-exist-or-that-it-does-not-have-permission-to-execute-it-1fmoozk
 
-7.2.4. Phusion Passenger is using the wrong Apache during installation	=>	phusion-passenger-is-using-the-wrong-apache-during-installation-82qnt4
+7.7. The application thinks its not on SSL even though it is	=>	the-application-thinks-its-not-on-ssl-even-though-it-is-u9fcp1
 
-7.2.5. Phusion Passenger is using the wrong Ruby during installation	=>	phusion-passenger-is-using-the-wrong-ruby-during-installation-1nh3zml
+7.8. Ruby on Rails-specific troubleshooting	=>	ruby-on-rails-specific-problems-6umss5
 
-7.3. Problems after installation	=>	problems-after-installation-fwd23q
+7.8.1. The "About your application’s environment" link does not work	=>	the-about-your-application-s-environment-link-does-not-work-7k4tlm
 
-7.3.1. My Rails application works on Mongrel, but not on Phusion Passenger	=>	my-rails-application-works-on-mongrel-but-not-on-phusion-passenger-1f28drx
+7.8.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-v53i6s
 
-7.3.2. Phusion Passenger has been compiled against the wrong Apache installation	=>	phusion-passenger-has-been-compiled-against-the-wrong-apache-installation-n74ce0
+7.8.3. The Rails application’s log file is not being written to	=>	my-rails-application-s-log-file-is-not-being-written-to-3i747l
 
-7.3.3. I get a "403 Forbidden" error	=>	i-get-a-403-forbidden-error-m0rlay
+7.9. Conflicting Apache modules	=>	conflicting-apache-modules-1uwpixk
 
-7.3.4. Static assets such as images and stylesheets aren’t being displayed	=>	static-assets-such-as-images-and-stylesheets-aren-t-being-displayed-uaptpi
+7.9.1. mod_userdir	=>	mod-userdir-x5e2te
 
-7.3.5. The Apache error log says that the spawn manager script does not exist, or that it does not have permission to execute it	=>	the-apache-error-log-says-that-the-spawn-manager-script-does-not-exist-or-that-it-does-not-have-permission-to-execute-it-1fmoozk
+7.9.2. MultiViews (mod_negotiation)	=>	multiviews-mod-negotiation--zchfg0
 
-7.3.6. 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-v53i6s
-
-7.3.7. My Rails application’s log file is not being written to	=>	my-rails-application-s-log-file-is-not-being-written-to-3i747l
-
-7.3.8. I’ve deployed my app on SSL, but the app thinks its not on SSL	=>	i-ve-deployed-my-app-on-ssl-but-the-app-thinks-its-not-on-ssl-10rvgnr
-
-7.4. Conflicting Apache modules	=>	conflicting-apache-modules-1uwpixk
-
-7.4.1. mod_userdir	=>	mod-userdir-x5e2te
-
-7.4.2. MultiViews (mod_negotiation)	=>	multiviews-mod-negotiation--zchfg0
-
-7.4.3. VirtualDocumentRoot	=>	virtualdocumentroot-14cwd7l
+7.9.3. VirtualDocumentRoot	=>	virtualdocumentroot-14cwd7l
 
 8. Analysis and system maintenance	=>	analysis-and-system-maintenance-qvkwzr
 

data/doc/Users guide Apache.txt

@@ -22,6 +22,7 @@ using the command line.
 
 include::users_guide_snippets/support_information.txt[]
 
+[[installation]]
 == Installation
 
 include::users_guide_snippets/installation.txt[]
@@ -1925,217 +1926,31 @@ This option is no longer available in version 4.0.0. There is no alternative bec
 
 
 [[troubleshooting]]
-== Troubleshooting ==
+== Troubleshooting
 
-=== Operating system-specific problems ===
+include::users_guide_snippets/troubleshooting/default.txt[]
 
-==== MacOS X: The installer cannot locate MAMP's Apache ====
+=== OS X: The installer cannot locate MAMP's Apache
 
-.Symptoms
-*******************************************************************************
-The installer finds Apache 2 development headers at `/Applications/MAMP/Library/bin/apxs`.
-However, Apache cannot be found. The installer also outputs the following error:
+**Symptoms**::
+	The installer finds Apache 2 development headers at `/Applications/MAMP/Library/bin/apxs`. However, Apache cannot be found. The installer also outputs the following error:
++
 ------------------------------------
 cannot open /Applications/MAMP/Library/build/config_vars.mk:
 No such file or directory at /Applications/MAMP/Library/bin/apxs line 218.
 ------------------------------------
-*******************************************************************************
-
-Your MAMP installation seems to be broken. In particular, 'config_vars.mk' is missing.
-Please read link:http://forum.mamp.info/viewtopic.php?t=1866[this forum topic] to learn how
-to fix this problem.
-
-See also link:http://code.google.com/p/phusion-passenger/issues/detail?id=12[this bug report].
-
-
-=== Problems during installation ===
-
-[[installing_ruby_dev]]
-==== Ruby development headers aren't installed ====
-
-.Symptoms
-*******************************************************************************
-Installing Phusion Passenger fails because of one of the following errors:
-
-- The Phusion Passenger installer tells you that the Ruby development headers
-  aren't installed.
-- The error message ``'no such file to load -- mkmf''' occurs.
-- The error message ``'ruby.h: No such file or directory''' occurs.
-*******************************************************************************
-
-Phusion Passenger makes use of a native extension, so the Ruby development headers
-must be installed. On most Linux systems, Ruby and the Ruby development headers
-are contained in separate packages, so having Ruby installed does not
-automatically imply having the development headers installed.
-
-Here's how you can install the development headers:
-
-Ubuntu/Debian::
-	Please type:
-+
------------------------------------------
-sudo apt-get install ruby1.8-dev
------------------------------------------
-
-Fedora/CentOS/RHEL::
-	Please type:
-+
------------------------------------------
-su -c 'yum install ruby-devel'
------------------------------------------
-
-FreeBSD::
-	Please install Ruby from 'ports' or with `pkg_add`. If that fails,
-	please install Ruby from source.
-
-MacOS X::
-	Please install Ruby from source.
-
-Other operating systems::
-	Please consult your operating system's native package database.
-	There should be a package containing the Ruby development headers.
-	If that fails, please install Ruby from source.
-
-NOTE: If you've installed a new Ruby version (i.e. your system now contains
-multiple Ruby installations), then you will need to tell Phusion Passenger
-which Ruby installation you want to use. Please read
-<<specifying_ruby_installation,Specifying the correct Ruby installation>>.
-
-==== Apache development headers aren't installed ====
-
-.Symptoms
-*******************************************************************************
-Installing Phusion Passenger fails because of one of the following errors:
-
-- The installer says that the Apache development headers aren't installed.
-- The error message ``'httpd.h: No such file or directory''' occurs.
-+
-(Instead of 'httpd.h', the message might also be 'http_config.h' or something
-else similar to 'http_*.h'.)
-*******************************************************************************
-
-Ubuntu::
-	Please type:
-+
------------------------------------------
-sudo apt-get install apache2-prefork-dev
------------------------------------------
-
-Debian::
-	Please type:
-+
------------------------------------------
-sudo apt-get install apache2-dev
------------------------------------------
-
-Fedora/CentOS/RHEL::
-	Please type:
-+
---------------------------------
-su -c 'yum install httpd-devel'
---------------------------------
-
-FreeBSD::
-	Please install Apache from 'ports' or with `pkg_add`. If that fails,
-	please install Apache from source.
-
-MacOS X::
-	Please install Apache from source.
-
-Other operating systems::
-	Please consult your operating system's native package database.
-	There should be a package containing the Apache development headers.
-	If that fails, please install Apache from source.
-
-
-==== APR development headers aren't installed ====
 
-.Symptoms
-*******************************************************************************
-Installing Phusion Passenger fails because one of the following errors:
+**Cause**::
+	Your MAMP installation seems to be broken. In particular, 'config_vars.mk' is missing.
 
-- The installer tells you that APR development headers aren't installed.
-- The error message ``'apr_pools.h: No such file or directory''' occurs.
-- The error message ``'apr_strings.h: No such file or directory''' occurs.
-*******************************************************************************
+**Solution**::
+	Please read link:http://forum.mamp.info/viewtopic.php?t=1866[this forum topic] to learn how to fix this problem. See also link:http://code.google.com/p/phusion-passenger/issues/detail?id=12[this bug report].
 
-Ubuntu::
-	Please type:
-+
------------------------------------------
-sudo apt-get install libapr1-dev
------------------------------------------
-
-Debian::
-	Please type:
-+
------------------------------------------
-sudo apt-get install libapr1-dev
------------------------------------------
-
-Fedora/CentOS/RHEL::
-	Please type:
-+
---------------------------------
-su -c 'yum install apr-devel'
---------------------------------
-
-Other Linux distributions::
-	Please consult your distribution's package database. There should be a
-	package which provides APR development headers.
-
-Other operating systems::
-	The APR development are bundled with Apache. If the APR headers aren't,
-	then it probably means that they have been removed after Apache's been
-	installed. Please reinstall Apache to get back the APR headers.
-
-
-==== Phusion Passenger is using the wrong Apache during installation ====
-
-Please <<specifying_correct_apache_install,Specifying the correct Apache
-installation>>, and re-run the Phusion Passenger installer.
-
-
-==== Phusion Passenger is using the wrong Ruby during installation ====
-
-Please <<specifying_ruby_installation,Specifying the correct Ruby
-installation>>, and re-run the Phusion Passenger installer.
-
-
-=== Problems after installation ===
-
-[TIP]
-.The golden tip: read your Apache error logs!
-=====================================================
-'mod_passenger' will write all errors to the Apache error log. So if
-you're experiencing post-installation problems, please look
-inside the Apache error logs. It will tell you what exactly went wrong.
-=====================================================
-
-==== My Rails application works on Mongrel, but not on Phusion Passenger ====
-
-Please try setting <<PassengerSpawnMethod,PassengerSpawnMethod>> to 'conservative'.
-
-==== Phusion Passenger has been compiled against the wrong Apache installation ====
-
-.Symptoms
-*******************************************************************************
-Apache crashes during startup (after being daemonized). The Apache error log
-says ``'seg fault or similar nasty error detected in the parent process'''.
-*******************************************************************************
-
-This problem is most likely to occur on MacOS X. Most OS X users have multiple
-Apache installations on their system.
-
-To solve this problem, please <<specifying_correct_apache_install,specify the
-correct Apache installation>>, and <<install_passenger,reinstall Phusion
-Passenger>>.
-
-==== I get a "403 Forbidden" error ====
+=== Apache reports a "403 Forbidden" error
 
 See next subsection.
 
-==== Static assets such as images and stylesheets aren't being displayed ====
+=== Static assets such as images and stylesheets aren't being displayed
 
 Static assets are accelerated, i.e. they are served directly by Apache and do not
 go through the Rails stack. There are two reasons why Apache doesn't serve static
@@ -2160,7 +1975,7 @@ See also link:http://groups.google.com/group/phusion-passenger/browse_thread/thr
    Please make sure that the Rails application's folder, as well as all of its parent folders,
    have the correct permissions and/or ownerships.
 
-==== The Apache error log says that the spawn manager script does not exist, or that it does not have permission to execute it ====
+=== The Apache error log says that the spawn manager script does not exist, or that it does not have permission to execute it
 
 If you are sure that the 'PassengerRoot' configuration option is set correctly,
 then this problem is most likely caused by the fact that you're running Apache
@@ -2195,41 +2010,7 @@ chcon -R -h -t httpd_sys_content_t /path/to/passenger/folder
 
 Once the permissions are fixed, restart Apache.
 
-==== The Rails application reports that it's unable to start because of a permission error ====
-
-Please check whether your Rails application's folder has the correct
-permissions. By default, Rails applications are started as the owner of the
-file 'config/environment.rb', except if the file is owned by root. If the
-file is owned by root, then the Rails application will be started as 'nobody'
-(or as the user specify by <<RailsDefaultUser,RailsDefaultUser>>, if that's
-specified).
-
-Please read <<user_switching,User switching (security)>> for details.
-
-==== My Rails application's log file is not being written to ====
-
-There are a couple things that you should be aware of:
-
-- By default, Phusion Passenger runs Rails applications in 'production' mode,
-  so please be sure to check 'production.log' instead of 'development.log'. See
-  <<RailsEnv,RailsEnv>> for configuration.
-- By default, Phusion Passenger runs Rails applications as the owner of 'environment.rb'.
-  So the log file can only be written to if that user has write permission to the
-  log file. Please 'chmod' or 'chown' your log file accordingly.
-+
-See <<User_switching,User switching (security)>> for details.
-
-If you're using a RedHat-derived Linux distribution (such as Fedora or CentOS)
-then it is link:http://code.google.com/p/phusion-passenger/issues/detail?id=4[possible
-that SELinux is interfering]. RedHat's SELinux policy only allows Apache to read/write
-directories that have the 'httpd_sys_content_t' security context. Please run the
-following command to give your Rails application folder that context:
-
------------------------------------------------------------
-chcon -R -h -t httpd_sys_content_t /path/to/your/rails/app
------------------------------------------------------------
-
-==== I've deployed my app on SSL, but the app thinks its not on SSL ====
+=== The application thinks its not on SSL even though it is
 
 Rails and many other frameworks infers whether it's running on SSL through the CGI
 environment variable `HTTPS`. Apache always sets this variable when on SSL,
@@ -2270,6 +2051,8 @@ Include conf/extra/httpd-ssl.conf
 --------------------------------------
 
 
+include::users_guide_snippets/troubleshooting/rails.txt[]
+
 [[conflicting_apache_modules]]
 === Conflicting Apache modules ===
 
@@ -2387,4 +2170,7 @@ include::users_guide_snippets/appendix_b_terminology.txt[]
 
 include::users_guide_snippets/appendix_c_spawning_methods.txt[]
 
+[[about_environment_variables]]
+== Appendix D: About environment variables
+
 include::users_guide_snippets/environment_variables.txt[]

data/doc/Users guide Nginx.idmap.txt

@@ -22,19 +22,19 @@
 
 2.1. Synopsis	=>	synopsis-1uu3sqp
 
-2.2. Generic installation, upgrade and downgrade method: via RubyGems	=>	generic-installation-upgrade-and-downgrade-method-via-rubygems-76uol7
+2.2. Installing or upgrading on Mac OS X with Homebrew	=>	installing-or-upgrading-on-mac-os-x-with-homebrew-13ovvy9
 
-2.3. Generic installation, upgrade and downgrade method: via tarball	=>	generic-installation-upgrade-and-downgrade-method-via-tarball-2gkx43
+2.3. Installing or upgrading on Debian or Ubuntu	=>	installing-or-upgrading-on-ubuntu-fw5fvp
 
-2.4. Installing or upgrading on Debian or Ubuntu	=>	installing-or-upgrading-on-ubuntu-fw5fvp
+2.3.1. Adding our APT repository	=>	adding-our-apt-repository-p60cki
 
-2.4.1. Adding our APT repository	=>	adding-our-apt-repository-p60cki
+2.3.2. Installing packages	=>	installing-packages-j9glez
 
-2.4.2. Installing packages	=>	installing-packages-j9glez
+2.4. Installing or upgrading on Red Hat, Fedora, CentOS or ScientificLinux	=>	installing-or-upgrading-on-red-hat-fedora-centos-or-scientificlinux-1uus5a1
 
-2.5. Installing or upgrading on Red Hat, Fedora, CentOS or ScientificLinux	=>	installing-or-upgrading-on-red-hat-fedora-centos-or-scientificlinux-1uus5a1
+2.5. Generic installation, upgrade and downgrade method: via RubyGems	=>	generic-installation-upgrade-and-downgrade-method-via-rubygems-76uol7
 
-2.6. Installing or upgrading on Mac OS X with Homebrew	=>	installing-or-upgrading-on-mac-os-x-with-homebrew-13ovvy9
+2.6. Generic installation, upgrade and downgrade method: via tarball	=>	generic-installation-upgrade-and-downgrade-method-via-tarball-2gkx43
 
 2.7. Upgrading from open source to Enterprise	=>	upgrading-from-open-source-to-enterprise-1a58c2b
 
@@ -232,121 +232,139 @@
 
 6.18.1. rails_spawn_method	=>	rails-spawn-method-17vdnpt
 
-7. Analysis and system maintenance	=>	analysis-and-system-maintenance-1nnlnj8
+7. Troubleshooting	=>	troubleshooting-1pt0c76
 
-7.1. Inspecting memory usage	=>	inspecting-memory-usage-1k6y8v0
+7.1. Generic troubleshooting tips	=>	generic-troubleshooting-tips-xhe4nu
 
-7.2. Inspecting Phusion Passenger’s internal status	=>	inspecting-phusion-passenger-s-internal-status-v36wbc
+7.2. Why does the first request take a long time?	=>	why-does-the-first-request-take-a-long-time--1knj9fp
 
-7.3. Debugging frozen applications	=>	debugging-frozen-applications-qoctl8
+7.3. Upon accessing the web app, Nginx reports a "Permission denied" error	=>	upon-accessing-the-web-app-nginx-reports-a-permission-denied-error-1wgatlk
 
-7.4. Accessing individual application processes	=>	accessing-individual-application-processes-1qe4fqk
+7.4. The application thinks its not on SSL even though it is	=>	the-application-thinks-its-not-on-ssl-even-though-it-is-1e2m21h
 
-7.5. Attaching an IRB console to an application process	=>	attaching-an-irb-console-to-an-application-process-d36enw
+7.5. Ruby on Rails-specific troubleshooting	=>	ruby-on-rails-specific-troubleshooting-n8u5u1
 
-8. Tips	=>	tips-n4c22d
+7.5.1. The "About your application’s environment" link does not work	=>	the-about-your-application-s-environment-link-does-not-work-9p7b2g
 
-8.1. User Switching (security feature)	=>	user-switching-security--zmsy9o
+7.5.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.1.1. Requirements	=>	requirements-15ozqdj
+7.5.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.1.2. Effects	=>	effects-nd2m44
+8. Analysis and system maintenance	=>	analysis-and-system-maintenance-1nnlnj8
 
-8.1.3. Caveats & troubleshooting	=>	caveats-troubleshooting-mbw582
+8.1. Inspecting memory usage	=>	inspecting-memory-usage-1k6y8v0
 
-8.1.4. Finding out what user an application is running as	=>	finding-out-what-user-an-application-is-running-as-1ni7zk6
+8.2. Inspecting Phusion Passenger’s internal status	=>	inspecting-phusion-passenger-s-internal-status-v36wbc
 
-8.2. Copy-on-write memory support (reducing memory consumption of Ruby applications)	=>	reducing-memory-consumption-of-ruby-on-rails-applications-by-33--1o3z66q
+8.3. Debugging frozen applications	=>	debugging-frozen-applications-qoctl8
 
-8.3. Capistrano recipe	=>	capistrano-recipe-pfn4qu
+8.4. Accessing individual application processes	=>	accessing-individual-application-processes-1qe4fqk
 
-8.4. Bundler support	=>	bundler-support-19v1h43
+8.5. Attaching an IRB console to an application process	=>	attaching-an-irb-console-to-an-application-process-d36enw
 
-8.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
+9. Tips	=>	tips-n4c22d
 
-8.5. Installing multiple Ruby on Rails versions	=>	installing-multiple-ruby-on-rails-versions-1bp1fff
+9.1. User Switching (security feature)	=>	user-switching-security--zmsy9o
 
-8.6. Making the application restart after each request	=>	making-the-application-restart-after-each-request-vimy48
+9.1.1. Requirements	=>	requirements-15ozqdj
 
-8.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
+9.1.2. Effects	=>	effects-nd2m44
 
-8.8. Out-of-Band Work and Out-of-Band Garbage Collection	=>	out-of-band-work-and-out-of-band-garbage-collection-v89lu2
+9.1.3. Caveats & troubleshooting	=>	caveats-troubleshooting-mbw582
 
-8.9. Flying Passenger	=>	flying-passenger-137qg5e
+9.1.4. Finding out what user an application is running as	=>	finding-out-what-user-an-application-is-running-as-1ni7zk6
 
-8.9.1. Requirements	=>	requirements-194ysj6
+9.2. Copy-on-write memory support (reducing memory consumption of Ruby applications)	=>	reducing-memory-consumption-of-ruby-on-rails-applications-by-33--1o3z66q
 
-8.9.2. Basic usage	=>	basic-usage-1qtgvwx
+9.3. Capistrano recipe	=>	capistrano-recipe-pfn4qu
 
-8.9.3. Configuring Flying Passenger	=>	configuring-flying-passenger-n558np
+9.4. Bundler support	=>	bundler-support-19v1h43
 
-8.9.4. Managing the Flying Passenger daemon	=>	managing-the-flying-passenger-daemon-vjmzdh
+9.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
 
-8.9.5. Using Flying Passenger with MRI 1.8 or JRuby	=>	using-flying-passenger-with-mri-1-8-or-jruby-pxho35
+9.5. Installing multiple Ruby on Rails versions	=>	installing-multiple-ruby-on-rails-versions-1bp1fff
 
-8.9.6. Caveats and limitations	=>	caveats-and-limitations-15wakf
+9.6. Making the application restart after each request	=>	making-the-application-restart-after-each-request-vimy48
 
-9. Under the hood	=>	under-the-hood-8uney
+9.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
 
-9.1. Page caching support	=>	page-caching-support-nafhf6
+9.8. Out-of-Band Work and Out-of-Band Garbage Collection	=>	out-of-band-work-and-out-of-band-garbage-collection-v89lu2
 
-9.2. Phusion Passenger and its relationship with Ruby	=>	phusion-passenger-and-its-relationship-with-ruby-1hub1pa
+9.9. Flying Passenger	=>	flying-passenger-137qg5e
 
-9.2.1. How Ruby is used	=>	how-ruby-is-used-j7g2a4
+9.9.1. Requirements	=>	requirements-194ysj6
 
-9.2.2. When the system has multiple Ruby interpreters	=>	when-the-system-has-multiple-ruby-interpreters-fwn3t
+9.9.2. Basic usage	=>	basic-usage-1qtgvwx
 
-9.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
+9.9.3. Configuring Flying Passenger	=>	configuring-flying-passenger-n558np
 
-10. Appendix A: About this document	=>	appendix-a-about-this-document-zfvixm
+9.9.4. Managing the Flying Passenger daemon	=>	managing-the-flying-passenger-daemon-vjmzdh
 
-11. Appendix B: Terminology	=>	appendix-b-terminology-wzv5ro
+9.9.5. Using Flying Passenger with MRI 1.8 or JRuby	=>	using-flying-passenger-with-mri-1-8-or-jruby-pxho35
 
-11.1. Application root	=>	application-root-1fd6bqv
+9.9.6. Caveats and limitations	=>	caveats-and-limitations-15wakf
 
-11.2. Idle process	=>	idle-process-13byfw9
+10. Under the hood	=>	under-the-hood-8uney
 
-11.3. Inactive process	=>	inactive-process-1d2h0po
+10.1. Page caching support	=>	page-caching-support-nafhf6
 
-12. Appendix C: Spawning methods explained	=>	appendix-c-spawning-methods-explained-tcp8e6
+10.2. Phusion Passenger and its relationship with Ruby	=>	phusion-passenger-and-its-relationship-with-ruby-1hub1pa
 
-12.1. The most straightforward and traditional way: direct spawning	=>	the-most-straightforward-and-traditional-way-conservative-spawning-civ29z
+10.2.1. How Ruby is used	=>	how-ruby-is-used-j7g2a4
 
-12.2. The smart spawning method	=>	the-smart-spawning-method-7nhgtj
+10.2.2. When the system has multiple Ruby interpreters	=>	when-the-system-has-multiple-ruby-interpreters-fwn3t
 
-12.2.1. How it works	=>	how-it-works-f9umga
+10.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
 
-12.2.2. Summary of benefits	=>	summary-of-benefits-qovyvk
+11. Appendix A: About this document	=>	appendix-a-about-this-document-zfvixm
 
-12.3. Smart spawning gotcha #1: unintentional file descriptor sharing	=>	smart-spawning-gotcha-1-unintentional-file-descriptor-sharing-cebw6q
+12. Appendix B: Terminology	=>	appendix-b-terminology-wzv5ro
 
-12.3.1. Example 1: Memcached connection sharing (harmful)	=>	example-1-memcached-connection-sharing-harmful--1wfs3ad
+12.1. Application root	=>	application-root-1fd6bqv
 
-12.3.2. Example 2: Log file sharing (not harmful)	=>	example-2-log-file-sharing-not-harmful--ox4yfy
+12.2. Idle process	=>	idle-process-13byfw9
 
-12.4. Smart spawning gotcha #2: the need to revive threads	=>	smart-spawning-gotcha-2-the-need-to-revive-threads-1ey176o
+12.3. Inactive process	=>	inactive-process-1d2h0po
 
-12.5. Smart spawning gotcha #3: code load order	=>	smart-spawning-gotcha-3-code-load-order-12ydsn8
+13. Appendix C: Spawning methods explained	=>	appendix-c-spawning-methods-explained-tcp8e6
 
-13. Appendix D: About environment variables	=>	appendix-d-about-environment-variables-1t2cuff
+13.1. The most straightforward and traditional way: direct spawning	=>	the-most-straightforward-and-traditional-way-conservative-spawning-civ29z
 
-13.1. Working with environment variables	=>	working-with-environment-variables-1kmvq8w
+13.2. The smart spawning method	=>	the-smart-spawning-method-7nhgtj
 
-13.2. The PATH environment variable	=>	the-path-environment-variable-vlp05e
+13.2.1. How it works	=>	how-it-works-f9umga
 
-13.2.1. Adding Phusion Passenger’s administration tools to PATH	=>	adding-phusion-passenger-s-administration-tools-to-path-1flz2tu
+13.2.2. Summary of benefits	=>	summary-of-benefits-qovyvk
 
-13.3. Making environment variables permanent	=>	making-environment-variables-permanent-1wjyhzt
+13.3. Smart spawning gotcha #1: unintentional file descriptor sharing	=>	smart-spawning-gotcha-1-unintentional-file-descriptor-sharing-cebw6q
 
-13.3.1. bash	=>	bash-19xsxec
+13.3.1. Example 1: Memcached connection sharing (harmful)	=>	example-1-memcached-connection-sharing-harmful--1wfs3ad
 
-13.3.2. Apache	=>	apache-9hqtyj
+13.3.2. Example 2: Log file sharing (not harmful)	=>	example-2-log-file-sharing-not-harmful--ox4yfy
 
-13.3.3. Nginx	=>	nginx-157dpwy
+13.4. Smart spawning gotcha #2: the need to revive threads	=>	smart-spawning-gotcha-2-the-need-to-revive-threads-1ey176o
 
-13.3.4. cron	=>	cron-1nuc9cz
+13.5. Smart spawning gotcha #3: code load order	=>	smart-spawning-gotcha-3-code-load-order-12ydsn8
 
-13.3.5. Phusion Passenger-served apps	=>	phusion-passenger-served-apps-uiewl5
+14. Appendix D: About environment variables	=>	appendix-d-about-environment-variables-1t2cuff
 
-13.4. Environment variables and sudo	=>	environment-variables-and-sudo-10lphxn
+14.1. Working with environment variables	=>	working-with-environment-variables-1kmvq8w
+
+14.2. The PATH environment variable	=>	the-path-environment-variable-vlp05e
+
+14.2.1. Adding Phusion Passenger’s administration tools to PATH	=>	adding-phusion-passenger-s-administration-tools-to-path-1flz2tu
+
+14.3. Making environment variables permanent	=>	making-environment-variables-permanent-1wjyhzt
+
+14.3.1. bash	=>	bash-19xsxec
+
+14.3.2. Apache	=>	apache-9hqtyj
+
+14.3.3. Nginx	=>	nginx-157dpwy
+
+14.3.4. cron	=>	cron-1nuc9cz
+
+14.3.5. Phusion Passenger-served apps	=>	phusion-passenger-served-apps-uiewl5
+
+14.4. Environment variables and sudo	=>	environment-variables-and-sudo-10lphxn