passenger 4.0.5 → 4.0.6

data/debian.template/libapache2-mod-passenger.install

@@ -0,0 +1,3 @@
+usr/lib/apache2/modules/
+../passenger.conf etc/apache2/mods-available
+../passenger.load etc/apache2/mods-available

data/debian.template/locations.ini

@@ -0,0 +1,12 @@
+[locations]
+natively_packaged=true
+bin=/usr/bin
+agents=/usr/lib/passenger/agents
+libdir=/usr/lib/passenger
+helper_scripts=/usr/share/passenger/helper-scripts
+resources=/usr/share/passenger
+includedir=/usr/share/passenger/include
+doc=/usr/share/doc/ruby-passenger
+rubylibdir=/usr/lib/ruby/vendor_ruby
+apache2_module=/usr/lib/apache2/modules/mod_passenger.so
+ruby_extension_source=/usr/share/passenger/ruby_extension_source

data/debian.template/passenger.conf

@@ -0,0 +1,4 @@
+<IfModule mod_passenger.c>
+  PassengerRoot /usr/lib/ruby/vendor_ruby/phusion_passenger/locations.ini
+  PassengerDefaultRuby /usr/bin/ruby
+</IfModule>

data/debian.template/repack.sh

@@ -0,0 +1,42 @@
+#!/bin/sh
+# Repackage upstream source to exclude non-distributable files
+# should be called as "repack.sh --upstream-source <ver> <downloaded file>
+# (for example, via uscan)
+
+set -e
+set -u
+
+VER="$2debian"
+FILE="$3"
+PKG=`dpkg-parsechangelog|grep ^Source:|sed 's/^Source: //'`
+
+REPACK_DIR="$PKG-$VER.orig" # DevRef § 6.7.8.2
+
+echo -e "\nRepackaging $FILE\n"
+
+DIR=`mktemp -d ./tmpRepackXXXXXX`
+trap "rm -rf \"$DIR\"" QUIT INT EXIT
+
+# Create an extra directory to cope with rootless tarballs
+UP_BASE="$DIR/unpack"
+mkdir "$UP_BASE"
+tar xzf "$FILE" -C "$UP_BASE"
+
+if [ `ls -1 "$UP_BASE" | wc -l` -eq 1 ]; then
+	# Tarball does contain a root directory
+	UP_BASE="$UP_BASE/`ls -1 "$UP_BASE"`"
+fi
+
+## Remove stuff
+rm -vfr $UP_BASE/test/support/valgrind.h
+rm -vfr $UP_BASE/debian
+
+mv "$UP_BASE" "$DIR/$REPACK_DIR"
+
+# Using a pipe hides tar errors!
+tar cfC "$DIR/repacked.tar" "$DIR" "$REPACK_DIR"
+gzip -9 < "$DIR/repacked.tar" > "$DIR/repacked.tar.gz"
+FILE="../${PKG}_${VER}.orig.tar.gz"
+mv "$DIR/repacked.tar.gz" "$FILE"
+
+echo "*** $FILE repackaged"

data/debian.template/ruby-passenger-dev.install

@@ -0,0 +1,3 @@
+usr/share/passenger/ngx_http_passenger_module
+usr/share/passenger/include/
+usr/lib/passenger/common/

data/debian.template/ruby-passenger-doc.install

@@ -0,0 +1,2 @@
+debian/tmp/usr/share/doc/passenger/* usr/share/doc/ruby-passenger/
+CONTRIBUTORS usr/share/doc/ruby-passenger/

data/debian.template/ruby-passenger.docs

@@ -0,0 +1,4 @@
+CONTRIBUTING.md
+README.md
+NEWS
+debian/README.Debian

data/debian.template/ruby-passenger.install

@@ -0,0 +1,11 @@
+usr/lib/passenger/agents/
+usr/share/passenger/helper-scripts/
+usr/share/passenger/templates/
+usr/share/passenger/standalone_default_root/
+usr/share/passenger/ruby_extension_source/
+usr/share/passenger/*.types
+usr/share/passenger/*.crt
+usr/lib/ruby/
+debian/locations.ini usr/lib/ruby/vendor_ruby/phusion_passenger/
+usr/sbin/
+usr/bin/

data/debian.template/ruby-passenger.manpages

@@ -0,0 +1,4 @@
+man/passenger-memory-stats.8
+man/passenger-status.8
+man/passenger-config.1
+man/passenger-stress-test.1

data/debian.template/rules.template

@@ -0,0 +1,35 @@
+#!/usr/bin/make -f
+# export DH_VERBOSE=1
+
+export USE_VENDORED_LIBEV=false
+
+#if ['1', 'true', 'on', 'yes'].include?(ENV['USE_CCACHE'])
+	export USE_CCACHE=1
+#endif
+
+%:
+	dh $@
+
+override_dh_auto_configure:
+	# Do nothing
+
+override_dh_auto_build:
+	/usr/bin/ruby1.8 /usr/bin/rake fakeroot
+	mv pkg/fakeroot pkg/fakeroot1.8
+	/usr/bin/ruby1.9.1 /usr/bin/rake fakeroot
+	mv pkg/fakeroot pkg/fakeroot1.9.1
+
+override_dh_auto_install:
+	mkdir debian/tmp/
+	# Merge Ruby 1.8 and 1.9 files into a single directory.
+	cp -a pkg/fakeroot1.8/* debian/tmp/
+	cp -a pkg/fakeroot1.9.1/* debian/tmp/
+	# Do not package Passenger Standalone.
+	rm -rf debian/tmp/usr/bin/passenger
+
+override_dh_auto_clean:
+	/usr/bin/rake clean CLEAN_DOCS=false
+	rm -rf pkg/fakeroot1.8
+	rm -rf pkg/fakeroot1.9.1
+	# Hack to prevent HTML files from being renegerated
+	touch doc/*.html

data/debian.template/source/format

@@ -0,0 +1 @@
+3.0 (quilt)

data/debian.template/watch

@@ -0,0 +1,3 @@
+version=3
+options="dversionmangle=s/debian[0-9]*//" \
+http://rubyforge.org/frs/?group_id=5873 .*passenger-([\d.-]*)\.t.* debian debian/repack.sh

data/dev/run_travis.sh

@@ -15,70 +15,70 @@ sudo sh -c 'cat >> /etc/hosts' <<EOF
 127.0.0.1 7.passenger.test 8.passenger.test 9.passenger.test
 EOF
 
+function run()
+{
+	echo "$ $@"
+	"$@"
+}
+
 if [[ "$TEST_RUBY_VERSION" != "" ]]; then
 	echo "$ rvm use $TEST_RUBY_VERSION"
-	source ~/.rvm/scripts/rvm
+	if [[ -f ~/.rvm/scripts/rvm ]]; then
+		source ~/.rvm/scripts/rvm
+	else
+		source /usr/local/rvm/scripts/rvm
+	fi
 	rvm use $TEST_RUBY_VERSION
 	if [[ "$TEST_RUBYGEMS_VERSION" = "" ]]; then
-		echo "$ gem --version"
-		gem --version
+		run gem --version
 	fi
 fi
 
 if [[ "$TEST_RUBYGEMS_VERSION" != "" ]]; then
-	echo "$ rvm install rubygems $TEST_RUBYGEMS_VERSION"
-	rvm install rubygems $TEST_RUBYGEMS_VERSION
-	echo "$ gem --version"
-	gem --version
-fi
-
-if [[ "$TEST_FULL_COMPILE" = 1 ]]; then
-	echo "$ gem install rack --no-rdoc --no-ri"
-	gem install rack --no-rdoc --no-ri
-	echo "$ ./bin/passenger-install-apache2-module --auto"
-	./bin/passenger-install-apache2-module --auto
-	echo "$ rake nginx"
-	rake nginx
-	echo "$ rake test/cxx/CxxTestMain"
-	rake test/cxx/CxxTestMain
-	echo "$ rake test/oxt/oxt_test_main"
-	rake test/oxt/oxt_test_main
+	run rvm install rubygems $TEST_RUBYGEMS_VERSION
+	run gem --version
 fi
 
 if [[ "$TEST_CXX" = 1 ]]; then
-	echo "$ rake test:install_deps RAILS_BUNDLES=no"
-	rake test:install_deps RAILS_BUNDLES=no
-	echo "$ rake test:cxx"
-	rake test:cxx
-	echo "$ rake test:oxt"
-	rake test:oxt
+	run rake test:install_deps RAILS_BUNDLES=no DOCTOOLS=no
+	run rake test:cxx
+	run rake test:oxt
 fi
 
 if [[ "$TEST_RUBY" = 1 ]]; then
-	echo "$ rake test:install_deps"
-	rake test:install_deps
-	echo "$ rake test:ruby"
-	rake test:ruby
+	run rake test:install_deps DOCTOOLS=no
+	run rake test:ruby
 fi
 
 if [[ "$TEST_NGINX" = 1 ]]; then
-	echo "$ rake test:install_deps RAILS_BUNDLES=no"
-	rake test:install_deps RAILS_BUNDLES=no
-	echo "$ gem install rack daemon_controller --no-rdoc --no-ri"
-	gem install rack daemon_controller --no-rdoc --no-ri
-	echo "$ ./bin/passenger-install-nginx-module --auto --prefix=/tmp/nginx --auto-download"
-	./bin/passenger-install-nginx-module --auto --prefix=/tmp/nginx --auto-download
-	echo "$ rake test:integration:nginx"
-	rake test:integration:nginx
+	run rake test:install_deps RAILS_BUNDLES=no DOCTOOLS=no
+	run gem install rack daemon_controller --no-rdoc --no-ri
+	run ./bin/passenger-install-nginx-module --auto --prefix=/tmp/nginx --auto-download
+	run rake test:integration:nginx
 fi
 
 if [[ "$TEST_APACHE2" = 1 ]]; then
-	echo "$ rake test:install_deps RAILS_BUNDLES=no"
-	rake test:install_deps RAILS_BUNDLES=no
-	echo "$ gem install rack --no-rdoc --no-ri"
-	gem install rack --no-rdoc --no-ri
-	echo "$ rake apache2"
-	rake apache2
-	echo "$ rake test:integration:apache2"
-	rake test:integration:apache2
+	run sudo apt-get install -y --no-install-recommends \
+		apache2-mpm-worker apache2-threaded-dev
+	run rake test:install_deps RAILS_BUNDLES=no DOCTOOLS=no
+	run gem install rack --no-rdoc --no-ri
+	run ./bin/passenger-install-apache2-module --auto
+	run rake test:integration:apache2
+fi
+
+if [[ "$TEST_DEBIAN_PACKAGING" = 1 ]]; then
+	run sudo apt-get install -y --no-install-recommends \
+		devscripts debhelper rake apache2-mpm-worker apache2-threaded-dev \
+		ruby1.8 ruby1.8-dev ruby1.9.1 ruby1.9.1-dev libev-dev gdebi-core \
+		source-highlight
+	run rake test:install_deps RAILS_BUNDLES=no
+	run rake debian:dev
+	run sudo gdebi -n pkg/ruby-passenger_*.deb
+	run sudo gdebi -n pkg/ruby-passenger-dev_*.deb
+	run sudo gdebi -n pkg/ruby-passenger-doc_*.deb
+	run sudo gdebi -n pkg/libapache2-mod-passenger_*.deb
+	run rvmsudo env LOCATIONS_INI=/usr/lib/ruby/vendor_ruby/phusion_passenger/locations.ini \
+		rspec -f s -c test/integration_tests/native_packaging_spec.rb
+	run env PASSENGER_LOCATION_CONFIGURATION_FILE=/usr/lib/ruby/vendor_ruby/phusion_passenger/locations.ini \
+		rake test:integration:apache2
 fi

data/doc/Architectural overview.html

@@ -1059,8 +1059,8 @@ pre {
 <body class="article">
 <div id="topbar" style="display: none">
 	<div class="title">
-		<img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAsAAAAKCAYAAAEV95QVAAAAAXNSR0IArs4c6QAAAAZiS0dEAP8A/wD/oL2nkwAAAAlwSFlzAAALEwAACxMBAJqcGAAAAAd0SU1FB9sGCRMSACDxkZwAAAAidEVYdENvbW1lbnQAQ3JlYXRlZCB3aXRoIEdJTVAgb24gYSBNYWOHqHdDAAAAZUlEQVQY032PSxbAIAjEIlfygL6ePF3UUvpzNjgSYWwqAMEhUQnANnsC7TQPeJpsVWzMuh2sog4vDTUbqP081zECrW4dtdaQGSIKlWluPyjK+VXxAz5XfcKufCzA130AfQHWB30HZxlPaP080xsAAAAASUVORK5CYII=" width="11" height="10" alt="">
-		<a href="javascript:void(Mizuho.smoothlyScrollToToc())">Phusion Passenger design &amp; architecture</a>
+		<!-- 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 design &amp; architecture</a>
 	</div>
 	<a href="javascript:void(0)" id="current_section"></a>
 </div>

data/doc/Packaging.html

@@ -481,28 +481,35 @@ button.btn.btn-mini,input[type="submit"].btn.btn-mini{*padding-top:1px;*padding-
 
       <h1>Introduction</h1>
 
+<p>This document describes how packagers can package Phusion Passenger binaries
+for their operating system.</p>
+
 <p>Phusion Passenger can be configured in 2 ways, the "originally packaged"
-configuration and the "natively packaged" configuration. Depending on the
-configuration, Phusion Passenger locates its files (also called <em>assets</em>)
-in a different manner.</p>
+configuration where everything is in the same directory, and the
+"natively packaged" configuration where files are scattered across the
+filesystem, e.g. in a FHS-compliant configuration. This document describes
+how you can configure Phusion Passenger to locate its own files when they're
+scattered across the filesystem.</p>
+
+<p>Phusion Passenger files are also called <em>assets</em> in this document.</p>
 
 <h2>Originally packaged</h2>
 
 <p>This is the configuration you get when you checkout Phusion Passenger from git,
-when you install Phusion Passenger from a gem or when you extract it from a tarball.
-All the original files are stored in a single directory tree, which we call the
-<em>source root</em>.</p>
+when you install Phusion Passenger from a gem or when you extract it from a
+tarball. All the original files are stored in a single directory tree, which we
+call the <em>source root</em>.</p>
 
-<p>This configuration does not come with any binaries; they have to be compiled by the
-user. Binaries may either be located in the source root, or located in a different
-location. The following rules apply when it comes to looking for binaries and
-determining where to store compiled binaries:</p>
+<p>The git repository, gems and tarballs do not come with any binaries; they have
+to be compiled by the user. Phusion Passenger looks for binaries in, and (if
+the user initiates the compilation process) stores binaries in, the following
+directories:</p>
 
 <ul>
-<li>It will normally look for binaries in a subdirectory under the source root, and
-it will store compiled binaries in a subdirectory under the source root.</li>
-<li><p>Phusion Passenger Standalone does things a little differently. It looks for
-its binaries in one of these places, whichever first exists:</p>
+<li>Normally, binaries are to be located in the <code>agents</code> and <code>libout</code>
+subdirectories under the source root.</li>
+<li><p>Phusion Passenger Standalone does things a little differently. Binaries are
+to be located in one of the following directories, whichever it finds first:</p>
 
 <ul>
 <li><code>~/.passenger/standalone/&lt;VERSION&gt;/&lt;TYPE-AND-ARCH&gt;</code> (a)</li>
@@ -510,9 +517,9 @@ its binaries in one of these places, whichever first exists:</p>
 </ul>
 
 
-<p>If neither directories exist, then Passenger Standalone compiles the binaries and
-stores them in (b) (when running as root) or in (a). It still looks for everything
-else (like the .rb files) in the source root.</p></li>
+<p>If neither directories exist, then Passenger Standalone compiles the
+binaries and stores them in (b) (when running as root) or in (a). It still
+looks for everything else (like the .rb files) in the source root.</p></li>
 </ul>
 
 
@@ -718,7 +725,9 @@ print an example configuration snippet.</p>
 <li><p><code>ruby_extension_source</code></p>
 
 <p>The directory that contains the source code for the Phusion Passenger Ruby
-extension.</p>
+extension. Phusion Passenger uses these sources to build a Ruby extension,
+when it detects that the user is using a new Ruby interpeter for which
+no Ruby extension has been compiled.</p>
 
 <p>Value when originally packaged: <code>&lt;SOURCE_ROOT&gt;/ext/ruby</code>.</p></li>
 </ul>

data/doc/Packaging.txt.md

@@ -1,33 +1,40 @@
 # Introduction
 
+This document describes how packagers can package Phusion Passenger binaries
+for their operating system.
+
 Phusion Passenger can be configured in 2 ways, the "originally packaged"
-configuration and the "natively packaged" configuration. Depending on the
-configuration, Phusion Passenger locates its files (also called _assets_)
-in a different manner.
+configuration where everything is in the same directory, and the
+"natively packaged" configuration where files are scattered across the
+filesystem, e.g. in a FHS-compliant configuration. This document describes
+how you can configure Phusion Passenger to locate its own files when they're
+scattered across the filesystem.
+
+Phusion Passenger files are also called _assets_ in this document.
 
 ## Originally packaged
 
 This is the configuration you get when you checkout Phusion Passenger from git,
-when you install Phusion Passenger from a gem or when you extract it from a tarball.
-All the original files are stored in a single directory tree, which we call the
-_source root_.
+when you install Phusion Passenger from a gem or when you extract it from a
+tarball. All the original files are stored in a single directory tree, which we
+call the _source root_.
 
-This configuration does not come with any binaries; they have to be compiled by the
-user. Binaries may either be located in the source root, or located in a different
-location. The following rules apply when it comes to looking for binaries and
-determining where to store compiled binaries:
+The git repository, gems and tarballs do not come with any binaries; they have
+to be compiled by the user. Phusion Passenger looks for binaries in, and (if
+the user initiates the compilation process) stores binaries in, the following
+directories:
 
- * It will normally look for binaries in a subdirectory under the source root, and
-   it will store compiled binaries in a subdirectory under the source root.
- * Phusion Passenger Standalone does things a little differently. It looks for
-   its binaries in one of these places, whichever first exists:
+ * Normally, binaries are to be located in the `agents` and `libout`
+   subdirectories under the source root.
+ * Phusion Passenger Standalone does things a little differently. Binaries are
+   to be located in one of the following directories, whichever it finds first:
 
     - `~/.passenger/standalone/<VERSION>/<TYPE-AND-ARCH>` (a)
     - `/var/lib/passenger-standalone/<VERSION-AND-ARCH>` (b)
 
-   If neither directories exist, then Passenger Standalone compiles the binaries and
-   stores them in (b) (when running as root) or in (a). It still looks for everything
-   else (like the .rb files) in the source root.
+   If neither directories exist, then Passenger Standalone compiles the
+   binaries and stores them in (b) (when running as root) or in (a). It still
+   looks for everything else (like the .rb files) in the source root.
 
 ## Natively packaged
 
@@ -229,7 +236,9 @@ a list of all possible assets and asset directories.
  * `ruby_extension_source`
 
    The directory that contains the source code for the Phusion Passenger Ruby
-   extension.
+   extension. Phusion Passenger uses these sources to build a Ruby extension,
+   when it detects that the user is using a new Ruby interpeter for which
+   no Ruby extension has been compiled.
 
    Value when originally packaged: `<SOURCE_ROOT>/ext/ruby`.
 

data/doc/Security of user switching support.html

@@ -1059,8 +1059,8 @@ pre {
 <body class="article">
 <div id="topbar" style="display: none">
 	<div class="title">
-		<img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAsAAAAKCAYAAAEV95QVAAAAAXNSR0IArs4c6QAAAAZiS0dEAP8A/wD/oL2nkwAAAAlwSFlzAAALEwAACxMBAJqcGAAAAAd0SU1FB9sGCRMSACDxkZwAAAAidEVYdENvbW1lbnQAQ3JlYXRlZCB3aXRoIEdJTVAgb24gYSBNYWOHqHdDAAAAZUlEQVQY032PSxbAIAjEIlfygL6ePF3UUvpzNjgSYWwqAMEhUQnANnsC7TQPeJpsVWzMuh2sog4vDTUbqP081zECrW4dtdaQGSIKlWluPyjK+VXxAz5XfcKufCzA130AfQHWB30HZxlPaP080xsAAAAASUVORK5CYII=" width="11" height="10" alt="">
-		<a href="javascript:void(Mizuho.smoothlyScrollToToc())">Security of user switching support in Passenger</a>
+		<!-- 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())">Security of user switching support in Passenger</a>
 	</div>
 	<a href="javascript:void(0)" id="current_section"></a>
 </div>

data/doc/Users guide Apache.html

@@ -1059,8 +1059,8 @@ pre {
 <body class="article">
 <div id="topbar" style="display: none">
 	<div class="title">
-		<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, Apache version</a>
+		<!-- 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, Apache version</a>
 	</div>
 	<a href="javascript:void(0)" id="current_section"></a>
 </div>
@@ -1111,7 +1111,7 @@ using the command line.</p></div>
 <div class="foo toclevel3"><a href="#_synopsis">2.1. Synopsis</a></div>
 <div class="foo toclevel3"><a href="#rubygems_generic_install">2.2. Generic installation, upgrade and downgrade method: via RubyGems</a></div>
 <div class="foo toclevel3"><a href="#tarball_generic_install">2.3. Generic installation, upgrade and downgrade method: via tarball</a></div>
-<div class="foo toclevel3"><a href="#_installing_or_upgrading_on_debian_6_or_ubuntu">2.4. Installing or upgrading on Debian 6 or Ubuntu</a></div>
+<div class="foo toclevel3"><a href="#install_on_debian_ubuntu">2.4. Installing or upgrading on Debian 6 or Ubuntu</a></div>
 <div class="foo toclevel3"><a href="#_installing_or_upgrading_on_red_hat_fedora_centos_or_scientificlinux">2.5. Installing or upgrading on Red Hat, Fedora, CentOS or ScientificLinux</a></div>
 <div class="foo toclevel3"><a href="#_upgrading_from_open_source_to_enterprise">2.6. Upgrading from open source to Enterprise</a></div>
 <div class="foo toclevel3"><a href="#_cryptographic_verification_of_installation_files">2.7. Cryptographic verification of installation files</a></div>
@@ -1126,7 +1126,7 @@ using the command line.</p></div>
 <div class="foo toclevel3"><a href="#_customizing_the_compilation_process">2.9. Customizing the compilation process</a></div>
 <div class="foo toclevel4"><a href="#_setting_the_compiler">2.9.1. Setting the compiler</a></div>
 <div class="foo toclevel4"><a href="#_adding_additional_compiler_or_linker_flags">2.9.2. Adding additional compiler or linker flags</a></div>
-<div class="foo toclevel4"><a href="#_forcing_location_of_certain_command_line_tools">2.9.3. Forcing location of certain command line tools</a></div>
+<div class="foo toclevel4"><a href="#_forcing_location_of_command_line_tools_and_dependencies">2.9.3. Forcing location of command line tools and dependencies</a></div>
 <div class="foo toclevel3"><a href="#working_with_apache_conf">2.10. Working with the Apache configuration file</a></div>
 <div class="foo toclevel3"><a href="#_disabling_without_uninstalling">2.11. Disabling without uninstalling</a></div>
 <div class="foo toclevel3"><a href="#uninstalling">2.12. Uninstalling</a></div>
@@ -1155,7 +1155,7 @@ using the command line.</p></div>
 <div class="foo toclevel3"><a href="#_redeploying_restarting_the_wsgi_application">5.3. Redeploying (restarting the WSGI application)</a></div>
 <div class="foo toclevel2"><a href="#_configuring_phusion_passenger">6. Configuring Phusion Passenger</a></div>
 <div class="foo toclevel3"><a href="#_passengerroot_lt_directory_gt">6.1. PassengerRoot &lt;directory&gt;</a></div>
-<div class="foo toclevel3"><a href="#PassengerDefaultRuby">6.2. PassengerDefaultRuby and PassengerRuby</a></div>
+<div class="foo toclevel3"><a href="#PassengerDefaultRuby">6.2. PassengerDefaultRuby &lt;filename&gt;</a></div>
 <div class="foo toclevel3"><a href="#PassengerRuby">6.3. PassengerRuby &lt;filename&gt;</a></div>
 <div class="foo toclevel3"><a href="#_passengerpython_lt_filename_gt">6.4. PassengerPython &lt;filename&gt;</a></div>
 <div class="foo toclevel3"><a href="#PassengerAppRoot">6.5. PassengerAppRoot &lt;path/to/root&gt;</a></div>
@@ -1169,11 +1169,11 @@ using the command line.</p></div>
 <div class="foo toclevel3"><a href="#_passengerresistdeploymenterrors_lt_on_off_gt">6.13. PassengerResistDeploymentErrors &lt;on|off&gt;</a></div>
 <div class="foo toclevel3"><a href="#_security_options">6.14. Security options</a></div>
 <div class="foo toclevel4"><a href="#PassengerUserSwitching">6.14.1. PassengerUserSwitching &lt;on|off&gt;</a></div>
-<div class="foo toclevel4"><a href="#_passengeruser_lt_username_gt">6.14.2. PassengerUser &lt;username&gt;</a></div>
-<div class="foo toclevel4"><a href="#_passengergroup_lt_group_name_gt">6.14.3. PassengerGroup &lt;group name&gt;</a></div>
+<div class="foo toclevel4"><a href="#PassengerUser">6.14.2. PassengerUser &lt;username&gt;</a></div>
+<div class="foo toclevel4"><a href="#PassengerGroup">6.14.3. PassengerGroup &lt;group name&gt;</a></div>
 <div class="foo toclevel4"><a href="#PassengerDefaultUser">6.14.4. PassengerDefaultUser &lt;username&gt;</a></div>
 <div class="foo toclevel4"><a href="#PassengerDefaultGroup">6.14.5. PassengerDefaultGroup &lt;group name&gt;</a></div>
-<div class="foo toclevel4"><a href="#_passengerfriendlyerrorpages_lt_on_off_gt">6.14.6. PassengerFriendlyErrorPages &lt;on|off&gt;</a></div>
+<div class="foo toclevel4"><a href="#PassengerFriendlyErrorPages">6.14.6. PassengerFriendlyErrorPages &lt;on|off&gt;</a></div>
 <div class="foo toclevel3"><a href="#_resource_control_and_optimization_options">6.15. Resource control and optimization options</a></div>
 <div class="foo toclevel4"><a href="#_passengermaxpoolsize_lt_integer_gt">6.15.1. PassengerMaxPoolSize &lt;integer&gt;</a></div>
 <div class="foo toclevel4"><a href="#PassengerMinInstances">6.15.2. PassengerMinInstances &lt;integer&gt;</a></div>
@@ -1193,7 +1193,7 @@ using the command line.</p></div>
 <div class="foo toclevel4"><a href="#PassengerResolveSymlinksInDocumentRoot">6.16.1. PassengerResolveSymlinksInDocumentRoot &lt;on|off&gt;</a></div>
 <div class="foo toclevel4"><a href="#_passengerallowencodedslashes_lt_on_off_gt">6.16.2. PassengerAllowEncodedSlashes &lt;on|off&gt;</a></div>
 <div class="foo toclevel3"><a href="#_logging_and_debugging_options">6.17. Logging and debugging options</a></div>
-<div class="foo toclevel4"><a href="#_passengerloglevel_lt_integer_gt">6.17.1. PassengerLogLevel &lt;integer&gt;</a></div>
+<div class="foo toclevel4"><a href="#PassengerLogLevel">6.17.1. PassengerLogLevel &lt;integer&gt;</a></div>
 <div class="foo toclevel4"><a href="#_passengerdebuglogfile_lt_filename_gt">6.17.2. PassengerDebugLogFile &lt;filename&gt;</a></div>
 <div class="foo toclevel4"><a href="#_passengerdebugger_lt_on_off_gt">6.17.3. PassengerDebugger &lt;on|off&gt;</a></div>
 <div class="foo toclevel3"><a href="#_classic_ruby_on_rails_8656_2_x_specific_options">6.18. Classic Ruby on Rails (⇐ 2.x)-specific options</a></div>
@@ -1240,16 +1240,27 @@ using the command line.</p></div>
 <div class="foo toclevel3"><a href="#_accessing_individual_application_processes">8.4. Accessing individual application processes</a></div>
 <div class="foo toclevel3"><a href="#_attaching_an_irb_console_to_an_application_process">8.5. Attaching an IRB console to an application process</a></div>
 <div class="foo toclevel2"><a href="#_tips">9. Tips</a></div>
-<div class="foo toclevel3"><a href="#user_switching">9.1. User switching (security)</a></div>
-<div class="foo toclevel3"><a href="#reducing_memory_usage">9.2. Reducing memory consumption of Ruby on Rails applications by 33%</a></div>
+<div class="foo toclevel3"><a href="#user_switching">9.1. User Switching (security feature)</a></div>
+<div class="foo toclevel4"><a href="#_requirements">9.1.1. Requirements</a></div>
+<div class="foo toclevel4"><a href="#_effects">9.1.2. Effects</a></div>
+<div class="foo toclevel4"><a href="#_caveats_amp_troubleshooting">9.1.3. Caveats &amp; troubleshooting</a></div>
+<div class="foo toclevel4"><a href="#finding_out_app_user">9.1.4. Finding out what user an application is running as</a></div>
+<div class="foo toclevel3"><a href="#reducing_memory_usage">9.2. Copy-on-write memory support (reducing memory consumption of Ruby applications)</a></div>
 <div class="foo toclevel3"><a href="#capistrano">9.3. Capistrano recipe</a></div>
 <div class="foo toclevel3"><a href="#bundler_support">9.4. Bundler support</a></div>
+<div class="foo toclevel4"><a href="#add_passenger_to_gemfile">9.4.1. Does Phusion Passenger itself need to be added to the Gemfile?</a></div>
 <div class="foo toclevel3"><a href="#_installing_multiple_ruby_on_rails_versions">9.5. Installing multiple Ruby on Rails versions</a></div>
 <div class="foo toclevel3"><a href="#_making_the_application_restart_after_each_request">9.6. Making the application restart after each request</a></div>
 <div class="foo toclevel3"><a href="#sub_uri_deployment_uri_fix">9.7. How to fix broken images/CSS/JavaScript URIs in sub-URI deployments</a></div>
 <div class="foo toclevel3"><a href="#_out_of_band_garbage_work_and_out_of_band_garbage_collection">9.8. Out-of-Band Garbage Work and Out-of-Band Garbage Collection</a></div>
-<div class="foo toclevel3"><a href="#_x_sendfile_support">9.9. X-Sendfile support</a></div>
-<div class="foo toclevel3"><a href="#_upload_progress">9.10. Upload progress</a></div>
+<div class="foo toclevel3"><a href="#flying_passenger">9.9. Flying Passenger</a></div>
+<div class="foo toclevel4"><a href="#_requirements_2">9.9.1. Requirements</a></div>
+<div class="foo toclevel4"><a href="#_basic_usage">9.9.2. Basic usage</a></div>
+<div class="foo toclevel4"><a href="#configuring_flying_passenger">9.9.3. Configuring Flying Passenger</a></div>
+<div class="foo toclevel4"><a href="#_managing_the_flying_passenger_daemon">9.9.4. Managing the Flying Passenger daemon</a></div>
+<div class="foo toclevel4"><a href="#flying_passenger_caveats">9.9.5. Caveats and limitations</a></div>
+<div class="foo toclevel3"><a href="#_x_sendfile_support">9.10. X-Sendfile support</a></div>
+<div class="foo toclevel3"><a href="#_upload_progress">9.11. Upload progress</a></div>
 <div class="foo toclevel2"><a href="#_under_the_hood">10. Under the hood</a></div>
 <div class="foo toclevel3"><a href="#_static_assets_serving">10.1. Static assets serving</a></div>
 <div class="foo toclevel3"><a href="#_page_caching_support">10.2. Page caching support</a></div>
@@ -1269,6 +1280,16 @@ using the command line.</p></div>
 <div class="foo toclevel4"><a href="#_example_2_log_file_sharing_not_harmful">13.3.2. Example 2: Log file sharing (not harmful)</a></div>
 <div class="foo toclevel3"><a href="#_smart_spawning_gotcha_2_the_need_to_revive_threads">13.4. Smart spawning gotcha #2: the need to revive threads</a></div>
 <div class="foo toclevel3"><a href="#_smart_spawning_gotcha_3_code_load_order">13.5. Smart spawning gotcha #3: code load order</a></div>
+<div class="foo toclevel2"><a href="#about_environment_variables">14. Appendix D: About environment variables</a></div>
+<div class="foo toclevel3"><a href="#_working_with_environment_variables">14.1. Working with environment variables</a></div>
+<div class="foo toclevel3"><a href="#_the_path_environment_variable">14.2. The PATH environment variable</a></div>
+<div class="foo toclevel3"><a href="#_making_environment_variables_permanent">14.3. Making environment variables permanent</a></div>
+<div class="foo toclevel4"><a href="#_bash">14.3.1. bash</a></div>
+<div class="foo toclevel4"><a href="#_apache">14.3.2. Apache</a></div>
+<div class="foo toclevel4"><a href="#_nginx">14.3.3. Nginx</a></div>
+<div class="foo toclevel4"><a href="#_cron">14.3.4. cron</a></div>
+<div class="foo toclevel4"><a href="#env_vars_passenger_apps">14.3.5. Phusion Passenger-served apps</a></div>
+<div class="foo toclevel3"><a href="#env_vars_and_sudo">14.4. Environment variables and sudo</a></div>
 </div>
 </div>
 <div id="content">
@@ -1295,14 +1316,14 @@ if it doesn’t work on your POSIX-compliant operating system.</p></div>
 <div class="ulist"><ul>
 <li>
 <p>
-<a href="http://code.google.com/p/phusion-passenger/issues/list">Issue tracker</a> - report
-  bugs here.
+<a href="http://groups.google.com/group/phusion-passenger">Discussion forum</a> - post a
+  message here if you’re experiencing problems. Support on this forum is provided by the community on a best-effort basis, so a (timely) response is not guaranteed.
 </p>
 </li>
 <li>
 <p>
-<a href="http://groups.google.com/group/phusion-passenger">Discussion forum</a> - post a
-  message here if you’re experiencing problems. Support on this forum is provided by the community on a best-effort basis, so a (timely) response is not guaranteed.
+<a href="http://code.google.com/p/phusion-passenger/issues/list">Issue tracker</a> - report
+  bugs here.
 </p>
 </li>
 <li>
@@ -1317,7 +1338,7 @@ Email <a href="mailto:support@phusion.nl">support@phusion.nl</a> if you are a <a
 </li>
 <li>
 <p>
-Report security vulnerabilities to <a href="mailto:support@phusion.nl">support@phusion.nl</a>. We will do our best to respond to you as quickly as we can, so please do not disclose the vulnerability until then.
+Report security vulnerabilities to <a href="mailto:security@phusion.nl">security@phusion.nl</a>. We will do our best to respond to you as quickly as we can, so please do not disclose the vulnerability until then.
 </p>
 </li>
 </ul></div>
@@ -1478,7 +1499,21 @@ chmod o+x /home/phusion</pre>
 configuration file. However, it doesn’t copy any files to outside the Phusion Passenger source directory.</p>
 </div>
 <div class="paragraph"><p><span class="monospaced">passenger-install-apache2-module</span> is actually just a user-friendly frontend around the command <span class="monospaced">rake apache2</span>, which performs the actual compilation of Phusion Passenger.</p></div>
-<span class="anchor_helper" id="verify_passenger_running"></span><h4 class="float" data-anchor="verify_passenger_running">Step 6: Verifying that Phusion Passenger is running</h4>
+<span class="anchor_helper" id="_step_6_restarting_the_flying_passenger_daemon"></span><h4 class="float" data-anchor="_step_6_restarting_the_flying_passenger_daemon">Step 6: Restarting the Flying Passenger daemon</h4>
+<div class="paragraph"><p>If you are using <a href="#flying_passenger">Flying Passenger</a> then you must restart the Flying Passenger daemon by sending it the SIGTERM signal:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>kill `cat /path-to/flying-passenger.pid`</pre>
+</div>
+</div>
+<div class="paragraph"><p>Or, if Flying Passenger is not running with a PID file, look up its PID us <span class="monospaced">ps</span> and then send it SIGTERM:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>ps auxw | grep flying-passenger
+kill PID_OF_FLYING_PASSENGER</pre>
+</div>
+</div>
+<span class="anchor_helper" id="verify_passenger_running"></span><h4 class="float" data-anchor="verify_passenger_running">Step 7: Verifying that Phusion Passenger is running</h4>
 <div class="paragraph"><p>Restart your web server and run:</p></div>
 <div class="listingblock">
 <div class="content monospaced">
@@ -1491,24 +1526,7 @@ configuration file. However, it doesn’t copy any files to outside the Phusion
 <div class="sect2">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="tarball_generic_install"></span><h3 data-comment-topic="installing-via-the-source-tarball-1cgxrqc" data-anchor="tarball_generic_install">2.3. Generic installation, upgrade and downgrade method: via tarball</h3>
 <span class="anchor_helper" id="_step_1_download_and_extract_the_tarball"></span><h4 class="float" data-anchor="_step_1_download_and_extract_the_tarball">Step 1: download and extract the tarball</h4>
-<div class="paragraph"><p>Download the open source Phusion Passenger tarball from <a href="https://www.phusionpassenger.com/download#open_source">the Phusion Passenger website</a>. Specific older versions are not found on the Phusion Passenger website, but are found in the following places:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-All versions starting from 4.0.0 can be found on <a href="https://code.google.com/p/phusion-passenger/downloads/list">Google Code</a>.
-</p>
-</li>
-<li>
-<p>
-All versions prior to 4.0.0, except for beta releases and Release Candidates, can be found on <a href="http://rubyforge.org/frs/?group_id=5873&amp;release_id=46919">RubyForge</a>.
-</p>
-</li>
-<li>
-<p>
-All beta releases and Release Candidates prior to 4.0.0 beta 1 can be found on <a href="https://code.google.com/p/phusion-passenger/downloads/list">Google Code</a>.
-</p>
-</li>
-</ul></div>
+<div class="paragraph"><p>Download the open source Phusion Passenger tarball from <a href="https://www.phusionpassenger.com/download#open_source">the Phusion Passenger website</a>. Older versions can be found on <a href="https://www.phusionpassenger.com/file_releases">the release archive</a>.</p></div>
 <div class="paragraph"><p>If you a <a href="https://www.phusionpassenger.com/enterprise">Phusion Passenger Enterprise</a> customer, download the Phusion Passenger Enterprise tarball from the <a href="https://www.phusionpassenger.com/orders">Customer Area</a>. Also be sure to download the <strong>license key</strong> and save it as <em>/etc/passenger-enterprise-license</em>.</p></div>
 <div class="paragraph"><p>Once you have downloaded the tarball, pick a location to extract it to. You can pick any location. A good location is <em>/opt/passenger</em>. Let’s call this location <span class="monospaced">$PREFIX</span>. Create this directory and extract the tarball as follows:</p></div>
 <div class="listingblock">
@@ -1601,11 +1619,25 @@ sudo apt-get update</pre>
 <span class="anchor_helper" id="_step_5_run_the_phusion_passenger_installer"></span><h4 class="float" data-anchor="_step_5_run_the_phusion_passenger_installer">Step 5: run the Phusion Passenger installer</h4>
 <div class="paragraph"><p>Please refer to <a href="#run_passenger_installer">this section</a>.
 Note that the <span class="monospaced">passenger-install-apache2-module</span> command is inside the <em>bin</em> subdirectory of the Phusion Passenger source directory, so you would have to run something like <em>/opt/passenger/passenger-x.x.x/bin/passenger-install-apache2-module</em>.</p></div>
-<span class="anchor_helper" id="_step_6_verifying_that_phusion_passenger_is_running"></span><h4 class="float" data-anchor="_step_6_verifying_that_phusion_passenger_is_running">Step 6: Verifying that Phusion Passenger is running</h4>
+<span class="anchor_helper" id="_step_6_restarting_the_flying_passenger_daemon_2"></span><h4 class="float" data-anchor="_step_6_restarting_the_flying_passenger_daemon_2">Step 6: Restarting the Flying Passenger daemon</h4>
+<div class="paragraph"><p>If you are using <a href="#flying_passenger">Flying Passenger</a> then you must restart the Flying Passenger daemon by sending it the SIGTERM signal:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>kill `cat /path-to/flying-passenger.pid`</pre>
+</div>
+</div>
+<div class="paragraph"><p>Or, if Flying Passenger is not running with a PID file, look up its PID us <span class="monospaced">ps</span> and then send it SIGTERM:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>ps auxw | grep flying-passenger
+kill PID_OF_FLYING_PASSENGER</pre>
+</div>
+</div>
+<span class="anchor_helper" id="_step_7_verifying_that_phusion_passenger_is_running"></span><h4 class="float" data-anchor="_step_7_verifying_that_phusion_passenger_is_running">Step 7: Verifying that Phusion Passenger is running</h4>
 <div class="paragraph"><p>Please refer to <a href="#verify_passenger_running">this section</a>. Note that all Phusion Passenger administration scripts are located inside the <em>bin</em> subdirectory of the Phusion Passenger source directory, so you would have to run something like <em>/opt/passenger/passenger-x.x.x/bin/passenger-memory-stats</em>.</p></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_installing_or_upgrading_on_debian_6_or_ubuntu"></span><h3 data-comment-topic="installing-or-upgrading-on-ubuntu-1xg22xs" data-anchor="_installing_or_upgrading_on_debian_6_or_ubuntu">2.4. Installing or upgrading on Debian 6 or Ubuntu</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="install_on_debian_ubuntu"></span><h3 data-comment-topic="installing-or-upgrading-on-ubuntu-1xg22xs" data-anchor="install_on_debian_ubuntu">2.4. Installing or upgrading on Debian 6 or Ubuntu</h3>
 <div class="paragraph"><p>John Leach from Brightbox has kindly provided Ubuntu packages for Phusion Passenger. The Ubuntu Lucid packages are compatible with Debian 6. The packages are available from the <a href="http://wiki.brightbox.co.uk/docs:phusion-passenger">Brightbox repository</a>. Only packages for the open source version of Phusion Passenger are provided. <a href="https://www.phusionpassenger.com/enterprise">Phusion Passenger Enterprise</a> customers should use the <a href="#rubygems_generic_install">generic RubyGems installation method</a> or <a href="#tarball_generic_install">the generic tarball installation method</a> instead.</p></div>
 <div class="paragraph"><p>If you use these packages to install Phusion Passenger then you do not need to run <span class="monospaced">passenger-install-apache2-module</span> or <span class="monospaced">passenger-install-nginx-module</span>. These packages contain all the binaries that you need.</p></div>
 <div class="paragraph">
@@ -1614,7 +1646,7 @@ Note that the <span class="monospaced">passenger-install-apache2-module</span> c
 </div>
 <div class="listingblock">
 <div class="content monospaced">
-<pre>sudo apt-add-repository ppa:brightbox/passenger
+<pre>sudo apt-add-repository ppa:brightbox/passenger-experimental
 sudo apt-get update</pre>
 </div>
 </div>
@@ -1622,7 +1654,7 @@ sudo apt-get update</pre>
 <div class="paragraph"><p>Debian 6:</p></div>
 <div class="listingblock">
 <div class="content monospaced">
-<pre>sudo sh -c 'echo "deb http://ppa.launchpad.net/brightbox/passenger/ubuntu lucid main" &gt; /etc/apt/sources.list.d/brightbox-passenger.list'
+<pre>sudo sh -c 'echo "deb http://ppa.launchpad.net/brightbox/passenger-experimental/ubuntu lucid main" &gt; /etc/apt/sources.list.d/brightbox-passenger.list'
 sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys C3173AA6
 sudo apt-get update</pre>
 </div>
@@ -1630,7 +1662,7 @@ sudo apt-get update</pre>
 <div class="paragraph"><p>Ubuntu 8.04 Hardy:</p></div>
 <div class="listingblock">
 <div class="content monospaced">
-<pre>sudo sh -c 'echo "deb http://ppa.launchpad.net/brightbox/passenger/ubuntu hardy main" &gt; /etc/apt/sources.list.d/brightbox-passenger.list'
+<pre>sudo sh -c 'echo "deb http://ppa.launchpad.net/brightbox/passenger-experimental/ubuntu hardy main" &gt; /etc/apt/sources.list.d/brightbox-passenger.list'
 sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys C3173AA6
 sudo apt-get update</pre>
 </div>
@@ -1648,7 +1680,7 @@ sudo apt-get update</pre>
 </div>
 <div class="listingblock">
 <div class="content monospaced">
-<pre>sudo apt-add-repository ppa:brightbox/passenger-nginx
+<pre>sudo apt-add-repository ppa:brightbox/passenger-experimental
 sudo apt-get update</pre>
 </div>
 </div>
@@ -1656,7 +1688,7 @@ sudo apt-get update</pre>
 <div class="paragraph"><p>Debian 6:</p></div>
 <div class="listingblock">
 <div class="content monospaced">
-<pre>sudo sh -c 'echo "deb http://ppa.launchpad.net/brightbox/passenger-nginx/ubuntu lucid main" &gt; /etc/apt/sources.list.d/brightbox-passenger-nginx.list'
+<pre>sudo sh -c 'echo "deb http://ppa.launchpad.net/brightbox/passenger-experimental/ubuntu lucid main" &gt; /etc/apt/sources.list.d/brightbox-passenger-nginx.list'
 sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys C3173AA6
 sudo apt-get update</pre>
 </div>
@@ -1664,7 +1696,7 @@ sudo apt-get update</pre>
 <div class="paragraph"><p>Ubuntu 8.04 Hardy:</p></div>
 <div class="listingblock">
 <div class="content monospaced">
-<pre>sudo sh -c 'echo "deb http://ppa.launchpad.net/brightbox/passenger/ubuntu hardy main" &gt; /etc/apt/sources.list.d/brightbox-passenger-nginx.list'
+<pre>sudo sh -c 'echo "deb http://ppa.launchpad.net/brightbox/passenger-experimental/ubuntu hardy main" &gt; /etc/apt/sources.list.d/brightbox-passenger-nginx.list'
 sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys C3173AA6
 sudo apt-get update</pre>
 </div>
@@ -1889,16 +1921,29 @@ gpg --refresh-keys --keyserver keyserver.ubuntu.com</pre>
 </div>
 <div class="sect2">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_customizing_the_compilation_process"></span><h3 data-comment-topic="customizing-the-compilation-process-1sds3od" data-anchor="_customizing_the_compilation_process">2.9. Customizing the compilation process</h3>
+<div class="paragraph"><p>The Phusion Passenger compilation process can be customized with environment variables. You can learn more about environment variables in <a href="#about_environment_variables">About environment variables</a>.</p></div>
 <div class="sect3">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_setting_the_compiler"></span><h4 data-comment-topic="setting-the-compiler-1symq7h" data-anchor="_setting_the_compiler">2.9.1. Setting the compiler</h4>
 <div class="paragraph"><p>You can force the Phusion Passenger build system to use a specific C or C++ compiler by setting the <span class="monospaced">CC</span> and <span class="monospaced">CXX</span> environment variables. These may be set to any arbitrary shell commands.</p></div>
 <div class="paragraph"><p>For example, contributors who want to hack on Phusion Passenger may want to use Clang for faster compilation and <a href="http://ccache.samba.org/">ccache</a> for faster recompilation, and may want to enable more error-catching compilation flags:</p></div>
 <div class="listingblock">
-<div class="content monospaced">
-<pre>export CC='ccache clang -fcolor-diagnostics -Qunused-arguments -fcatch-undefined-behavior -ftrapv'
-export CXX='ccache clang++ -fcolor-diagnostics -Qunused-arguments -fcatch-undefined-behavior -ftrapv'</pre>
+<div class="content">
+<!-- Generator: GNU source-highlight 2.11.1
+by Lorenzo Bettini
+http://www.lorenzobettini.it
+http://www.gnu.org/software/src-highlite -->
+<pre><tt><span style="font-weight: bold"><span style="color: #0000FF">export</span></span> <span style="color: #009900">CC</span><span style="color: #990000">=</span><span style="color: #FF0000">'ccache clang -fcolor-diagnostics -Qunused-arguments -fcatch-undefined-behavior -ftrapv'</span>
+<span style="font-weight: bold"><span style="color: #0000FF">export</span></span> <span style="color: #009900">CXX</span><span style="color: #990000">=</span><span style="color: #FF0000">'ccache clang++ -fcolor-diagnostics -Qunused-arguments -fcatch-undefined-behavior -ftrapv'</span></tt></pre>
 </div>
 </div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="./images/icons/note.png" alt="Note">
+</td>
+<td class="content">If you run the installer with <span class="monospaced">sudo</span> then environment variables may not be passed properly. Learn more at <a href="#env_vars_and_sudo">Environment variables and sudo</a>.</td>
+</tr></table>
+</div>
 </div>
 <div class="sect3">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_adding_additional_compiler_or_linker_flags"></span><h4 data-comment-topic="adding-additional-compiler-or-linker-flags-wzu0ey" data-anchor="_adding_additional_compiler_or_linker_flags">2.9.2. Adding additional compiler or linker flags</h4>
@@ -1953,11 +1998,19 @@ export CXX='ccache clang++ -fcolor-diagnostics -Qunused-arguments -fcatch-undefi
 </p>
 </dd>
 </dl></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="./images/icons/note.png" alt="Note">
+</td>
+<td class="content">If you run the installer with <span class="monospaced">sudo</span> then environment variables may not be passed properly. Learn more at <a href="#env_vars_and_sudo">Environment variables and sudo</a>.</td>
+</tr></table>
+</div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_forcing_location_of_certain_command_line_tools"></span><h4 data-comment-topic="forcing-location-of-certain-command-line-tools-1hym30u" data-anchor="_forcing_location_of_certain_command_line_tools">2.9.3. Forcing location of certain command line tools</h4>
+<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-1hym30u" 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 often force the build to find certain command line tools at certain locations by using the following environment variables:</p></div>
+<div class="paragraph"><p>You can force the build to find certain command line tools at certain locations by using the following environment variables:</p></div>
 <div class="dlist"><dl>
 <dt class="hdlist1">
 <span class="monospaced">HTTPD</span>
@@ -1972,8 +2025,18 @@ export CXX='ccache clang++ -fcolor-diagnostics -Qunused-arguments -fcatch-undefi
 </dt>
 <dd>
 <p>
-        The location of the <span class="monospaced">apxs2</span> executable (the Apache module developer tool).
+        The location of the <span class="monospaced">apxs2</span> executable (the Apache module developer tool). Only used by <span class="monospaced">passenger-install-apache2-module</span>.
 </p>
+<div class="paragraph"><p>This environment variable, together with <span class="monospaced">HTTPD</span>, are what you need to customize if you have multiple Apache installations on your system, or if your Apache is located in a non-standard location which Phusion Passenger cannot detect. By setting <span class="monospaced">APXS2</span> and <span class="monospaced">HTTP</span> to the right paths, you can force Phusion Passenger to be compiled against that specific Apache installation.</p></div>
+<div class="paragraph"><p>For example, if your Apache installation is located in <span class="monospaced">/opt/lamp/apache2</span>, then you can run the installer as follows:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>$ sudo bash
+# export HTTPD=/opt/lampp/apache2/bin/apache
+# export APXS2=/opt/lampp/apache2/bin/apxs
+# passenger-install-apache2-module</pre>
+</div>
+</div>
 </dd>
 <dt class="hdlist1">
 <span class="monospaced">APR_CONFIG</span>
@@ -2008,6 +2071,14 @@ export CXX='ccache clang++ -fcolor-diagnostics -Qunused-arguments -fcatch-undefi
 </p>
 </dd>
 </dl></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="./images/icons/note.png" alt="Note">
+</td>
+<td class="content">If you run the installer with <span class="monospaced">sudo</span> then environment variables may not be passed properly. Learn more at <a href="#env_vars_and_sudo">Environment variables and sudo</a>.</td>
+</tr></table>
+</div>
 </div>
 </div>
 <div class="sect2">
@@ -2109,7 +2180,7 @@ done this, you need to remove the Phusion Passenger files.</p></div>
 <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 an <a href="https://www.phusionpassenger.com/enterprise">Phusion Passenger Enterprise</a> user, <span class="monospaced">gem uninstall passenger-enterprise-server</span>).
+If you installed Phusion Passenger via a Ruby gem, then run <span class="monospaced">gem uninstall passenger</span> (or, if you’re a <a href="https://www.phusionpassenger.com/enterprise">Phusion Passenger Enterprise</a> user, <span class="monospaced">gem uninstall passenger-enterprise-server</span>).
   You <a href="#is_ruby_home_or_system_wide_installed">might have to run this as root</a>.
 </p>
 </li>
@@ -2879,7 +2950,7 @@ this option as well. Please read
 <div class="paragraph"><p>This required option may only occur once, in the global server configuration.</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="PassengerDefaultRuby"></span><h3 data-comment-topic="passengerdefaultruby-and-passengerruby-7zblp8" data-anchor="PassengerDefaultRuby">6.2. PassengerDefaultRuby and PassengerRuby</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerDefaultRuby"></span><h3 data-comment-topic="passengerdefaultruby-and-passengerruby-7zblp8" data-anchor="PassengerDefaultRuby">6.2. PassengerDefaultRuby &lt;filename&gt;</h3>
 <div class="paragraph"><p><strong>Introduced in version 4.0.0.</strong></p></div>
 <div class="paragraph"><p>This option specifies the default Ruby interpreter to use for web apps as well as for all sorts of internal Phusion Passenger helper scripts, e.g. the one used by <a href="#PassengerPreStart">PassengerPreStart</a>. Please see <a href="#PassengerRuby">PassengerRuby</a> for more information, as well as how it relates to <a href="#PassengerRuby">PassengerRuby</a>.</p></div>
 <div class="paragraph"><p>This option may occur in the global server configuration. The default value is <em>ruby</em>, meaning that the Ruby interpreter will be looked up according to the <span class="monospaced">PATH</span> environment variable.</p></div>
@@ -3559,7 +3630,7 @@ In <em>.htaccess</em>, if <span class="monospaced">AllowOverride Options</span>
 The default value is <em>on</em>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_passengeruser_lt_username_gt"></span><h4 data-comment-topic="passengeruser" data-anchor="_passengeruser_lt_username_gt">6.14.2. PassengerUser &lt;username&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerUser"></span><h4 data-comment-topic="passengeruser" data-anchor="PassengerUser">6.14.2. PassengerUser &lt;username&gt;</h4>
 <div class="paragraph"><p>If <a href="#user_switching">user switching support</a> is enabled, then Phusion Passenger will
 by default run the web application as the owner of the file <em>config/environment.rb</em>
 (for Rails apps) or <em>config.ru</em> (for Rack apps). This option allows you to override
@@ -3586,7 +3657,7 @@ In a <span class="monospaced">&lt;Directory&gt;</span> or <span class="monospace
 <div class="paragraph"><p>In each place, it may be specified at most once.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_passengergroup_lt_group_name_gt"></span><h4 data-comment-topic="passengergroup" data-anchor="_passengergroup_lt_group_name_gt">6.14.3. PassengerGroup &lt;group name&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerGroup"></span><h4 data-comment-topic="passengergroup" data-anchor="PassengerGroup">6.14.3. PassengerGroup &lt;group name&gt;</h4>
 <div class="paragraph"><p>If <a href="#user_switching">user switching support</a> is enabled, then Phusion Passenger will
 by default run the web application as the primary group of the owner of the file
 <em>config/environment.rb</em> (for Rails apps) or <em>config.ru</em> (for Rack apps). This option
@@ -3632,7 +3703,7 @@ The default value is the primary group of the user specifified by
 <a href="#PassengerDefaultUser">PassengerDefaultUser</a>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_passengerfriendlyerrorpages_lt_on_off_gt"></span><h4 data-comment-topic="passengerfriendlyerrorpages" data-anchor="_passengerfriendlyerrorpages_lt_on_off_gt">6.14.6. PassengerFriendlyErrorPages &lt;on|off&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerFriendlyErrorPages"></span><h4 data-comment-topic="passengerfriendlyerrorpages" data-anchor="PassengerFriendlyErrorPages">6.14.6. PassengerFriendlyErrorPages &lt;on|off&gt;</h4>
 <div class="paragraph"><p>Phusion Passenger can display friendly error pages whenever an application fails
 to start. This friendly error page presents the startup error message, some
 suggestions for solving the problem, and a backtrace. This feature is very useful
@@ -4080,6 +4151,17 @@ measure to avoid freezing applications.</p></div>
 </td>
 </tr></table>
 </div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<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>
+</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="PassengerMemoryLimit"></span><h4 data-comment-topic="passengermemorylimit-integer--18irza1" data-anchor="PassengerMemoryLimit">6.15.11. PassengerMemoryLimit &lt;integer&gt;</h4>
@@ -4623,7 +4705,7 @@ displaying maintenance.html will work fine even for URLs starting with "/users".
 <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="_logging_and_debugging_options"></span><h3 data-comment-topic="logging-and-debugging-options-el2cuc" data-anchor="_logging_and_debugging_options">6.17. Logging and debugging options</h3>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_passengerloglevel_lt_integer_gt"></span><h4 data-comment-topic="passengerloglevel-integer--s3kbil" data-anchor="_passengerloglevel_lt_integer_gt">6.17.1. PassengerLogLevel &lt;integer&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerLogLevel"></span><h4 data-comment-topic="passengerloglevel-integer--s3kbil" data-anchor="PassengerLogLevel">6.17.1. PassengerLogLevel &lt;integer&gt;</h4>
 <div class="paragraph"><p>This option allows one to specify how much information Phusion Passenger should
 write to the Apache error log file. A higher log level value means that more
 information will be logged.</p></div>
@@ -5670,51 +5752,199 @@ through the <em>X-Passenger-Connect-Password</em> HTTP header, like this:</p></d
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_tips"></span><h2 data-comment-topic="tips-19cwwf7" data-anchor="_tips">9. Tips</h2>
 <div class="sectionbody">
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="user_switching"></span><h3 data-comment-topic="user-switching-security--8njx1x" data-anchor="user_switching">9.1. User switching (security)</h3>
-<div class="paragraph"><p>There is a problem that plagues most PHP web hosts, namely the fact that all PHP
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="user_switching"></span><h3 data-comment-topic="user-switching-security--8njx1x" data-anchor="user_switching">9.1. User Switching (security feature)</h3>
+<div class="paragraph"><p>Phusion Passenger supports automatic <em>user switching</em>: by default, it attempts to run applications as the "right" user, instead of running all applications as the same user.</p></div>
+<div class="paragraph"><p>To better understand the problem, let us consider the situation with PHP.
+There is a problem that plagues most PHP web hosts, namely the fact that all PHP
 applications are run in the same user context as the web server. So for
 example, Joe’s PHP application will be able to read Jane’s PHP application’s
 passwords. This is obviously undesirable on many servers.</p></div>
-<div class="paragraph"><p>Phusion Passenger solves this problem by implementing <em>user switching</em>. A Rails
-application is started as the owner of the file <em>config/environment.rb</em>,
-and a Rack application is started as the owner of the file <em>config.ru</em>.
-So if <em>/home/webapps/foo/config/environment.rb</em> is owned by <em>joe</em>, then Phusion
-Passenger will launch the corresponding application as <em>joe</em> as well.</p></div>
-<div class="paragraph"><p>This behavior is the default, and you don’t need to configure anything. But
-there are things that you should keep in mind:</p></div>
+<div class="paragraph"><p>Phusion Passenger’s <em>user switching</em> feature solves this problem. Applications are
+run as the owner of their "startup file". For Ruby apps, the startup file is
+<span class="monospaced">config.ru</span> (Rack and Rails &gt;= 3) or <span class="monospaced">config/environment.rb</span> (Rails 1 and 2). For
+Python apps, the startup file is <span class="monospaced">passenger_wsgi.py</span>. So suppose that <span class="monospaced">config.ru</span>
+is owned by user <em>joe</em>, then Phusion Passenger will spawn the corresponding
+application as <em>joe</em> as well. The exact rules are a little bit more complicated,
+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-yxvtxo" data-anchor="_requirements">9.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>
+<li>
+<p>
+When not using <a href="#flying_passenger">Flying Passenger</a> (this is probably the case):
+</p>
+<div class="ulist"><ul>
+<li>
+<p>
+The
+  <a href="#PassengerUserSwitching">PassengerUserSwitching</a>
+option must be enabled.
+</p>
+</li>
+<li>
+<p>
+The web server’s control process must have root privileges. This is the case on most installations.
+</p>
+</li>
+</ul></div>
+</li>
+<li>
+<p>
+When using <a href="#flying_passenger">Flying Passenger</a>:
+</p>
 <div class="ulist"><ul>
 <li>
 <p>
-The owner of <em>environment.rb</em>/<em>config.ru</em> must have read access to the application’s
-  root directory, and read/write access to the application’s <em>logs</em> directory.
+The Flying Passenger daemon must be run with root privileges.
 </p>
 </li>
+</ul></div>
+</li>
+</ul></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="_effects"></span><h4 data-comment-topic="effects-1lko7vo" data-anchor="_effects">9.1.2. Effects</h4>
+<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>
+<td class="tableblock halign-left valign-top"><p class="tableblock"></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>PassengerUserSwitching on</strong></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><strong>PassengerUserSwitching off</strong></p></td>
+</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">PassengerDefaultUser</a> and
+  <a href="#PassengerDefaultGroup">PassengerDefaultGroup</a>.</p></td>
+</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>
+<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>
+<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>
+<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>
+<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">
 <li>
 <p>
-This feature is only available if the web server is started by <em>root</em>. This is the
-  case on most installations.
+If
+  <a href="#PassengerUser">PassengerUser</a> or
+  <a href="#PassengerGroup">PassengerGroup</a>
+are set, then the application will be run as the specified user/group. Thus, these options are a good way to override user switching settings.
 </p>
 </li>
 <li>
 <p>
-Under no circumstances will applications be run as <em>root</em>. If
-  <em>environment.rb</em>/<em>config.ru</em> is owned as root or by an unknown user, then the
-  Rails/Rack application will run as the user specified by
+If the startup file is owned by root or an unknown user, then the application will run as the user specified by
   <a href="#PassengerDefaultUser">PassengerDefaultUser</a> and
   <a href="#PassengerDefaultGroup">PassengerDefaultGroup</a>.
 </p>
 </li>
+<li>
+<p>
+Otherwise, the application is run as the owner of the startup file.
+</p>
+</li>
+</ol></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="_caveats_amp_troubleshooting"></span><h4 data-comment-topic="caveats-troubleshooting-161hgge" data-anchor="_caveats_amp_troubleshooting">9.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>
+<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.
+</p>
+</li>
+<li>
+<p>
+The application fails to start and its error message mentions the path <em>/nonexistent</em>. This probably indicates that your application is started as the <em>nobody</em> user. This is because on many systems, the <em>nobody</em> user’s home directory is <em>/nonexistent</em>.
+</p>
+</li>
 </ul></div>
-<div class="paragraph"><p>User switching can be disabled with the
-<a href="#PassengerUserSwitching">PassengerUserSwitching</a>
-option.</p></div>
+<div class="paragraph"><p>To check whether it is indeed the case that your application is started as a different user than you intended to, see <a href="#finding_out_app_user">Finding out what user an application is running as</a>.</p></div>
+<div class="paragraph"><p>The most likely reason why your application is started as <em>nobody</em> is probably because your startup file is owned by <em>root</em>, by <em>nobody</em> or by an unknown user. To fix this, change the owner of the startup file to the owner that you want to run the application as.</p></div>
+<div class="paragraph"><p>Whatever user your application runs as, it must have read access to the <a href="#application_root">application root</a>, and read/write access to the application’s <em>logs</em> directory.</p></div>
+</div>
+<div class="sect3">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="finding_out_app_user"></span><h4 data-comment-topic="finding-out-what-user-an-application-is-running-as-7uwrol" data-anchor="finding_out_app_user">9.1.4. Finding out what user an application is running as</h4>
+<div class="paragraph"><p>To find our what user an application is started as, first access its URL in your browser so that Phusion Passenger starts the application. For example:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>http://www.example.local/</pre>
+</div>
+</div>
+<div class="paragraph"><p>The application will now either successfully start or fail to start. If it fails to start then you will see an error page that tells you what user the application was being started as. If you do not see the error page in the browser then set
+  <a href="#PassengerFriendlyErrorPages">PassengerFriendlyErrorPages</a>
+on.</p></div>
+<div class="paragraph"><p>If the application successfully started, then run <span class="monospaced">passenger-status</span> to find the process’s PID:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>.---------- General information -----------
+Max pool size : 6
+Processes     : 1
+Requests in top-level queue : 0
+
+.---------- Application groups -----------
+/webapps/example.local#default:
+  App root: /webapps/example.local
+  Requests in queue: 0
+  * PID: 16915   Sessions: 0       Processed: 1       Uptime: 2s
+    CPU: 0%      Memory  : 9M      Last used: 2s ago</pre>
+</div>
+</div>
+<div class="paragraph"><p>In the above example we see that the PID is 16915. Next, use <em>ps</em> to find out the user that it is running as:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre># ps -o pid,user,comm -p 16915
+  PID USER    COMM
+16915 phusion Passenger RackApp: /webapps/example.local</pre>
+</div>
+</div>
+<div class="paragraph"><p>As you can see, the application in this example is being run as user <em>phusion</em>.</p></div>
+</div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="reducing_memory_usage"></span><h3 data-comment-topic="reducing-memory-consumption-of-ruby-on-rails-applications-by-33--1ubxnq0" data-anchor="reducing_memory_usage">9.2. Reducing memory consumption of Ruby on Rails applications by 33%</h3>
-<div class="paragraph"><p>Is it possible to reduce memory consumption of your Rails applications by 33% on average,
-by using <a href="http://www.rubyenterpriseedition.com/">Ruby Enterprise Edition</a>.
-Please visit the website for details.</p></div>
-<div class="paragraph"><p>Note that this feature does not apply to Rack applications.</p></div>
+<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--1ubxnq0" data-anchor="reducing_memory_usage">9.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>
+<li>
+<p>
+MRI Ruby &gt;= 2.0. Versions prior to 2.0 did not have a copy-on-write friendly garbage collector.
+</p>
+</li>
+<li>
+<p>
+<a href="http://www.rubyenterpriseedition.com/">Ruby Enterprise Edition</a>, which was Phusion’s branch of MRI Ruby 1.8 with a copy-on-write friendly garbage collector and other enhancement. It has reached End-Of-Life as of 2012, but remains available for legacy systems.
+</p>
+</li>
+</ul></div>
 </div>
 <div class="sect2">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="capistrano"></span><h3 data-comment-topic="capistrano-recipe-syzgo7" data-anchor="capistrano">9.3. Capistrano recipe</h3>
@@ -5754,7 +5984,9 @@ end</pre>
 <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="bundler_support"></span><h3 data-comment-topic="bundler-support-cf72ih" data-anchor="bundler_support">9.4. Bundler support</h3>
 <div class="paragraph"><p>Phusion Passenger has automatic support for <a href="http://gembundler.com/git.html">Bundler</a>.
-It works as follows:</p></div>
+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>
 <li>
 <p>
@@ -5779,10 +6011,22 @@ have any negative effects.</p></div>
 <div class="paragraph"><p>Phusion Passenger assumes that you’re using Bundler &gt;= 0.9.5. If you don’t want Phusion
 Passenger to run its Bundler support code, e.g. because you need to use an older version
 of Bundler with an incompatible API or because you use a system other than Bundler, then
-you can override Phusion Passenger’s Bundler support code by creating a file
+you can override Phusion Passenger’s Bundler support code by creating an empty file
 <em>config/setup_load_paths.rb</em>. If this file exists then it will be required before loading
 the application startup file. In this file you can do whatever you need to setup Bundler
 or a similar system.</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="add_passenger_to_gemfile"></span><h4 data-comment-topic="does-phusion-passenger-itself-need-to-be-added-to-the-gemfile--17whimp" data-anchor="add_passenger_to_gemfile">9.4.1. Does Phusion Passenger itself need to be added to the Gemfile?</h4>
+<div class="paragraph"><p>It is never necessary to add Phusion Passenger to the application’s Gemfile. In case of Phusion Passenger Standalone, it is not necessary to execute the <span class="monospaced">passenger</span> command through <span class="monospaced">bundle exec</span>. The reason for this is because Phusion Passenger automatically loads the Gemfile environment. Most other Ruby application servers do not automatically load the Gemfile environment, which is why they must be added to the Gemfile and be executed with <span class="monospaced">bundle exec</span>.</p></div>
+<div class="paragraph"><p>Even when your application uses any of the Phusion Passenger APIs, you still do not need to add Phusion Passenger to the Gemfile. The only thing you need to do is to put Phusion Passenger API calls inside <span class="monospaced">if</span> blocks that check whether Phusion Passenger is active, by checking whether the <span class="monospaced">PhusionPassenger</span> namespace is defined:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre><strong>if</strong> defined?(PhusionPassenger)
+    ...
+<strong>end</strong></pre>
+</div>
+</div>
+</div>
 </div>
 <div class="sect2">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_installing_multiple_ruby_on_rails_versions"></span><h3 data-comment-topic="installing-multiple-ruby-on-rails-versions-mi5j14" data-anchor="_installing_multiple_ruby_on_rails_versions">9.5. Installing multiple Ruby on Rails versions</h3>
@@ -5894,7 +6138,7 @@ You can actually perform out-of-band work when you receive a <span class="monosp
 </li>
 </ol></div>
 <div class="paragraph"><p>Note that even though you can request out-of-band work, there’s no guarantee that Phusion Passenger will send an <span class="monospaced">oob_work</span> event in a timely manner, if at all. It is also possible that Phusion Passenger sends an <span class="monospaced">oob_work</span> event without you ever having requested one. This latter could for example happen if the OOB work is administrator-initiated. Do not make any assumptions in your code.</p></div>
-<div class="paragraph"><p>Here’s an example which implements out-of-band garbage collection using the Out-of-Band framework:</p></div>
+<div class="paragraph"><p>Here’s an example which implements out-of-band garbage collection using the Out-of-Band framework. This example code doesn’t do anything when the code is not being run in Phusion Passenger, thanks to the <span class="monospaced">if</span> block.</p></div>
 <div class="listingblock">
 <div class="content">
 <!-- Generator: GNU source-highlight 2.11.1
@@ -5906,27 +6150,32 @@ http://www.gnu.org/software/src-highlite -->
 response<span style="color: #990000">.</span>headers<span style="color: #990000">[</span><span style="color: #FF0000">"X-Passenger-Request-OOB-Work"</span><span style="color: #990000">]</span> <span style="color: #990000">=</span> <span style="color: #FF0000">"true"</span>
 
 <span style="font-style: italic"><span style="color: #9A1900"># Somewhere during application initialization:</span></span>
-PhusionPassenger<span style="color: #990000">.</span>on_event<span style="color: #990000">(:</span>oob_work<span style="color: #990000">)</span> <span style="font-weight: bold"><span style="color: #0000FF">do</span></span>
-  <span style="font-style: italic"><span style="color: #9A1900"># Phusion Passenger has told us that we're ready to perform OOB work.</span></span>
-  t0 <span style="color: #990000">=</span> Time<span style="color: #990000">.</span>now
-  GC<span style="color: #990000">.</span>start
-  Rails<span style="color: #990000">.</span>logger<span style="color: #990000">.</span>info <span style="color: #FF0000">"Out-Of-Bound GC finished in #{Time.now - t0} sec"</span>
+<span style="font-weight: bold"><span style="color: #0000FF">if</span></span> <span style="font-weight: bold"><span style="color: #0000FF">defined</span></span><span style="color: #990000">?(</span>PhusionPassenger<span style="color: #990000">)</span>
+    PhusionPassenger<span style="color: #990000">.</span>on_event<span style="color: #990000">(:</span>oob_work<span style="color: #990000">)</span> <span style="font-weight: bold"><span style="color: #0000FF">do</span></span>
+        <span style="font-style: italic"><span style="color: #9A1900"># Phusion Passenger has told us that we're ready to perform OOB work.</span></span>
+        t0 <span style="color: #990000">=</span> Time<span style="color: #990000">.</span>now
+        GC<span style="color: #990000">.</span>start
+        Rails<span style="color: #990000">.</span>logger<span style="color: #990000">.</span>info <span style="color: #FF0000">"Out-Of-Bound GC finished in #{Time.now - t0} sec"</span>
+    <span style="font-weight: bold"><span style="color: #0000FF">end</span></span>
 <span style="font-weight: bold"><span style="color: #0000FF">end</span></span></tt></pre>
 </div>
 </div>
-<div class="paragraph"><p>For your convenience, Phusion Passenger provides a Rack middleware for out-of-band garbage collection. Add this to your <span class="monospaced">config.ru</span>:</p></div>
+<div class="paragraph"><p>For your convenience, Phusion Passenger provides a Rack middleware for out-of-band garbage collection. Add the following to your <span class="monospaced">config.ru</span>. Likewise, this example code doesn’t do anything when the code is not being run in Phusion Passenger, thanks to the <span class="monospaced">if</span> block.</p></div>
 <div class="listingblock">
 <div class="content">
 <!-- Generator: GNU source-highlight 2.11.1
 by Lorenzo Bettini
 http://www.lorenzobettini.it
 http://www.gnu.org/software/src-highlite -->
-<pre><tt><span style="font-weight: bold"><span style="color: #000080">require</span></span> <span style="color: #FF0000">'phusion_passenger/rack/out_of_band_gc'</span>
+<pre><tt><span style="font-weight: bold"><span style="color: #0000FF">if</span></span> <span style="font-weight: bold"><span style="color: #0000FF">defined</span></span><span style="color: #990000">?(</span>PhusionPassenger<span style="color: #990000">)</span>
+    <span style="font-weight: bold"><span style="color: #000080">require</span></span> <span style="color: #FF0000">'phusion_passenger/rack/out_of_band_gc'</span>
 
-<span style="font-style: italic"><span style="color: #9A1900"># Trigger out-of-band GC every 5 requests.</span></span>
-use PhusionPassenger<span style="color: #990000">::</span>Rack<span style="color: #990000">::</span>OutOfBandGc<span style="color: #990000">,</span> <span style="color: #993399">5</span></tt></pre>
+    <span style="font-style: italic"><span style="color: #9A1900"># Trigger out-of-band GC every 5 requests.</span></span>
+    use PhusionPassenger<span style="color: #990000">::</span>Rack<span style="color: #990000">::</span>OutOfBandGc<span style="color: #990000">,</span> <span style="color: #993399">5</span>
+<span style="font-weight: bold"><span style="color: #0000FF">end</span></span></tt></pre>
 </div>
 </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>
 <li>
@@ -5937,12 +6186,223 @@ use PhusionPassenger<span style="color: #990000">::</span>Rack<span style="color
 </ul></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_x_sendfile_support"></span><h3 data-comment-topic="x-sendfile-support-1cgyykw" data-anchor="_x_sendfile_support">9.9. X-Sendfile support</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="flying_passenger"></span><h3 data-comment-topic="flying-passenger-q916f7" data-anchor="flying_passenger">9.9. Flying Passenger</h3>
+<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.6. <a href="https://www.phusionpassenger.com/download">Buy Phusion Passenger Enterprise here.</a></strong></p></div>
+<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>
+<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.
+</p>
+</li>
+<li>
+<p>
+The web server must be configured to forward requests to the Flying Passenger daemon.
+</p>
+</li>
+<li>
+<p>
+You should beware of the <a href="#flying_passenger_caveats">caveats and limitations</a>.
+</p>
+</li>
+</ul></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_2"></span><h4 data-comment-topic="requirements-1ntkin3" data-anchor="_requirements_2">9.9.1. Requirements</h4>
+<div class="paragraph"><p>At this time, this feature is <strong>only available in the Enterprise version of Phusion Passenger for Nginx</strong>. You must have Phusion Passenger for Nginx properly installed.</p></div>
+</div>
+<div class="sect3">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_basic_usage"></span><h4 data-comment-topic="basic-usage-joifsk" data-anchor="_basic_usage">9.9.2. Basic usage</h4>
+<div class="paragraph"><p>Start the Flying Passenger daemon by invoking the <span class="monospaced">flying-passenger</span> command. The only required option is <span class="monospaced">--socket-file</span>. Depending on whether you wish to enable <a href="#user_switching">User Switching</a>, you have to start <span class="monospaced">flying-passenger</span> with root privileges or not.</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>$ sudo flying-passenger --socket-file=/var/run/flying-passenger.sock
+I, [2013-06-14T09:10:13.095339 #77179]  INFO -- : Welcome to Flying Passenger 4.1.0
+I, [2013-06-14T09:10:13.095339 #77179]  INFO -- : Starting PassengerWatchdog...
+I, [2013-06-14T09:10:13.097036 #77179]  INFO -- : PassengerWatchdog started on PID 77181
+...
+I, [2013-06-14T09:10:13.129017 #77179]  INFO -- : PassengerWatchdog initialized properly
+I, [2013-06-14T09:10:13.129127 #77179]  INFO -- : Flying Passenger up and listening on /var/run/flying-passenger.sock!</pre>
+</div>
+</div>
+<div class="paragraph"><p>Now configure Phusion Passenger for Nginx to make use of the Flying Passenger daemon, by setting the <span class="monospaced">passenger_fly_with</span> option to the socket filename:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>http {
+    ...
+    passenger_fly_with /var/run/flying-passenger.sock;
+    ...
+}</pre>
+</div>
+</div>
+<div class="paragraph"><p>After (re)starting Nginx, Nginx + Flying Passenger is fully operational:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>$ sudo /path-to/nginx</pre>
+</div>
+</div>
+<div class="paragraph"><p>You can test it by adding a virtual host for a web app:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>http {
+    ...
+
+    server {
+        listen 80;
+        server_name www.foo.local;
+        root /webapps/foo/public;
+        passenger_enabled on;
+    }
+}</pre>
+</div>
+</div>
+<div class="paragraph"><p>Verify that it works by making an HTTP request to it:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>$ curl http://www.foo.local/</pre>
+</div>
+</div>
+<div class="paragraph"><p>Now let’s verify that restarting the web server does not restart the just-spawned application process. Run <span class="monospaced">passenger-status</span> to obtain the PID of the application process:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>$ sudo passenger-status
+Version: 4.1.0
+Date   : 2013-06-14 09:21:51 -0400
+.---------- General information -----------
+Max pool size : 6
+Processes     : 1
+Requests in top-level queue : 0
+
+.---------- Application groups -----------
+/webapps/foo#default:
+  App root: /webapps/foo
+  Requests in queue: 0
+  * PID: 77283   Sessions: 0       Processed: 1       Uptime: 2s
+    CPU: 1%      Memory  : 8M      Last used: 2s ago</pre>
+</div>
+</div>
+<div class="paragraph"><p>As you can see, the PID of the application process is <strong>77283</strong>. Now let’s see what happens if we restart Nginx:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>$ sudo /path-to/nginx -s stop
+$ sudo /path-to/nginx
+$ sudo passenger-status</pre>
+</div>
+</div>
+<div class="paragraph"><p>The application process should remain there, unchanged:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>$ sudo passenger-status
+Version: 4.1.0
+Date   : 2013-06-14 09:21:51 -0400
+.---------- General information -----------
+Max pool size : 6
+Processes     : 1
+Requests in top-level queue : 0
+
+.---------- Application groups -----------
+/webapps/foo#default:
+  App root: /webapps/foo
+  Requests in queue: 0
+  * PID: 77283   Sessions: 0       Processed: 1       Uptime: 18s
+    CPU: 1%      Memory  : 8M      Last used: 18s ago</pre>
+</div>
+</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="configuring_flying_passenger"></span><h4 data-comment-topic="configuring-flying-passenger-1v35vgg" data-anchor="configuring_flying_passenger">9.9.3. Configuring Flying Passenger</h4>
+<div class="paragraph"><p>Flying Passenger gets <strong>some</strong> configuration from the web server, but not all. In particular, most web server directives that are only valid in the <span class="monospaced">http</span> context, e.g. <a href="#PassengerLogLevel">passenger_log_level</a>, have no effect when using Flying Passenger. Instead, you are supposed to pass these configuration directives through command line options to the Flying Passenger daemon. Configuration directives that have no effect on Flying Passenger are documented as such. You can assume that configuration directives that are not documented as such, work fine on Flying Passenger.</p></div>
+<div class="paragraph"><p>For example, to achieve the same effect as setting passenger_log_level to 2, run the Flying Passenger daemon as follows:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>$ sudo flying-passenger --socket-file=/var/run/flying-passenger.sock --log-level=2</pre>
+</div>
+</div>
+<div class="paragraph"><p>Currently, not all configuration directives have a Flying Passenger equivalent. Run the following command to see an overview of available options:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>$ flying-passenger --help</pre>
+</div>
+</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="_managing_the_flying_passenger_daemon"></span><h4 data-comment-topic="managing-the-flying-passenger-daemon-1bng2bu" data-anchor="_managing_the_flying_passenger_daemon">9.9.4. Managing the Flying Passenger daemon</h4>
+<div class="paragraph"><p>The Flying Passenger daemon runs in the foreground by default. This is undesirable on server environments. You can make it go into the background by passing <span class="monospaced">--daemonize</span>, <span class="monospaced">--log-file</span> and <span class="monospaced">--pid-file</span>:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>$ sudo flying-passenger --socket-file=/var/run/flying-passenger.sock \
+    --daemonize --log-file=/var/log/flying-passenger.log \
+    --pid-file=/var/run/flying-passenger.pid</pre>
+</div>
+</div>
+<div class="paragraph"><p>You can shut down a Flying Passenger daemon by sending SIGINT or SIGTERM to it:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>$ kill `cat /var/run/flying-passenger.pid`</pre>
+</div>
+</div>
+<div class="paragraph"><p>We recommend using <a href="http://cr.yp.to/daemontools.html">daemontools</a> or <a href="http://smarden.org/runit/">runit</a> for managing the Flying Passenger daemon. These tools will allow automatically starting the Flying Passenger daemon at boot, and will automatically restart the daemon if it crashes. You can create and enable a daemontools/runit service as folows:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>$ sudo mkdir /etc/service/flying-passenger
+$ sudo nano /etc/service/flying-passenger/run
+#!/bin/sh
+exec /path-to/flying-passenger \
+    --socket-file=/var/run/flying-passenger.sock \
+    --log-file=/var/log/flying-passenger.log \
+    --pid-file=/var/run/flying-passenger.pid</pre>
+</div>
+</div>
+<div class="paragraph"><p>Immediately after creating the <span class="monospaced">run</span> file, daemontools/runit automatically runs it to start the daemon. Note that the location (<span class="monospaced">/etc/service</span>) depends on the OS or Linux distros. Sometimes it’s <span class="monospaced">/service</span>. Also note that we start the Flying Passenger daemon without <span class="monospaced">--daemonize</span>.</p></div>
+<div class="paragraph"><p>To shut down a daemontools/runit-managed daemon, you need to use <span class="monospaced">svc -d /etc/service/flying-passenger</span> (daemontools) or <span class="monospaced">sv stop /etc/service/flying-passenger</span> (runit) instead of sending a signal to the process.</p></div>
+</div>
+<div class="sect3">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="flying_passenger_caveats"></span><h4 data-comment-topic="caveats-and-limitations-lz3rbb" data-anchor="flying_passenger_caveats">9.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>
+<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.
+</p>
+</li>
+<li>
+<p>
+The <a href="#PassengerRoot">passenger_root</a> directive has no effect. When using Flying Passenger, you are not supposed to set <span class="monospaced">passenger_root</span>.
+</p>
+</li>
+<li>
+<p>
+When you add a new application to the web server configuration, Flying Passenger will automatically pick up the application’s settings and spawn this new application upon the first request to it. However it is not capable of automatically starting the new app before a request has been sent to it (i.e. <a href="#PassengerPreStart">passenger_pre_start</a>-like behavior is not available in this case). As a workaround, you can send an HTTP request to your application after starting the daemon, which forces it to spawn application processes.
+</p>
+</li>
+<li>
+<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>
+<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.
+</p>
+</li>
+<li>
+<p>
+Restart the Flying Passenger daemon.
+</p>
+</li>
+</ul></div>
+</li>
+</ul></div>
+</div>
+</div>
+<div class="sect2">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_x_sendfile_support"></span><h3 data-comment-topic="x-sendfile-support-1cgyykw" data-anchor="_x_sendfile_support">9.10. X-Sendfile support</h3>
 <div class="paragraph"><p>Phusion Passenger does not provide X-Sendfile support by itself. Please install
 <a href="http://tn123.ath.cx/mod_xsendfile/">mod_xsendfile</a> for X-Sendfile support.</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="_upload_progress"></span><h3 data-comment-topic="upload-progress-71cyl7" data-anchor="_upload_progress">9.10. Upload progress</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_upload_progress"></span><h3 data-comment-topic="upload-progress-71cyl7" data-anchor="_upload_progress">9.11. Upload progress</h3>
 <div class="paragraph"><p>Phusion Passenger does not provide upload progress support by itself. Please
 try drogus’s <a href="http://github.com/drogus/apache-upload-progress-module/tree/master">
 Apache upload progress module</a> instead.</p></div>
@@ -6457,6 +6917,332 @@ has no effect.</p></div>
 </div>
 </div>
 </div>
+<div class="sect1">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="about_environment_variables"></span><h2 data-comment-topic="appendix-d-about-environment-variables-1lebv1u" data-anchor="about_environment_variables">14. Appendix D: About environment variables</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>The Phusion Passenger compilation process can be customized with environment variables.</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>
+<li>
+<p>
+…only newly spawned bash shells see them.
+</p>
+</li>
+<li>
+<p>
+…the web server usually does not see them, because the web server tends to be started from init scripts, not from bash.
+</p>
+</li>
+<li>
+<p>
+…cron jobs do not see them, because cron jobs' environment variables are entirely dictated by their crontabs.
+</p>
+</li>
+</ul></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="./images/icons/note.png" alt="Note">
+</td>
+<td class="content">Because this chapter is meant for beginners, it assumes that the reader uses the bash shell. This chapter does not describe instructions for zsh, csh or other shells. We assume that users of other shells are familiar with the Bourne shell syntax, and know how to apply the instructions in this chapter in their shells' native syntaxes.</td>
+</tr></table>
+</div>
+<div class="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-85e6aa" data-anchor="_working_with_environment_variables">14.1. Working with environment variables</h3>
+<div class="paragraph"><p>You can see all environment variables in your shell by running the following command:</p></div>
+<div class="listingblock">
+<div class="content">
+<!-- Generator: GNU source-highlight 2.11.1
+by Lorenzo Bettini
+http://www.lorenzobettini.it
+http://www.gnu.org/software/src-highlite -->
+<pre><tt>env</tt></pre>
+</div>
+</div>
+<div class="paragraph"><p>You can set an evironment variable with the syntax <span class="monospaced">export &lt;NAME&gt;=&lt;VALUE&gt;</span>. For example, to set the <span class="monospaced">APXS2</span> variable to the value <span class="monospaced">/usr/sbin/apxs2</span>:</p></div>
+<div class="listingblock">
+<div class="content">
+<!-- Generator: GNU source-highlight 2.11.1
+by Lorenzo Bettini
+http://www.lorenzobettini.it
+http://www.gnu.org/software/src-highlite -->
+<pre><tt><span style="font-weight: bold"><span style="color: #0000FF">export</span></span> <span style="color: #009900">APXS2</span><span style="color: #990000">=</span>/usr/sbin/apxs<span style="color: #993399">2</span></tt></pre>
+</div>
+</div>
+<div class="paragraph"><p>Any process that you run from your shell from that point on will have said environment variable:</p></div>
+<div class="listingblock">
+<div class="content">
+<!-- Generator: GNU source-highlight 2.11.1
+by Lorenzo Bettini
+http://www.lorenzobettini.it
+http://www.gnu.org/software/src-highlite -->
+<pre><tt><span style="font-weight: bold"><span style="color: #0000FF">export</span></span> <span style="color: #009900">APXS2</span><span style="color: #990000">=</span>/usr/sbin/apxs<span style="color: #993399">2</span>
+ruby -e <span style="color: #FF0000">'p ENV["APXS2"]'</span>
+<span style="font-style: italic"><span style="color: #9A1900"># =&gt; "/usr/sbin/apxs2"</span></span></tt></pre>
+</div>
+</div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="./images/icons/note.png" alt="Note">
+</td>
+<td class="content">
+<div class="title">The "export" keyword is important</div>
+<div class="paragraph"><p>You <strong>must</strong> set the <span class="monospaced">export</span> keyword. If you omit the <span class="monospaced">export</span> keyword then the environment variable will not be visible to other processes:</p></div>
+<div class="listingblock">
+<div class="content">
+<!-- Generator: GNU source-highlight 2.11.1
+by Lorenzo Bettini
+http://www.lorenzobettini.it
+http://www.gnu.org/software/src-highlite -->
+<pre><tt><span style="color: #009900">APXS2</span><span style="color: #990000">=</span>/usr/sbin/apxs<span style="color: #993399">2</span>
+ruby -e <span style="color: #FF0000">'p ENV["APXS2"]'</span>
+<span style="font-style: italic"><span style="color: #9A1900"># =&gt; nil</span></span></tt></pre>
+</div>
+</div>
+</td>
+</tr></table>
+</div>
+<div class="paragraph"><p>You can reference an environment variable in your shell by typing the <span class="monospaced">$</span> sign followed by the environment variable’s name. For example, to see the value of the <span class="monospaced">PATH</span> variable:</p></div>
+<div class="listingblock">
+<div class="content">
+<!-- Generator: GNU source-highlight 2.11.1
+by Lorenzo Bettini
+http://www.lorenzobettini.it
+http://www.gnu.org/software/src-highlite -->
+<pre><tt>echo <span style="color: #009900">$PATH</span></tt></pre>
+</div>
+</div>
+<div class="paragraph"><p>You can also use this trick to extend the value of an environment variable:</p></div>
+<div class="listingblock">
+<div class="content">
+<!-- Generator: GNU source-highlight 2.11.1
+by Lorenzo Bettini
+http://www.lorenzobettini.it
+http://www.gnu.org/software/src-highlite -->
+<pre><tt><span style="font-weight: bold"><span style="color: #0000FF">export</span></span> <span style="color: #009900">PATH</span><span style="color: #990000">=</span>/usr/bin
+
+<span style="font-style: italic"><span style="color: #9A1900"># Prepends '/opt/local/bin', so that it becomes /opt/local/bin:/usr/bin</span></span>
+<span style="font-weight: bold"><span style="color: #0000FF">export</span></span> <span style="color: #009900">PATH</span><span style="color: #990000">=</span>/opt/local/bin<span style="color: #990000">:</span><span style="color: #009900">$PATH</span>
+<span style="font-style: italic"><span style="color: #9A1900"># Appends '/usr/local/bin', so that it becomes /opt/local/bin:/usr/bin:/usr/local/bin</span></span>
+<span style="font-weight: bold"><span style="color: #0000FF">export</span></span> <span style="color: #009900">PATH</span><span style="color: #990000">=</span><span style="color: #009900">$PATH</span><span style="color: #990000">:</span>/usr/local/bin</tt></pre>
+</div>
+</div>
+</div>
+<div class="sect2">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_the_path_environment_variable"></span><h3 data-comment-topic="the-path-environment-variable-p8e32r" data-anchor="_the_path_environment_variable">14.2. The PATH environment variable</h3>
+<div class="paragraph"><p>The <span class="monospaced">PATH</span> environment variable dictates where the system looks for command. It is a colon-separated list of directories. If you get a "command not found" error while you know that the command is installed, then setting <span class="monospaced">PATH</span> will help. For example suppose that the command <span class="monospaced">frobnicator</span> is in <span class="monospaced">/opt/local/bin</span>:</p></div>
+<div class="listingblock">
+<div class="content">
+<!-- Generator: GNU source-highlight 2.11.1
+by Lorenzo Bettini
+http://www.lorenzobettini.it
+http://www.gnu.org/software/src-highlite -->
+<pre><tt>user@localhost bash$ frobnicator
+bash<span style="color: #990000">:</span> frobnicator<span style="color: #990000">:</span> <span style="font-weight: bold"><span style="color: #0000FF">command</span></span> not found</tt></pre>
+</div>
+</div>
+<div class="paragraph"><p>We verify that <span class="monospaced">/opt/local/bin</span> is not in <span class="monospaced">PATH</span>:</p></div>
+<div class="listingblock">
+<div class="content">
+<!-- Generator: GNU source-highlight 2.11.1
+by Lorenzo Bettini
+http://www.lorenzobettini.it
+http://www.gnu.org/software/src-highlite -->
+<pre><tt>user@localhost bash$ echo <span style="color: #009900">$PATH</span>
+/bin<span style="color: #990000">:</span>/usr/bin<span style="color: #990000">:</span>/usr/local/bin</tt></pre>
+</div>
+</div>
+<div class="paragraph"><p>We can run <span class="monospaced">frobnicator</span> through it’s full path…</p></div>
+<div class="listingblock">
+<div class="content">
+<!-- Generator: GNU source-highlight 2.11.1
+by Lorenzo Bettini
+http://www.lorenzobettini.it
+http://www.gnu.org/software/src-highlite -->
+<pre><tt>user@localhost bash$ /opt/local/bin/frobnicator
+<span style="font-style: italic"><span style="color: #9A1900"># =&gt; success!</span></span></tt></pre>
+</div>
+</div>
+<div class="paragraph"><p>…or we can add <span class="monospaced">/opt/local/bin</span> to <span class="monospaced">PATH</span>.</p></div>
+<div class="listingblock">
+<div class="content">
+<!-- Generator: GNU source-highlight 2.11.1
+by Lorenzo Bettini
+http://www.lorenzobettini.it
+http://www.gnu.org/software/src-highlite -->
+<pre><tt>user@localhost bash$ <span style="font-weight: bold"><span style="color: #0000FF">export</span></span> <span style="color: #009900">PATH</span><span style="color: #990000">=</span><span style="color: #009900">$PATH</span><span style="color: #990000">:</span>/opt/local/bin
+user@localhost bash$ frobnicator
+<span style="font-style: italic"><span style="color: #9A1900"># =&gt; success!</span></span></tt></pre>
+</div>
+</div>
+</div>
+<div class="sect2">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_making_environment_variables_permanent"></span><h3 data-comment-topic="making-environment-variables-permanent-13x0l4h" data-anchor="_making_environment_variables_permanent">14.3. Making environment variables permanent</h3>
+<div class="paragraph"><p>When you exit your shell, the evironment variable changes are lost. There is no standard method to set environment variables system-wide, so you have to set them in different configuration files for different services.</p></div>
+<div class="sect3">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_bash"></span><h4 data-comment-topic="bash-1pktn63" data-anchor="_bash">14.3.1. bash</h4>
+<div class="paragraph"><p>To make environment variables permanent for future bash sessions <strong>for the current user</strong>, add them to your <span class="monospaced">~/.bashrc</span>:</p></div>
+<div class="listingblock">
+<div class="content">
+<!-- Generator: GNU source-highlight 2.11.1
+by Lorenzo Bettini
+http://www.lorenzobettini.it
+http://www.gnu.org/software/src-highlite -->
+<pre><tt>echo <span style="color: #FF0000">'export FOO=bar'</span> <span style="color: #990000">&gt;&gt;</span> <span style="color: #990000">~/.</span>bashrc
+echo <span style="color: #FF0000">'export PATH=/usr/local/bin:$PATH'</span> <span style="color: #990000">&gt;&gt;</span> <span style="color: #990000">~/.</span>bashrc</tt></pre>
+</div>
+</div>
+<div class="paragraph"><p>To make them permanent for future bash sessions <strong>for all users</strong>, add them to <span class="monospaced">/etc/bashrc</span>.</p></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="./images/icons/note.png" alt="Note">
+</td>
+<td class="content">Depending on the system, the bashrc file may have a different filename. On Debian and Ubuntu, it’s <span class="monospaced">/etc/bash.bashrc</span>.</td>
+</tr></table>
+</div>
+</div>
+<div class="sect3">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_apache"></span><h4 data-comment-topic="apache-15zqjvi" data-anchor="_apache">14.3.2. Apache</h4>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="./images/icons/note.png" alt="Note">
+</td>
+<td class="content">This subsection describes how to set environment variables on Apache itself, not on apps served through Phusion Passenger for Apache. The environment variables you set here will be passed to all apps, but you cannot customize them on a per-app basis. See also <a href="#env_vars_passenger_apps">Setting environment variables on Phusion Passenger-served apps</a>.</td>
+</tr></table>
+</div>
+<div class="paragraph"><p>On Debian and Ubuntu, with an Apache installed through apt, Apache environment variables are defined in the file <span class="monospaced">/etc/apache2/envvars</span>. This is a shell script so environment variables must be specified with the shell syntax.</p></div>
+<div class="paragraph"><p>On Red Hat, Fedora, CentOS and ScientificLinux, with an Apache installed through YUM, Apache environment variables are defined in <span class="monospaced">/etc/sysconfig/httpd</span>.</p></div>
+<div class="paragraph"><p>On OS X they are defined in <span class="monospaced">/System/Library/LaunchDaemons/org.apache.httpd.plist</span>, as explained <a href="/System/Library/LaunchDaemons/org.apache.httpd.plist">here on Stack Overflow</a>.</p></div>
+<div class="paragraph"><p>On other systems, or if you did not install Apache through the system’s package manager, the configuration file for environment variables is specific to the vendor that supplied Apache. There may not even be such a configuration file. You should contact the vendor for support.</p></div>
+</div>
+<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-l7ztbb" data-anchor="_nginx">14.3.3. Nginx</h4>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="./images/icons/note.png" alt="Note">
+</td>
+<td class="content">This subsection describes how to set environment variables on Nginx itself, not on apps served through Phusion Passenger for Nginx. The environment variables you set here will be passed to all apps, but you cannot customize them on a per-app basis. See also <a href="#env_vars_passenger_apps">Setting environment variables on Phusion Passenger-served apps</a>.</td>
+</tr></table>
+</div>
+<div class="paragraph"><p>If you installed Nginx through <a href="#install_on_debian_ubuntu">the 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
+the Nginx init script described in the <a href="http://www.modrails.com/documentation/Users%20guide%20Nginx.html">Phusion Passenger Users Guide, Nginx version</a>,
+then you should edit that script to define the environment variables. Those init scripts are regular shell scripts, so use the <span class="monospaced">export FOO=bar</span> syntax. Just make sure your set your environment variables before the script starts Nginx.</p></div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="./images/icons/note.png" alt="Note">
+</td>
+<td class="content">Setting environment variables on Nginx has no effect on the <a href="#flying_passenger">Flying Passenger daemon</a> because the daemon is started seperately. You should set the environment variables in the shell right before starting the daemon.</td>
+</tr></table>
+</div>
+</div>
+<div class="sect3">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_cron"></span><h4 data-comment-topic="cron-1kjp7ck" data-anchor="_cron">14.3.4. cron</h4>
+<div class="paragraph"><p>To make environment variables permanent for cron jobs, add those variables to the relevant crontab. But note that inside crontabs you cannot refer to existing environment variables with the <span class="monospaced">$</span> syntax because crontabs are not shell scripts. You have to specify the entire value.</p></div>
+<div class="listingblock">
+<div class="title">What to put in "crontab -e"</div>
+<div class="content monospaced">
+<pre># Environment variable definitions
+FOO=bar
+APXS2=/usr/sbin/apxs2
+
+# **WRONG!** You cannot refer to existing variables with the `$` syntax!
+PATH=/usr/bin:$PATH
+# **WRONG!** You cannot use the 'export' keyword!
+export PATH=/usr/bin:/usr/local/bin
+# Correct:
+PATH=/usr/bin:/usr/local/bin
+
+# Jobs:
+# m h  dom mon dow   command
+  * *  *   *   *     frobnicator</pre>
+</div>
+</div>
+</div>
+<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-478vyt" data-anchor="env_vars_passenger_apps">14.3.5. Phusion Passenger-served apps</h4>
+<div class="paragraph"><p>You can pass environment variables to Phusion Passenger-served apps through various methods:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+When running Apache, use the <span class="monospaced">PassEnv</span> and <span class="monospaced">SetEnv</span> directives of <a href="http://httpd.apache.org/docs/2.4/mod/mod_env.html">mod_env</a>. This is supported starting from Phusion Passenger 4.0.
+</p>
+</li>
+<li>
+<p>
+When running Nginx, use the <span class="monospaced">env</span> directive. Unlike Apache, Nginx’s <span class="monospaced">env</span> directive can only be set globally and cannot be customized on a per-virtual host basis.
+</p>
+</li>
+<li>
+<p>
+Through your <span class="monospaced">bashrc</span>. Starting from version 4.0, Phusion Passenger 4.0 spawns applications through bash and inherit all bash environment variables. Phusion Passenger Standalone tends to be started from the shell and thus inherits all environment variables set by the shell.
+</p>
+</li>
+<li>
+<p>
+Through Apache and Nginx, as described earlier in this chapter. Any environment variables that you set on Apache and Nginx itself are inherited by Phusion Passenger, and thus by Phusion Passenger-served apps as well.
+</p>
+</li>
+<li>
+<p>
+Through the application itself. Most programming languages provide APIs for setting environment variables. For example in Ruby you can write:
+</p>
+<div class="listingblock">
+<div class="content">
+<!-- Generator: GNU source-highlight 2.11.1
+by Lorenzo Bettini
+http://www.lorenzobettini.it
+http://www.gnu.org/software/src-highlite -->
+<pre><tt>ENV<span style="color: #990000">[</span><span style="color: #FF0000">'FOO'</span><span style="color: #990000">]</span> <span style="color: #990000">=</span> <span style="color: #FF0000">'bar'</span></tt></pre>
+</div>
+</div>
+<div class="paragraph"><p>In Python you can write:</p></div>
+<div class="listingblock">
+<div class="content">
+<!-- Generator: GNU source-highlight 2.11.1
+by Lorenzo Bettini
+http://www.lorenzobettini.it
+http://www.gnu.org/software/src-highlite -->
+<pre><tt><span style="font-weight: bold"><span style="color: #000080">import</span></span> os
+os<span style="color: #990000">.</span>environ<span style="color: #990000">[</span><span style="color: #FF0000">'FOO'</span><span style="color: #990000">]</span> <span style="color: #990000">=</span> <span style="color: #FF0000">'bar'</span></tt></pre>
+</div>
+</div>
+</li>
+</ul></div>
+</div>
+</div>
+<div class="sect2">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="env_vars_and_sudo"></span><h3 data-comment-topic="environment-variables-and-sudo-1odzcpz" data-anchor="env_vars_and_sudo">14.4. Environment variables and sudo</h3>
+<div class="paragraph"><p>The <span class="monospaced">sudo</span> command resets all environment variables before running the specified command, for security reasons. So if you set environment variables before running <span class="monospaced">sudo passenger-install-xxx-module</span>, <span class="monospaced">sudo passenger-status</span> or any other commands, then the environment variables are not correctly passed to the command. You can solve this by running sudo with <span class="monospaced">-E</span> (preserve environment variables):</p></div>
+<div class="listingblock">
+<div class="content">
+<!-- Generator: GNU source-highlight 2.11.1
+by Lorenzo Bettini
+http://www.lorenzobettini.it
+http://www.gnu.org/software/src-highlite -->
+<pre><tt>user@localhost bash$ <span style="font-weight: bold"><span style="color: #0000FF">export</span></span> <span style="color: #009900">APXS2</span><span style="color: #990000">=</span>/usr/sbin/apxs<span style="color: #993399">2</span>
+user@localhost bash$ sudo -E passenger-install-apache<span style="color: #993399">2</span>-module</tt></pre>
+</div>
+</div>
+<div class="paragraph"><p>Alternatively, you can obtain a root prompt with sudo first, and <strong>then</strong> set the environment variables, before running any further commands:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>user@localhost bash$ sudo -s
+Password: ...
+root@localhost bash# export APXS2=/usr/sbin/apxs2
+root@localhost bash# passenger-install-apache2-module</pre>
+</div>
+</div>
+</div>
+</div>
+</div>
 </div>
 <div id="footnotes"><hr></div>
 <div id="footer">