passenger 2.2.2 → 2.2.3

data/doc/Users guide Apache.html

@@ -470,80 +470,21 @@ using the commandline.</p></div>
 <div class="sectionbody">
 <div class="paragraph"><p>Phusion Passenger works on any POSIX-compliant operating system. In other
 words: practically any operating system on earth, except Microsoft Windows.</p></div>
-<div class="paragraph"><p>Phusion Passenger has been tested on:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Ubuntu Linux 6.06 (x86)
-</p>
-</li>
-<li>
-<p>
-Ubuntu Linux 7.10 (x86)
-</p>
-</li>
-<li>
-<p>
-Ubuntu Linux 8.04 (x86)
-</p>
-</li>
-<li>
-<p>
-Debian Sarge (x86)
-</p>
-</li>
-<li>
-<p>
-Debian Etch (x86)
-</p>
-</li>
-<li>
-<p>
-Debian Lenny/Sid (x86)
-</p>
-</li>
-<li>
-<p>
-CentOS 5 (x86)
-</p>
-</li>
-<li>
-<p>
-Red Hat Enterprise Linux 5 (x86)
-</p>
-</li>
-<li>
-<p>
-Gentoo, March 14 2008 (AMD64)
-</p>
-</li>
-<li>
-<p>
-FreeBSD 6.1-RELEASE (x86)
-</p>
-</li>
-<li>
-<p>
-MacOS X Tiger (x86)
-</p>
-</li>
-<li>
-<p>
-MacOS X Leopard (x86)
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Other operating systems have not been tested, but Phusion Passenger will probably
-work fine on them. Please
+<div class="paragraph"><p>Phusion Passenger is confirmed on a large number of operating systems and Linux
+distributions, including, but not limited to, Ubuntu, Debian, CentOS/Fedora/RHEL,
+Gentoo, Mac OS X, FreeBSD and Solaris. Both 32-bit and 64-bit platforms are supported.</p></div>
+<div class="paragraph"><p>The only POSIX-compliant operating system on which Phusion Passenger for Apache is
+known not to work at this time, is OpenBSD. Please use Phusion Passenger for Nginx
+instead.</p></div>
+<div class="paragraph"><p>If Phusion Passenger does not work on your platform then please
 <a href="http://code.google.com/p/phusion-passenger/issues/list">report a bug</a>
 or
-<a href="http://groups.google.com/group/phusion-passenger">join our discussion list</a>
-if it doesn&#8217;t.</p></div>
+<a href="http://groups.google.com/group/phusion-passenger">join our discussion list</a>.</p></div>
 </div>
-<h2 id="_installing_phusion_passenger">2. Installing Phusion Passenger</h2>
+<h2 id="_installing_upgrading_and_uninstalling_phusion_passenger">2. Installing, upgrading and uninstalling Phusion Passenger</h2>
 <div class="sectionbody">
 <h3 id="_generic_installation_instructions">2.1. Generic installation instructions</h3>
-<h4 id="install_passenger">2.1.1. Overview of download and installation methods</h4>
+<h4 id="install_passenger">2.1.1. Overview of installation methods</h4>
 <div class="paragraph"><p>There are three ways to install Phusion Passenger:</p></div>
 <div class="olist arabic"><ol class="arabic">
 <li>
@@ -561,41 +502,62 @@ By downloading the source tarball from the Phusion Passenger website
 </li>
 <li>
 <p>
-By downloading a native Linux package (e.g. Debian package) from the
-   Phusion Passenger website.
+By installing a native Linux package (e.g. Debian package).
 </p>
 </li>
 </ol></div>
-<div class="paragraph"><p>In our opinion, installing the gem or the native package is easiest.</p></div>
-<div class="paragraph"><p>Phusion Passenger provides an easy-to-use installer for installing the Phusion
-Passenger Apache module, in case you choose to install via the gem or the
-source tarball.</p></div>
-<div class="admonitionblock">
-<table><tr>
-<td class="icon">
-<img src="./images/icons/tip.png" alt="Tip" />
-</td>
-<td class="content">You might have to run the installation commands in the following sections
-as <em>root</em>. If the installer fails because of permission errors, it will tell
-you.</td>
-</tr></table>
-</div>
-<h4 id="_preparation">2.1.2. Preparation</h4>
+<div class="paragraph"><p>The following sections will explain each installation method. Please read the
+section for the installation method that you prefer. In our opinion, installing
+the gem or the native package is easiest. For these two installation methods,
+Phusion Passenger provides an easy-to-use installer.</p></div>
+<h4 id="_preparation_gem_and_source_tarball_only">2.1.2. Preparation (gem and source tarball only)</h4>
 <div class="paragraph"><p>If you want to install Phusion Passenger via the gem or the source tarball,
-then some preparation might be required. You can skip this subsection if
+then some preparations might be required. You can skip this subsection if
 you&#8217;re installing Phusion Passenger via a native Linux package, because no
 compilation is necessary.</p></div>
+<h5 id="_switching_to_a_root_command_prompt">Switching to a root command prompt</h5>
+<div class="paragraph"><p>Before installing, you will probably need to switch to the <tt>root</tt> user first.
+When you install Phusion Passenger via a gem or a source tarball, some Phusion
+Passenger files have to be compiled, which requires write access to the
+directory in which the Phusion Passenger files are located. On Unix systems,
+the root user is the user who has write access to the entire system. So unless
+you know that your normal user account has write access to the Phusion Passenger
+directory, you should switch to root before installing Phusion Passenger.</p></div>
+<div class="paragraph"><p>You can switch to root by typing the following command:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><tt>sudo -s</tt></pre>
+</div></div>
+<div class="paragraph"><p>This will open a command prompt as the root user, from which you can proceed
+with installing Phusion Passenger.</p></div>
+<div class="paragraph"><p>If your system does not have <em>sudo</em> installed, please type the following command instead, which should do the same thing:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><tt>su</tt></pre>
+</div></div>
 <h5 id="specifying_correct_apache_install">Specifying the correct Apache installation</h5>
-<div class="paragraph"><p>If your system has multiple Apache installations (this is likely the case on
-MacOS X), then you will need to tell the Phusion Passenger installer which one
-to use. If you only have one Apache installation (the case on most Linux
-systems), then you can skip this section because Phusion Passenger will
-automatically detect it.</p></div>
-<div class="paragraph"><p>Every Apache installation has its own <tt>apxs</tt> program. You will need to tell
-Phusion Passenger the location of this program, by specifying the <tt>APXS2</tt>
-environment variable. Suppose that you want to use the Apache installation in
-<em>/opt/apache2</em>. Then, assuming that the corresponding <tt>apxs</tt> program is located
-<em>/opt/apache2/bin/apxs</em>, type:</p></div>
+<div class="paragraph"><p>The Phusion Passenger installer will attempt to automatically detect Apache,
+and compile Phusion Passenger against that Apache version. It does this by
+looking for the <tt>apxs</tt> or <tt>apxs2</tt> command in the PATH environment variable.
+Apxs is an integral part of any Apache installation.</p></div>
+<div class="paragraph"><p>However, some systems have multiple Apache installations. This is likely
+the case on MacOS X: the OS ships with Apache, but users tend to install
+another Apache version seperately, e.g. via MacPorts. If your system has
+multiple Apache installations, then you will need to tell the Phusion Passenger
+installer which one to use. It is very important that you specify the
+correct Apache installation, because if you load Phusion Passenger in an
+Apache installation that it wasn&#8217;t compiled against, then it will likely
+crash.</p></div>
+<div class="paragraph"><p>On yet other systems, Apache is installed in a non-standard location,
+preventing the Phusion Passenger installer from detecting Apache. This
+is most likely the case on systems on which Apache was installed by hand
+from source, i.e. as opposed to installed through the system&#8217;s native
+package manager. If this is the case, then you will also have to tell
+the installer where it can find Apache.</p></div>
+<div class="paragraph"><p>To do so, set the <tt>APXS2</tt> environment variable to the full path of the
+correct <tt>apxs</tt> or <tt>apxs2</tt> command. Suppose that you want to use the Apache
+installation in <em>/opt/apache2</em>. Then, assuming that the corresponding
+<tt>apxs</tt> program&#8217;s path is <em>/opt/apache2/bin/apxs</em>, type:</p></div>
 <div class="listingblock">
 <div class="content">
 <pre><tt>export APXS2=/opt/apache2/bin/apxs</tt></pre>
@@ -609,6 +571,20 @@ environment variable. Suppose that you want to use the Apache installation in
 be located in the <tt>sbin</tt> folder instead of the <tt>bin</tt> folder.</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="title">Environment variables and <em>sudo</em></div>By default, the <em>sudo</em> command will erase any environment variables that it
+doesn&#8217;t recognize, prior to executing the given command. So if you set APXS2 as a
+normal user, then run <tt>sudo passenger-install-apache2-module</tt> (which is the command
+for the Phusion Passenger installer), then the installer will not receive the
+environment variable value that you set. To solve this problem, please become root
+prior to setting any environment variables, as described in the previous subsection.</td>
+</tr></table>
+</div>
 <h5 id="specifying_ruby_installation">Specifying the correct Ruby installation</h5>
 <div class="paragraph"><p>If your system has multiple Ruby installations&#8201;&#8212;&#8201;which is likely the case on
 MacOS X, or if you&#8217;ve also installed
@@ -680,6 +656,14 @@ sudo sh -c 'wget -q -O - http://apt.brightbox.net/release.asc | apt-key add -'
 sudo apt-get update
 sudo apt-get install libapache2-mod-passenger</tt></pre>
 </div></div>
+<h4 id="_what_does_the_installer_do">2.1.6. What does the installer do?</h4>
+<div class="paragraph"><p>Although we call it an &#8220;installer&#8221;, it doesn&#8217;t actually install anything.
+The installer checks whether all required dependencies are installed,
+compiles Phusion Passenger for you, and tells you how to modify the Apache
+configuration file, but it doesn&#8217;t copy any files around.</p></div>
+<div class="paragraph"><p><tt>passenger-install-apache2-module</tt> is actually just a user-friendly frontend
+around the command <tt>rake apache2</tt>, which performs the actual compilation of
+Phusion Passenger.</p></div>
 <h3 id="_operating_system_specific_instructions_and_information">2.2. Operating system-specific instructions and information</h3>
 <h4 id="_macos_x">2.2.1. MacOS X</h4>
 <div class="paragraph"><p>Ben Ruebenstein has written an excellent
@@ -690,6 +674,111 @@ on installing Phusion Passenger on OS X</a>.</p></div>
 <h4 id="_opensolaris">2.2.3. OpenSolaris</h4>
 <div class="paragraph"><p>J Aaron Farr has written a <a href="http://cubiclemuses.com/cm/articles/2009/04/09/rails-passenger-open-solaris-ec2/">guide</a>
 about setting up Ruby on Rails and Phusion Passenger on OpenSolaris and EC2.</p></div>
+<h3 id="_upgrading_or_downgrading_phusion_passenger">2.3. Upgrading or downgrading Phusion Passenger</h3>
+<h4 id="_via_a_gem_or_a_source_tarball">2.3.1. Via a gem or a source tarball</h4>
+<div class="paragraph"><p>To ugrade or downgrade Phusion Passenger via the gem or the source tarball, install the newer
+or older version as you normally would; that is, install the gem or unpack the tarball, and
+run <tt>passenger-install-apache2-module</tt>. Eventually <tt>passenger-install-apache2-module</tt> will tell
+you to copy &amp; paste some settings into the Apache configuration file; something that looks along
+the lines of:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><tt>LoadModule passenger_module ...
+PassengerRoot ...
+PassengerRuby ...</tt></pre>
+</div></div>
+<div class="paragraph"><p>Because you already have Phusion Passenger installed, you already have the same settings
+in your Apache configuration file, just with different values. Replace the old settings with
+the new ones that the installer outputs.</p></div>
+<div class="paragraph"><p>When you&#8217;re done, restart Apache.</p></div>
+<h4 id="_via_a_native_linux_package">2.3.2. Via a native Linux package</h4>
+<div class="paragraph"><p>There are no special instructions required to upgrade or downgrade Phusion Passenger
+via a native Linux package.</p></div>
+<h3 id="_unloading_disabling_phusion_passenger_from_apache_without_uninstalling_it">2.4. Unloading (disabling) Phusion Passenger from Apache without uninstalling it</h3>
+<div class="paragraph"><p>You can temporarily unload (disable) Phusion Passenger from Apache, without
+uninstalling the Phusion Passenger files, so that Apache behaves as if Phusion
+Passenger was never installed in the first place. This might be useful to you if,
+for example, you seem to be experiencing a problem caused by Phusion Passenger,
+but you want to make sure whether that&#8217;s actually the case, without having
+to through the hassle of uninstalling Phusion Passenger completely.</p></div>
+<div class="paragraph"><p>To unload Phusion Passenger from Apache, edit your Apache configuration file(s)
+and comment out:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+all Phusion Passenger configuration directives.
+</p>
+</li>
+<li>
+<p>
+the <em>LoadModule passenger_module</em> directive.
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>For example, if your configuration file looks like this&#8230;</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><tt>Listen *:80
+NameVirtualHosts *:80
+....
+
+LoadModule passenger_module /somewhere/passenger-x.x.x/ext/apache2/mod_passenger.so
+
+PassengerRuby /usr/bin/ruby
+PassengerRoot /somewhere/passenger/x.x.x
+PassengerMaxPoolSize 10
+
+&lt;VirtualHost *:80&gt;
+    ServerName www.foo.com
+    DocumentRoot /webapps/foo/public
+    RailsBaseURI /rails
+&lt;/VirtualHost&gt;</tt></pre>
+</div></div>
+<div class="paragraph"><p>&#8230;then comment out the relevant directives, so that it looks like this:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><tt>Listen *:80
+NameVirtualHosts *:80
+....
+
+# LoadModule passenger_module /somewhere/passenger-x.x.x/ext/apache2/mod_passenger.so
+
+# PassengerRuby /usr/bin/ruby
+# PassengerRoot /somewhere/passenger/x.x.x
+# PassengerMaxPoolSize 10
+
+&lt;VirtualHost *:80&gt;
+    ServerName www.foo.com
+    DocumentRoot /webapps/foo/public
+    # RailsBaseURI /rails
+&lt;/VirtualHost&gt;</tt></pre>
+</div></div>
+<div class="paragraph"><p>After you&#8217;ve done this, save the file and restart Apache.</p></div>
+<h3 id="_uninstalling_phusion_passenger">2.5. Uninstalling Phusion Passenger</h3>
+<div class="paragraph"><p>To uninstall Phusion Passenger, please first remove all Phusion Passenger
+configuration directives from your Apache configuration file(s). After you&#8217;ve
+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 gem, then type <tt>gem uninstall passenger</tt>.
+  You might have to run this as root.
+</p>
+</li>
+<li>
+<p>
+If you installed Phusion Passenger via a source tarball, then remove the directory
+  in which you placed the extracted Phusion Passenger files. This directory is the
+  same as the one pointed to the by <em>PassengerRoot</em> configuration directive.
+</p>
+</li>
+<li>
+<p>
+If you installed Phusion Passenger via a Debian package, then remove type
+  <tt>sudo apt-get remove libapache2-mod-passenger</tt>.
+</p>
+</li>
+</ul></div>
 </div>
 <h2 id="_deploying_a_ruby_on_rails_application">3. Deploying a Ruby on Rails application</h2>
 <div class="sectionbody">
@@ -793,7 +882,7 @@ By restarting Apache.
 <p>
 By creating or modifying the file <em>tmp/restart.txt</em> in the Rails
    application&#8217;s <a href="#application_root">root folder</a>. Phusion Passenger will
-   automatically restart the application.
+   automatically restart the application during the next request.
 </p>
 </li>
 </ol></div>
@@ -803,6 +892,10 @@ command line:</p></div>
 <div class="content">
 <pre><tt>touch /webapps/mycook/tmp/restart.txt</tt></pre>
 </div></div>
+<div class="paragraph"><p>Please note that, unlike earlier versions of Phusion Passenger, <em>restart.txt</em>
+is not automatically deleted. Phusion Passenger checks whether the timestamp
+of this file has changed in order to determine whether the application should
+be restarted.</p></div>
 <h3 id="_migrations">3.4. Migrations</h3>
 <div class="paragraph"><p>Phusion Passenger is not related to Ruby on Rails migrations in any way. To
 run migrations on your deployment server, please login to your deployment
@@ -878,7 +971,7 @@ $ some_awesome_editor config.ru
 ...type in some source code...
 $ cat config.ru
 app = proc do |env|
-    return [200, { "Content-Type" =&gt; "text/html" }, "hello &lt;b&gt;world&lt;/b&gt;"]
+    [200, { "Content-Type" =&gt; "text/html" }, ["hello &lt;b&gt;world&lt;/b&gt;"]]
 end
 run app</tt></pre>
 </div></div>
@@ -1019,7 +1112,7 @@ run Mack::Utils::Server.build_app</tt></pre>
 require 'merb-core'
 
 Merb::Config.setup(
-  :merb_root   =&gt; File.expand_path(File.dirname(__FILE__)),
+  :merb_root   =&gt; ::File.expand_path(::File.dirname(__FILE__)),
   :environment =&gt; ENV['RACK_ENV']
 )
 Merb.environment = Merb::Config[:environment]
@@ -1043,13 +1136,7 @@ run Ramaze::Adapter::Base</tt></pre>
 <div class="content">
 <pre><tt>require 'rubygems'
 require 'sinatra'
-
-root_dir = File.dirname(__FILE__)
-
-set :environment, ENV['RACK_ENV'].to_sym
-set :root,        root_dir
-set :app_file,    File.join(root_dir, 'app.rb')
-disable :run
+require 'app.rb'
 
 run Sinatra::Application</tt></pre>
 </div></div>
@@ -1330,10 +1417,10 @@ follows:</p></div>
 <pre><tt>&lt;VirtualHost *:80&gt;
     ServerName www.foo.com
     DocumentRoot /apps/foo/public
-    &lt;Location /wordpress&gt;
+    &lt;Directory /apps/foo/public/wordpress&gt;
         PassengerEnabled off
         AllowOverride all      # &lt;-- Makes Wordpress's .htaccess file work.
-    &lt;/Location&gt;
+    &lt;/Directory&gt;
 &lt;/VirtualHost&gt;</tt></pre>
 </div></div>
 <div class="paragraph"><p>This way, Phusion Passenger will not interfere with Wordpress.</p></div>
@@ -1361,10 +1448,10 @@ In <em>.htaccess</em>.
 </li>
 </ul></div>
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>on</em>.</p></div>
-<h3 id="_passengertempdir_lt_directory_gt">5.10. PassengerTempDir &lt;directory&gt;</h3>
+<h3 id="PassengerTempDir">5.10. PassengerTempDir &lt;directory&gt;</h3>
 <div class="paragraph"><p>Specifies the directory that Phusion Passenger should use for storing temporary
-files. This includes things such as Unix socket files, buffered file uploads,
-etc.</p></div>
+files. This includes things such as Unix socket files, buffered file uploads
+(see also <a href="#PassengerUploadBufferDir">PassengerUploadBufferDir</a>), etc.</p></div>
 <div class="paragraph"><p>This option may be specified once, in the global server configuration. The
 default temp directory that Phusion Passenger uses is <em>/tmp</em>.</p></div>
 <div class="paragraph"><p>This option is especially useful if Apache is not allowed to write to /tmp
@@ -1384,7 +1471,48 @@ environment variable, like this:</p></div>
 sudo -E passenger-status
 # The -E option tells 'sudo' to preserve environment variables.</tt></pre>
 </div></div>
-<h3 id="_passengerrestartdir_lt_directory_gt">5.11. PassengerRestartDir &lt;directory&gt;</h3>
+<h3 id="PassengerUploadBufferDir">5.11. PassengerUploadBufferDir &lt;directory&gt;</h3>
+<div class="paragraph"><p>Phusion Passenger buffers large file uploads to disk in order prevent slow file
+uploads from blocking web applications. By default, a subdirectory in the
+system&#8217;s temporary files directory (or a subdirectory in the directory specified
+in <a href="#PassengerTempDir">PassengerTempDir</a>, if set) is automatically created for
+storing these buffered file uploads.</p></div>
+<div class="paragraph"><p>This configuration directive allows you to specify a different directory for storing
+buffered file uploads. If you&#8217;ve specified such a directory (as opposed to using
+Phusion Passenger&#8217;s default) then you <strong>must</strong> ensure that this directory exists.</p></div>
+<div class="paragraph"><p>This configuration directive is also useful if you&#8217;re using apache2-mpm-itk.
+The buffered file upload directory that Phusion Passenger creates by default has
+very strict permissions: it can only be accessed by the Apache worker processes.
+However, Phusion Passenger assumes that all Apache worker processes are running
+as the same user. apache2-mpm-itk breaks this assumption by running multiple
+Apache worker processes as different users. So if you&#8217;re using apace2-mpm-itk,
+you should set this option to a directory that is writable by all Apache worker
+processes, such as <em>/tmp</em>.</p></div>
+<div class="paragraph"><p>You may specify <em>PassengerUploadBufferDir</em> in the following places:</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+In the global server configuration.
+</p>
+</li>
+<li>
+<p>
+In a virtual host configuration block.
+</p>
+</li>
+<li>
+<p>
+In a <tt>&lt;Directory&gt;</tt> or <tt>&lt;Location&gt;</tt> block.
+</p>
+</li>
+<li>
+<p>
+In <em>.htaccess</em>, if <tt>AllowOverrides Options</tt> is enabled.
+</p>
+</li>
+</ul></div>
+<div class="paragraph"><p>In each place, it may be specified at most once.</p></div>
+<h3 id="_passengerrestartdir_lt_directory_gt">5.12. PassengerRestartDir &lt;directory&gt;</h3>
 <div class="paragraph"><p>As described in the deployment chapters of this document, Phusion Passenger
 checks the file <em>tmp/restart.txt</em> in the applications'
 <a href="#application_root">root directory</a> for restarting applications. Sometimes it
@@ -1452,8 +1580,8 @@ security flaw which allows an attacker to touch restart.txt, then that will
 allow the attacker to cause a Denial-of-Service.</p></div>
 <div class="paragraph"><p>You can prevent this from happening by pointing PassengerRestartDir to a
 directory that&#8217;s readable by Apache, but only writable by administrators.</p></div>
-<h3 id="_resource_control_and_optimization_options">5.12. Resource control and optimization options</h3>
-<h4 id="_passengermaxpoolsize_lt_integer_gt">5.12.1. PassengerMaxPoolSize &lt;integer&gt;</h4>
+<h3 id="_resource_control_and_optimization_options">5.13. Resource control and optimization options</h3>
+<h4 id="_passengermaxpoolsize_lt_integer_gt">5.13.1. PassengerMaxPoolSize &lt;integer&gt;</h4>
 <div class="paragraph"><p>The maximum number of Ruby on Rails or Rack application instances that may
 be simultaneously active. A larger number results in higher memory usage,
 but improved ability to handle concurrent HTTP clients.</p></div>
@@ -1478,7 +1606,7 @@ The default value is <em>6</em>.</p></div>
 by about 33%. And it&#8217;s not hard to install.</td>
 </tr></table>
 </div>
-<h4 id="_passengermaxinstancesperapp_lt_integer_gt">5.12.2. PassengerMaxInstancesPerApp &lt;integer&gt;</h4>
+<h4 id="_passengermaxinstancesperapp_lt_integer_gt">5.13.2. PassengerMaxInstancesPerApp &lt;integer&gt;</h4>
 <div class="paragraph"><p>The maximum number of application instances that may be simultaneously active
 for a single application. This helps to make sure that a single application
 will not occupy all available slots in the application pool.</p></div>
@@ -1488,7 +1616,7 @@ may use, i.e. only the global limit of <a href="#PassengerMaxPoolSize">Passenger
 will be enforced.</p></div>
 <div class="paragraph"><p>This option may only occur once, in the global server configuration.
 The default value is <em>0</em>.</p></div>
-<h4 id="PassengerPoolIdleTime">5.12.3. PassengerPoolIdleTime &lt;integer&gt;</h4>
+<h4 id="PassengerPoolIdleTime">5.13.3. PassengerPoolIdleTime &lt;integer&gt;</h4>
 <div class="paragraph"><p>The maximum number of seconds that an application instance may be idle. That is,
 if an application instance hasn&#8217;t received any traffic after the given number of
 seconds, then it will be shutdown in order to conserve memory.</p></div>
@@ -1508,7 +1636,7 @@ recommended if you&#8217;re on a non-shared host that&#8217;s only running a few
 applications, each which must be available at all times.</p></div>
 <div class="paragraph"><p>This option may only occur once, in the global server configuration.
 The default value is <em>300</em>.</p></div>
-<h4 id="PassengerMaxRequests">5.12.4. PassengerMaxRequests &lt;integer&gt;</h4>
+<h4 id="PassengerMaxRequests">5.13.4. PassengerMaxRequests &lt;integer&gt;</h4>
 <div class="paragraph"><p>The maximum number of requests an application instance will process. After
 serving that many requests, the application instance will be shut down and
 Phusion Passenger will restart it. A value of 0 means that there is no maximum:
@@ -1554,7 +1682,7 @@ measure to avoid memory leaks.</p></div>
 </td>
 </tr></table>
 </div>
-<h4 id="_passengerstatthrottlerate_lt_integer_gt">5.12.5. PassengerStatThrottleRate &lt;integer&gt;</h4>
+<h4 id="_passengerstatthrottlerate_lt_integer_gt">5.13.5. PassengerStatThrottleRate &lt;integer&gt;</h4>
 <div class="paragraph"><p>By default, Phusion Passenger performs several filesystem checks (or, in
 programmers jargon, <em>stat() calls</em>) each time a request is processed:</p></div>
 <div class="ulist"><ul>
@@ -1604,8 +1732,8 @@ In <em>.htaccess</em>, if <tt>AllowOverride Limits</tt> is on.
 </li>
 </ul></div>
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>0</em>.</p></div>
-<h3 id="_ruby_on_rails_specific_options">5.13. Ruby on Rails-specific options</h3>
-<h4 id="_railsautodetect_lt_on_off_gt">5.13.1. RailsAutoDetect &lt;on|off&gt;</h4>
+<h3 id="_ruby_on_rails_specific_options">5.14. Ruby on Rails-specific options</h3>
+<h4 id="_railsautodetect_lt_on_off_gt">5.14.1. RailsAutoDetect &lt;on|off&gt;</h4>
 <div class="paragraph"><p>Whether Phusion Passenger should automatically detect whether a virtual host&#8217;s
 document root is a Ruby on Rails application. The default is <em>on</em>.</p></div>
 <div class="paragraph"><p>This option may occur in the global server configuration or in a virtual host
@@ -1633,7 +1761,7 @@ application by using the <a href="#RailsBaseURI">RailsBaseURI</a> configuration
     RailsBaseURI /           # This line has been added.
 &lt;/VirtualHost&gt;</tt></pre>
 </div></div>
-<h4 id="RailsBaseURI">5.13.2. RailsBaseURI &lt;uri&gt;</h4>
+<h4 id="RailsBaseURI">5.14.2. RailsBaseURI &lt;uri&gt;</h4>
 <div class="paragraph"><p>Used to specify that the given URI is a Rails application. See
 <a href="#deploying_rails_to_sub_uri">Deploying Rails to a sub URI</a> for an example.</p></div>
 <div class="paragraph"><p>It is allowed to specify this option multiple times. Do this to deploy multiple
@@ -1661,7 +1789,7 @@ In <em>.htaccess</em>, if <tt>AllowOverride Options</tt> is on.
 </p>
 </li>
 </ul></div>
-<h4 id="rails_env">5.13.3. RailsEnv &lt;string&gt;</h4>
+<h4 id="rails_env">5.14.3. RailsEnv &lt;string&gt;</h4>
 <div class="paragraph"><p>This option allows one to specify the default <tt>RAILS_ENV</tt> value.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
 <div class="ulist"><ul>
@@ -1687,7 +1815,7 @@ In <em>.htaccess</em>, if <tt>AllowOverride Options</tt> is on.
 </li>
 </ul></div>
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>production</em>.</p></div>
-<h4 id="RailsSpawnMethod">5.13.4. RailsSpawnMethod &lt;string&gt;</h4>
+<h4 id="RailsSpawnMethod">5.14.4. RailsSpawnMethod &lt;string&gt;</h4>
 <div class="admonitionblock">
 <table><tr>
 <td class="icon">
@@ -1780,7 +1908,7 @@ In a virtual host configuration block.
 </li>
 </ul></div>
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>smart-lv2</em>.</p></div>
-<h4 id="_railsframeworkspawneridletime_lt_integer_gt">5.13.5. RailsFrameworkSpawnerIdleTime &lt;integer&gt;</h4>
+<h4 id="_railsframeworkspawneridletime_lt_integer_gt">5.14.5. RailsFrameworkSpawnerIdleTime &lt;integer&gt;</h4>
 <div class="paragraph"><p>The FrameworkSpawner server (explained in <a href="#spawning_methods_explained">Spawning methods explained</a>) has an idle timeout, just like the backend processes spawned by
 Phusion Passenger do. That is, it will automatically shutdown if it hasn&#8217;t done
 anything for a given period.</p></div>
@@ -1807,7 +1935,7 @@ In a virtual host configuration block.
 </li>
 </ul></div>
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>1800</em> (30 minutes).</p></div>
-<h4 id="_railsappspawneridletime_lt_integer_gt">5.13.6. RailsAppSpawnerIdleTime &lt;integer&gt;</h4>
+<h4 id="_railsappspawneridletime_lt_integer_gt">5.14.6. RailsAppSpawnerIdleTime &lt;integer&gt;</h4>
 <div class="paragraph"><p>The ApplicationSpawner server (explained in <a href="#spawning_methods_explained">Spawning methods explained</a>) has an idle timeout, just like the backend processes spawned by
 Phusion Passenger do. That is, it will automatically shutdown if it hasn&#8217;t done
 anything for a given period.</p></div>
@@ -1834,8 +1962,8 @@ In a virtual host configuration block.
 </li>
 </ul></div>
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>600</em> (10 minutes).</p></div>
-<h3 id="_rack_specific_options">5.14. Rack-specific options</h3>
-<h4 id="_rackautodetect_lt_on_off_gt">5.14.1. RackAutoDetect &lt;on|off&gt;</h4>
+<h3 id="_rack_specific_options">5.15. Rack-specific options</h3>
+<h4 id="_rackautodetect_lt_on_off_gt">5.15.1. RackAutoDetect &lt;on|off&gt;</h4>
 <div class="paragraph"><p>Whether Phusion Passenger should automatically detect whether a virtual host&#8217;s
 document root is a Rack application. The default is <em>on</em>.</p></div>
 <div class="paragraph"><p>This option may occur in the global server configuration or in a virtual host
@@ -1863,7 +1991,7 @@ application by using the <a href="#RackBaseURI">RackBaseURI</a> configuration op
     RackBaseURI /       # This line was added
 &lt;/VirtualHost&gt;</tt></pre>
 </div></div>
-<h4 id="RackBaseURI">5.14.2. RackBaseURI &lt;uri&gt;</h4>
+<h4 id="RackBaseURI">5.15.2. RackBaseURI &lt;uri&gt;</h4>
 <div class="paragraph"><p>Used to specify that the given URI is a Rack application. See
 <a href="#deploying_rack_to_sub_uri">Deploying Rack to a sub URI</a> for an example.</p></div>
 <div class="paragraph"><p>It is allowed to specify this option multiple times. Do this to deploy multiple
@@ -1891,7 +2019,7 @@ In <em>.htaccess</em>, if <tt>AllowOverride Options</tt> is on.
 </p>
 </li>
 </ul></div>
-<h4 id="rack_env">5.14.3. RackEnv &lt;string&gt;</h4>
+<h4 id="rack_env">5.15.3. RackEnv &lt;string&gt;</h4>
 <div class="paragraph"><p>The given value will be accessible in Rack applications in the <tt>RACK_ENV</tt>
 environment variable. This allows one to define the environment in which
 Rack applications are run, very similar to <tt>RAILS_ENV</tt>.</p></div>
@@ -1919,16 +2047,16 @@ In <em>.htaccess</em>, if <tt>AllowOverride Options</tt> is on.
 </li>
 </ul></div>
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>production</em>.</p></div>
-<h3 id="_deprecated_options">5.15. Deprecated options</h3>
+<h3 id="_deprecated_options">5.16. Deprecated options</h3>
 <div class="paragraph"><p>The following options have been deprecated, but are still supported for backwards
 compatibility reasons.</p></div>
-<h4 id="_railsruby">5.15.1. RailsRuby</h4>
+<h4 id="_railsruby">5.16.1. RailsRuby</h4>
 <div class="paragraph"><p>Deprecated in favor of <a href="#PassengerRuby">PassengerRuby</a>.</p></div>
-<h4 id="_railsuserswitching">5.15.2. RailsUserSwitching</h4>
+<h4 id="_railsuserswitching">5.16.2. RailsUserSwitching</h4>
 <div class="paragraph"><p>Deprecated in favor of <a href="#PassengerUserSwitching">PassengerUserSwitching</a>.</p></div>
-<h4 id="_railsdefaultuser">5.15.3. RailsDefaultUser</h4>
+<h4 id="_railsdefaultuser">5.16.3. RailsDefaultUser</h4>
 <div class="paragraph"><p>Deprecated in favor of <a href="#PassengerDefaultUser">PassengerDefaultUser</a>.</p></div>
-<h4 id="_railsallowmodrewrite">5.15.4. RailsAllowModRewrite</h4>
+<h4 id="_railsallowmodrewrite">5.16.4. RailsAllowModRewrite</h4>
 <div class="paragraph"><p>This option doesn&#8217;t do anything anymore in recent versions of Phusion Passenger.</p></div>
 </div>
 <h2 id="_troubleshooting">6. Troubleshooting</h2>
@@ -2742,7 +2870,104 @@ please refer to
 try drogus&#8217;s <a href="http://github.com/drogus/apache-upload-progress-module/tree/master">
 Apache upload progress module</a> instead.</p></div>
 </div>
-<h2 id="_appendix_a_about_this_document">9. Appendix A: About this document</h2>
+<h2 id="_under_the_hood">9. Under the hood</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>Phusion Passenger hides a lot of complexity for the end user (i.e. the web server
+system administrator), but sometimes it is desirable to know what is going on.
+This section describes a few things that Phusion Passenger does under the hood.</p></div>
+<h3 id="_static_assets_serving">9.1. Static assets serving</h3>
+<div class="paragraph"><p>Phusion Passenger accelerates serving of static files. This means that, if an URI
+maps to a file that exists, then Phusion Passenger will let Apache serve that file
+directly, without hitting the web application.</p></div>
+<div class="paragraph"><p>Phusion Passenger does all this without the need for any mod_rewrite rules. People
+who are switching from an old Mongrel-based setup might have mod_rewrite rules such
+as these:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><tt># Check whether this request has a corresponding file; if that
+# exists, let Apache serve it, otherwise forward the request to
+# Mongrel.
+RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f
+RewriteRule ^(.*)$ balancer://mongrel%{REQUEST_URI} [P,QSA,L]</tt></pre>
+</div></div>
+<div class="paragraph"><p>These kind of mod_rewrite rules are no longer required, and you can safely remove
+them.</p></div>
+<h3 id="_page_caching_support">9.2. Page caching support</h3>
+<div class="paragraph"><p>For each HTTP request, Phusion Passenger will automatically look for a corresponding
+page cache file, and serve that if it exists. It does this by appending ".html" to
+the filename that the URI normally maps to, and checking whether that file exists.
+This check occurs after checking whether the original mapped filename exists (as part
+of static asset serving). All this is done without the need for special mod_rewrite
+rules.</p></div>
+<div class="paragraph"><p>For example, suppose that the browser requests <em>/foo/bar</em>.</p></div>
+<div class="olist arabic"><ol class="arabic">
+<li>
+<p>
+Phusion Passenger will first check whether this URI maps to a static file, i.e.
+   whether the file <em>foo/bar</em> exists in the web application&#8217;s <em>public</em> directory.
+   If it does then Phusion Passenger will serve this file through Apache immediately.
+</p>
+</li>
+<li>
+<p>
+If that doesn&#8217;t exist, then Phusion Passenger will check whether the file
+   <em>foo/bar.html</em> exists. If it does then Phusion Passenger will serve this file
+   through Apache immediately.
+</p>
+</li>
+<li>
+<p>
+If <em>foo/bar.html</em> doesn&#8217;t exist either, then Phusion Passenger will forward the
+   request to the underlying web application.
+</p>
+</li>
+</ol></div>
+<div class="paragraph"><p>Note that Phusion Passenger&#8217;s page caching support doesn&#8217;t work if your web
+application uses a non-standard page cache directory, i.e. if it doesn&#8217;t cache to
+the <em>public</em> directory. In that case you&#8217;ll need to use mod_rewrite to serve such
+page cache files.</p></div>
+<h3 id="_how_phusion_passenger_detects_whether_a_virtual_host_is_a_web_application">9.3. How Phusion Passenger detects whether a virtual host is a web application</h3>
+<div class="paragraph"><p>After you&#8217;ve read the deployment instructions you might wonder how Phusion Passenger
+knows that the DocumentRoot points to a web application that Phusion Passenger is
+able to serve, and how it knows what kind of web application it is (e.g. Rails or Rack).</p></div>
+<div class="paragraph"><p>Phusion Passenger checks whether the virtual host is a Rails application by checking
+whether the following file exists:</p></div>
+<div class="listingblock">
+<div class="content">
+<pre><tt>dirname(DocumentRoot) + "/config/environment.rb"</tt></pre>
+</div></div>
+<div class="paragraph"><p>If you&#8217;re not a programmer and don&#8217;t understand the above pseudo-code snippet, it means
+that Phusion Passenger will:</p></div>
+<div class="olist arabic"><ol class="arabic">
+<li>
+<p>
+Extract the parent directory filename from the value of the DocumentRoot directory.
+</p>
+</li>
+<li>
+<p>
+Append the text "/config/environment.rb" to the result, and check whether the resulting
+   filename exists.
+</p>
+</li>
+</ol></div>
+<div class="paragraph"><p>So suppose that your document root is <em>/webapps/foo/public</em>. Phusion Passenger will check
+whether the file <em>/webapps/foo/config/environment.rb</em> exists.</p></div>
+<div class="paragraph"><p>Note that Phusion Passenger does <strong>not</strong> resolve any symlinks in the document root path since
+version 2.2.0&#8201;&#8212;&#8201;in contrast to versions earlier than 2.2.0, which does resolve symlinks.
+So for example, suppose that your DocumentRoot points to <em>/home/www/example.com</em>, which in
+turn is a symlink to <em>/webapps/example.com/public</em>. In versions earlier than 2.2.0, Phusion
+Passenger will check whether <em>/webapps/example.com/config/environment.rb</em> exists because it
+resolves all symlinks. Phusion Passenger 2.2.0 and later however will check for
+<em>/home/www/config/environment.rb</em>. This file of course doesn&#8217;t exist, and as a result Phusion
+Passenger will not activate itself for this virtual host, and you&#8217;ll most likely see an Apache
+mod_dirindex directory listing.</p></div>
+<div class="paragraph"><p>If you&#8217;re running into this problem, you can explicitly tell Phusion Passenger what the
+correct application root is through the <a href="#PassengerAppRoot">PassengerAppRoot</a> configuration directive.</p></div>
+<div class="paragraph"><p>Autodetection of Rack applications happens through the same mechanism, exception that
+Phusion Passenger will look for <em>config.ru</em> instead of <em>config/environment.rb</em>.</p></div>
+</div>
+<h2 id="_appendix_a_about_this_document">10. Appendix A: About this document</h2>
 <div class="sectionbody">
 <div class="paragraph"><p>The text of this document is licensed under the
 <a href="http://creativecommons.org/licenses/by-sa/3.0/">Creative Commons
@@ -2760,9 +2985,9 @@ Attribution-Share Alike 3.0 Unported License</a>.</p></div>
 </span></p></div>
 <div class="paragraph"><p>Phusion Passenger is a trademark of Hongli Lai &amp; Ninh Bui.</p></div>
 </div>
-<h2 id="_appendix_b_terminology">10. Appendix B: Terminology</h2>
+<h2 id="_appendix_b_terminology">11. Appendix B: Terminology</h2>
 <div class="sectionbody">
-<h3 id="application_root">10.1. Application root</h3>
+<h3 id="application_root">11.1. Application root</h3>
 <div class="paragraph"><p>The root directory of an application that&#8217;s served by Phusion Passenger.</p></div>
 <div class="paragraph"><p>In case of Ruby on Rails applications, this is the directory that contains
 <em>Rakefile</em>, <em>app/</em>, <em>config/</em>, <em>public/</em>, etc. In other words, the directory
@@ -2820,7 +3045,7 @@ For example, take the following directory structure:</p></div>
    +- ...</tt></pre>
 </div></div>
 </div>
-<h2 id="spawning_methods_explained">11. Appendix C: Spawning methods explained</h2>
+<h2 id="spawning_methods_explained">12. Appendix C: Spawning methods explained</h2>
 <div class="sectionbody">
 <div class="paragraph"><p>At its core, Phusion Passenger is an HTTP proxy and process manager. It spawns
 Ruby on Rails/Rack/WSGI worker processes (which may also be referred to as
@@ -2829,7 +3054,7 @@ processes.</p></div>
 <div class="paragraph"><p>While this may sound simple, there&#8217;s not just one way to spawn worker processes.
 Let&#8217;s go over the different spawning methods. For simplicity&#8217;s sake, let&#8217;s
 assume that we&#8217;re only talking about Ruby on Rails applications.</p></div>
-<h3 id="_the_most_straightforward_and_traditional_way_conservative_spawning">11.1. The most straightforward and traditional way: conservative spawning</h3>
+<h3 id="_the_most_straightforward_and_traditional_way_conservative_spawning">12.1. The most straightforward and traditional way: conservative spawning</h3>
 <div class="paragraph"><p>Phusion Passenger could create a new Ruby process, which will then load the
 Rails application along with the entire Rails framework. This process will then
 enter an request handling main loop.</p></div>
@@ -2844,7 +3069,7 @@ programmers jargon, mongrel_cluster creates new Ruby processes by forking the
 current process and exec()-ing a new Ruby interpreter. Phusion Passenger on the
 other hand creates processes that reuse the already loaded Ruby interpreter. In
 programmers jargon, Phusion Passenger calls fork(), but not exec().</p></div>
-<h3 id="_the_smart_spawning_method">11.2. The smart spawning method</h3>
+<h3 id="_the_smart_spawning_method">12.2. The smart spawning method</h3>
 <div class="admonitionblock">
 <table><tr>
 <td class="icon">
@@ -2867,7 +3092,7 @@ by application and Rails framework code, by utilizing so-called
 copy-on-write semantics of the virtual memory system on modern operating
 systems. As a side effect, the startup time is also reduced. This is technique
 is exploited by Phusion Passenger&#8217;s <em>smart</em> and <em>smart-lv2</em> spawn methods.</p></div>
-<h4 id="_how_it_works">11.2.1. How it works</h4>
+<h4 id="_how_it_works">12.2.1. How it works</h4>
 <div class="paragraph"><p>When the <em>smart-lv2</em> spawn method is being used, Phusion Passenger will first
 create a so-called <em>ApplicationSpawner server</em> process. This process loads the
 entire Rails application along with the Rails framework, by loading
@@ -2917,7 +3142,7 @@ ApplicationSpawner and FrameworkSpawner servers have an idle timeout just
 </p>
 </li>
 </ul></div>
-<h4 id="_summary_of_benefits">11.2.2. Summary of benefits</h4>
+<h4 id="_summary_of_benefits">12.2.2. Summary of benefits</h4>
 <div class="paragraph"><p>Suppose that Phusion Passenger needs a new worker process for an application
 that uses Rails 2.2.1.</p></div>
 <div class="ulist"><ul>
@@ -2951,7 +3176,7 @@ process).</p></div>
 assuming that your Ruby interpreter is <a href="#reducing_memory_usage">copy-on-write friendly</a>.</p></div>
 <div class="paragraph"><p>Of course, smart spawning is not without gotchas. But if you understand the
 gotchas you can easily reap the benefits of smart spawning.</p></div>
-<h3 id="_smart_spawning_gotcha_1_unintential_file_descriptor_sharing">11.3. Smart spawning gotcha #1: unintential file descriptor sharing</h3>
+<h3 id="_smart_spawning_gotcha_1_unintential_file_descriptor_sharing">12.3. Smart spawning gotcha #1: unintential file descriptor sharing</h3>
 <div class="paragraph"><p>Because worker processes are created by forking from an ApplicationSpawner
 server, it will share all file descriptors that are opened by the
 ApplicationSpawner server. (This is part of the semantics of the Unix
@@ -2983,7 +3208,7 @@ http://www.gnu.org/software/src-highlite -->
 <div class="paragraph"><p>Note that Phusion Passenger automatically reestablishes the connection to the
 database upon creating a new worker process, which is why you normally do not
 encounter any database issues when using smart spawning mode.</p></div>
-<h4 id="_example_1_memcached_connection_sharing_harmful">11.3.1. Example 1: Memcached connection sharing (harmful)</h4>
+<h4 id="_example_1_memcached_connection_sharing_harmful">12.3.1. Example 1: Memcached connection sharing (harmful)</h4>
 <div class="paragraph"><p>Suppose we have a Rails application that connects to a Memcached server in
 <em>environment.rb</em>. This causes the ApplicationSpawner to have a socket connection
 (file descriptor) to the Memcached server, as shown in the following figure:</p></div>
@@ -3073,7 +3298,7 @@ http://www.gnu.org/software/src-highlite -->
         <span style="font-weight: bold"><span style="color: #0000FF">end</span></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>
-<h4 id="_example_2_log_file_sharing_not_harmful">11.3.2. Example 2: Log file sharing (not harmful)</h4>
+<h4 id="_example_2_log_file_sharing_not_harmful">12.3.2. Example 2: Log file sharing (not harmful)</h4>
 <div class="paragraph"><p>There are also cases in which unintential file descriptor sharing is not harmful.
 One such case is log file file descriptor sharing. Even if two processes write
 to the log file at the same time, the worst thing that can happen is that the
@@ -3082,7 +3307,7 @@ data in the log file is interleaved.</p></div>
 must synchronize write access via an inter-process synchronization mechanism,
 such as file locks. Reopening the log file, like you would have done in the
 Memcached example, doesn&#8217;t help.</p></div>
-<h3 id="_smart_spawning_gotcha_2_the_need_to_revive_threads">11.4. Smart spawning gotcha #2: the need to revive threads</h3>
+<h3 id="_smart_spawning_gotcha_2_the_need_to_revive_threads">12.4. Smart spawning gotcha #2: the need to revive threads</h3>
 <div class="paragraph"><p>Another part of the <em>fork()</em> system call&#8217;s semantics is the fact that threads
 disappear after a fork call. So if you&#8217;ve created any threads in environment.rb,
 then those threads will no longer be running in newly created worker process.
@@ -3103,7 +3328,7 @@ http://www.gnu.org/software/src-highlite -->
         <span style="font-weight: bold"><span style="color: #0000FF">end</span></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>
-<h3 id="_smart_spawning_gotcha_3_code_load_order">11.5. Smart spawning gotcha #3: code load order</h3>
+<h3 id="_smart_spawning_gotcha_3_code_load_order">12.5. Smart spawning gotcha #3: code load order</h3>
 <div class="paragraph"><p>This gotcha is only applicable to the <em>smart</em> spawn method, not the <em>smart-lv2</em>
 spawn method.</p></div>
 <div class="paragraph"><p>If your application expects the Rails framework to be not loaded during the
@@ -3122,7 +3347,7 @@ has no effect.</p></div>
 </div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2009-04-25 13:39:21 CEST
+Last updated 2009-06-16 23:49:41 CEST
 </div>
 </div>
 </body>