passenger 3.0.7 → 3.0.8

data/doc/Users guide Apache.idmap.txt

@@ -0,0 +1,80 @@
+###### Autogenerated by Mizuho, DO NOT EDIT ######
+# This file maps section names to IDs so that the commenting system knows which
+# comments belong to which section. Section names may be changed at will but
+# IDs always stay the same, allowing one to retain old comments even if you
+# rename a section.
+#
+# This file is autogenerated but is not a cache; you MUST NOT DELETE this
+# file and you must check it into your version control system. If you lose
+# this file you may lose the ability to identity old comments.
+#
+# Entries marked with "fuzzy" indicate that the section title has changed
+# and that Mizuho has found an ID which appears to be associated with that
+# section. You should check whether it is correct, and if not, fix it.
+
+1. Support information	=>	support-information-1ai724i
+
+1.1. Supported operating systems	=>	supported-operating-systems-18x8jzn
+
+1.2. Where to get support	=>	where-to-get-support-h5oojh
+
+2. Installing, upgrading and uninstalling Phusion Passenger	=>	installing-upgrading-and-uninstalling-phusion-passenger-a1zbnb
+
+2.1. Generic installation instructions	=>	generic-installation-instructions-eh9xhl
+
+2.1.1. Overview of installation methods	=>	overview-of-installation-methods-1rv04e2
+
+2.1.2. Preparation (gem and source tarball only)	=>	preparation-gem-and-source-tarball-only--11ofr29
+
+2.1.3. Installing via the gem	=>	installing-via-the-gem-6zjt30
+
+2.1.4. Installing via the source tarball	=>	installing-via-the-source-tarball-mly13a
+
+2.1.5. Installing via a native Linux package	=>	installing-via-a-native-linux-package-7l0t4v
+
+2.1.6. What does the installer do?	=>	what-does-the-installer-do--1j2bczq
+
+2.2. Operating system-specific instructions and information	=>	operating-system-specific-instructions-and-information-pqoxte
+
+2.2.1. MacOS X	=>	macos-x-kvt0z1
+
+2.2.2. Ubuntu Linux	=>	ubuntu-linux-1uu7vpl
+
+2.2.3. OpenSolaris	=>	opensolaris-t7oylf
+
+2.3. Upgrading or downgrading Phusion Passenger	=>	upgrading-or-downgrading-phusion-passenger-maq6fw
+
+2.3.1. Via a gem or a source tarball	=>	via-a-gem-or-a-source-tarball-wzkten
+
+2.3.2. Via a native Linux package	=>	via-a-native-linux-package-12eene2
+
+2.4. Unloading (disabling) Phusion Passenger from Apache without uninstalling it	=>	unloading-disabling-phusion-passenger-from-apache-without-uninstalling-it-1rb6log
+
+2.5. Uninstalling Phusion Passenger	=>	uninstalling-phusion-passenger-u9x0gk
+
+3. Deploying a Ruby on Rails application	=>	deploying-a-ruby-on-rails-application-itdr6l
+
+3.1. Deploying to a virtual host’s root	=>	deploying-to-a-virtual-host-s-root-148jpxy
+
+3.2. Deploying to a sub URI	=>	deploying-to-a-sub-uri-cukfoc
+
+3.3. Redeploying (restarting the Ruby on Rails application)	=>	redeploying-restarting-the-ruby-on-rails-application--1unls8v
+
+3.4. Migrations	=>	migrations-fjdjdr
+
+3.5. Capistrano integration	=>	capistrano-integration-1m5sn2y
+
+4. Deploying a Rack-based Ruby application	=>	deploying-a-rack-based-ruby-application-1swt4rl
+
+4.1. Tutorial/example: writing and deploying a Hello World Rack application	=>	tutorial-example-writing-and-deploying-a-hello-world-rack-application-znzu46
+
+4.2. Deploying to a virtual host’s root	=>	deploying-to-a-virtual-host-s-root-5wmulv
+
+4.3. Deploying to a sub URI	=>	deploying-to-a-sub-uri-l6sbwx
+
+4.4. Redeploying (restarting the Rack application)	=>	redeploying-restarting-the-rack-application--vn8xzn
+
+4.5. Rackup specifications for various web frameworks	=>	rackup-specifications-for-various-web-frameworks-13g881i
+
+4.5.1. Camping	=>	camping-1e2lve4
+

data/doc/Users guide Apache.txt

@@ -247,7 +247,7 @@ about setting up Ruby on Rails and Phusion Passenger on OpenSolaris and EC2.
 
 ==== Via a gem or a source tarball ====
 
-To ugrade or downgrade Phusion Passenger via the gem or the source tarball, install the newer
+To upgrade 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 `passenger-install-apache2-module`. Eventually `passenger-install-apache2-module` will tell
 you to copy & paste some settings into the Apache configuration file; something that looks along
@@ -345,7 +345,7 @@ done this, you need to remove the Phusion Passenger files.
   `sudo apt-get remove libapache2-mod-passenger`.
 
 
-== Deploying a Ruby on Rails application ==
+== Deploying a Ruby on Rails 1.x or 2.x (but NOT Rails >= 3.x) application ==
 
 Suppose you have a Ruby on Rails application in '/webapps/mycook', and you own
 the domain 'www.mycook.com'. You can either deploy your application to the
@@ -490,7 +490,7 @@ a shell console, just like one would normally run migrations.
 See <<capistrano,Capistrano recipe>>.
 
 
-== Deploying a Rack-based Ruby application ==
+== Deploying a Rack-based Ruby application (including Rails >= 3) ==
 
 Phusion Passenger supports arbitrary Ruby web applications that follow the
 link:http://rack.rubyforge.org/[Rack] interface.
@@ -935,7 +935,7 @@ The default value is 'on'.
 
 ==== PassengerUser <username> ====
 If <<user_switching,user switching support>> is enabled, then Phusion Passenger will
-by default run the web application as the owner if the file 'config/environment.rb'
+by default run the web application as the owner of the file 'config/environment.rb'
 (for Rails apps) or 'config.ru' (for Rack apps). This option allows you to override
 that behavior and explicitly set a user to run the web application as, regardless
 of the ownership of 'environment.rb'/'config.ru'.
@@ -1951,7 +1951,7 @@ To solve this problem, please <<specifying_correct_apache_install,specify the
 correct Apache installation>>, and <<install_passenger,reinstall Phusion
 Passenger>>.
 
-==== I get a "304 Forbidden" error ====
+==== I get a "403 Forbidden" error ====
 
 See next subsection.
 

data/doc/Users guide Nginx.html

@@ -1,16 +1,35 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
-    "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+<!DOCTYPE html>
+<html lang="en">
 <head>
-<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 8.6.1" />
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<meta name="generator" content="AsciiDoc 8.6.5">
 <title>Phusion Passenger users guide, Nginx version</title>
 <style type="text/css">
-/* Debug borders */
-p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
 /*
-  border: 1px solid red;
-*/
+ * AsciiDoc 'flask' theme for xhtml11 and html5 backends. A shameless knock-off
+ * of the Flask website styling (http://flask.pocoo.org/docs/).
+ *
+ * The implementation is straight-forward, consisting of the asciidoc.css file
+ * followed by theme specific overrides.
+ *
+ * */
+
+
+/* Shared CSS for AsciiDoc xhtml11 and html5 backends */
+
+/* Default font. */
+body {
+  font-family: Georgia,serif;
+}
+
+/* Title font. */
+h1, h2, h3, h4, h5, h6,
+div.title, caption.title,
+thead, p.table.header,
+#toctitle,
+#author, #revnumber, #revdate, #revremark,
+#footer {
+  font-family: Arial,Helvetica,sans-serif;
 }
 
 body {
@@ -35,13 +54,8 @@ strong {
   color: #083194;
 }
 
-tt {
-  color: navy;
-}
-
 h1, h2, h3, h4, h5, h6 {
   color: #527bbd;
-  font-family: sans-serif;
   margin-top: 1.2em;
   margin-bottom: 0.5em;
   line-height: 1.3;
@@ -59,9 +73,11 @@ h3 {
 h3 + * {
   clear: left;
 }
+h5 {
+  font-size: 1.0em;
+}
 
 div.sectionbody {
-  font-family: serif;
   margin-left: 0;
 }
 
@@ -77,45 +93,44 @@ p {
 ul, ol, li > p {
   margin-top: 0;
 }
+ul > li     { color: #aaa; }
+ul > li > * { color: black; }
 
 pre {
   padding: 0;
   margin: 0;
 }
 
-span#author {
+#author {
   color: #527bbd;
-  font-family: sans-serif;
   font-weight: bold;
   font-size: 1.1em;
 }
-span#email {
+#email {
 }
-span#revnumber, span#revdate, span#revremark {
-  font-family: sans-serif;
+#revnumber, #revdate, #revremark {
 }
 
-div#footer {
-  font-family: sans-serif;
+#footer {
   font-size: small;
   border-top: 2px solid silver;
   padding-top: 0.5em;
   margin-top: 4.0em;
 }
-div#footer-text {
+#footer-text {
   float: left;
   padding-bottom: 0.5em;
 }
-div#footer-badges {
+#footer-badges {
   float: right;
   padding-bottom: 0.5em;
 }
 
-div#preamble {
+#preamble {
   margin-top: 1.5em;
   margin-bottom: 1.5em;
 }
-div.tableblock, div.imageblock, div.exampleblock, div.verseblock,
+div.imageblock, div.exampleblock, div.verseblock,
 div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
 div.admonitionblock {
   margin-top: 1.0em;
@@ -135,7 +150,6 @@ div.content { /* Block element content. */
 /* Block element titles. */
 div.title, caption.title {
   color: #527bbd;
-  font-family: sans-serif;
   font-weight: bold;
   text-align: left;
   margin-top: 1.0em;
@@ -157,13 +171,15 @@ div.content + div.title {
 
 div.sidebarblock > div.content {
   background: #ffffee;
-  border: 1px solid silver;
+  border: 1px solid #dddddd;
+  border-left: 4px solid #f0f0f0;
   padding: 0.5em;
 }
 
 div.listingblock > div.content {
-  border: 1px solid silver;
-  background: #f4f4f4;
+  border: 1px solid #dddddd;
+  border-left: 5px solid #f0f0f0;
+  background: #f8f8f8;
   padding: 0.5em;
 }
 
@@ -171,7 +187,7 @@ div.quoteblock, div.verseblock {
   padding-left: 1.0em;
   margin-left: 1.0em;
   margin-right: 10%;
-  border-left: 5px solid #dddddd;
+  border-left: 5px solid #f0f0f0;
   color: #777777;
 }
 
@@ -182,6 +198,7 @@ div.quoteblock > div.attribution {
 
 div.verseblock > pre.content {
   font-family: inherit;
+  font-size: inherit;
 }
 div.verseblock > div.attribution {
   padding-top: 0.75em;
@@ -254,36 +271,12 @@ div.compact div, div.compact div {
   margin-bottom: 0.1em;
 }
 
-div.tableblock > table {
-  border: 3px solid #527bbd;
-}
-thead, p.table.header {
-  font-family: sans-serif;
-  font-weight: bold;
-  color: #527bbd;
-}
 tfoot {
   font-weight: bold;
 }
 td > div.verse {
   white-space: pre;
 }
-p.table {
-  margin-top: 0;
-}
-/* Because the table frame attribute is overriden by CSS in most browsers. */
-div.tableblock > table[frame="void"] {
-  border-style: none;
-}
-div.tableblock > table[frame="hsides"] {
-  border-left-style: none;
-  border-right-style: none;
-}
-div.tableblock > table[frame="vsides"] {
-  border-top-style: none;
-  border-bottom-style: none;
-}
-
 
 div.hdlist {
   margin-top: 0.8em;
@@ -350,16 +343,15 @@ div.colist td img {
 }
 
 @media print {
-  div#footer-badges { display: none; }
+  #footer-badges { display: none; }
 }
 
-div#toc {
+#toc {
   margin-bottom: 2.5em;
 }
 
-div#toctitle {
+#toctitle {
   color: #527bbd;
-  font-family: sans-serif;
   font-size: 1.1em;
   font-weight: bold;
   margin-top: 1.0em;
@@ -383,10 +375,223 @@ div.toclevel4 {
   font-size: 0.9em;
 }
 
+span.aqua { color: aqua; }
+span.black { color: black; }
+span.blue { color: blue; }
+span.fuchsia { color: fuchsia; }
+span.gray { color: gray; }
+span.green { color: green; }
+span.lime { color: lime; }
+span.maroon { color: maroon; }
+span.navy { color: navy; }
+span.olive { color: olive; }
+span.purple { color: purple; }
+span.red { color: red; }
+span.silver { color: silver; }
+span.teal { color: teal; }
+span.white { color: white; }
+span.yellow { color: yellow; }
+
+span.aqua-background { background: aqua; }
+span.black-background { background: black; }
+span.blue-background { background: blue; }
+span.fuchsia-background { background: fuchsia; }
+span.gray-background { background: gray; }
+span.green-background { background: green; }
+span.lime-background { background: lime; }
+span.maroon-background { background: maroon; }
+span.navy-background { background: navy; }
+span.olive-background { background: olive; }
+span.purple-background { background: purple; }
+span.red-background { background: red; }
+span.silver-background { background: silver; }
+span.teal-background { background: teal; }
+span.white-background { background: white; }
+span.yellow-background { background: yellow; }
+
+span.big { font-size: 2em; }
+span.small { font-size: 0.6em; }
+
+span.underline { text-decoration: underline; }
+span.overline { text-decoration: overline; }
+span.line-through { text-decoration: line-through; }
+
+
+/*
+ * xhtml11 specific
+ *
+ * */
+
+tt {
+  font-family: monospace;
+  font-size: inherit;
+  color: navy;
+}
+
+div.tableblock {
+  margin-top: 1.0em;
+  margin-bottom: 1.5em;
+}
+div.tableblock > table {
+  border: 3px solid #527bbd;
+}
+thead, p.table.header {
+  font-weight: bold;
+  color: #527bbd;
+}
+p.table {
+  margin-top: 0;
+}
+/* Because the table frame attribute is overriden by CSS in most browsers. */
+div.tableblock > table[frame="void"] {
+  border-style: none;
+}
+div.tableblock > table[frame="hsides"] {
+  border-left-style: none;
+  border-right-style: none;
+}
+div.tableblock > table[frame="vsides"] {
+  border-top-style: none;
+  border-bottom-style: none;
+}
+
+
+/*
+ * html5 specific
+ *
+ * */
+
+.monospaced {
+  font-family: monospace;
+  font-size: inherit;
+  color: navy;
+}
+
+table.tableblock {
+  margin-top: 1.0em;
+  margin-bottom: 1.5em;
+}
+thead, p.tableblock.header {
+  font-weight: bold;
+  color: #527bbd;
+}
+p.tableblock {
+  margin-top: 0;
+}
+table.tableblock {
+  border-width: 3px;
+  border-spacing: 0px;
+  border-style: solid;
+  border-color: #527bbd;
+  border-collapse: collapse;
+}
+th.tableblock, td.tableblock {
+  border-width: 1px;
+  padding: 4px;
+  border-style: solid;
+  border-color: #527bbd;
+}
+
+table.tableblock.frame-topbot {
+  border-left-style: hidden;
+  border-right-style: hidden;
+}
+table.tableblock.frame-sides {
+  border-top-style: hidden;
+  border-bottom-style: hidden;
+}
+table.tableblock.frame-none {
+  border-style: hidden;
+}
+
+th.tableblock.halign-left, td.tableblock.halign-left {
+  text-align: left;
+}
+th.tableblock.halign-center, td.tableblock.halign-center {
+  text-align: center;
+}
+th.tableblock.halign-right, td.tableblock.halign-right {
+  text-align: right;
+}
+
+th.tableblock.valign-top, td.tableblock.valign-top {
+  vertical-align: top;
+}
+th.tableblock.valign-middle, td.tableblock.valign-middle {
+  vertical-align: middle;
+}
+th.tableblock.valign-bottom, td.tableblock.valign-bottom {
+  vertical-align: bottom;
+}
+
+
+/*
+ * Theme specific overrides of the preceding (asciidoc.css) CSS.
+ *
+ */
+body {
+  font-family: Garamond, Georgia, serif;
+  font-size: 17px;
+  color: #3E4349;
+  line-height: 1.3em;
+}
+h1, h2, h3, h4, h5, h6,
+div.title, caption.title,
+thead, p.table.header,
+#toctitle,
+#author, #revnumber, #revdate, #revremark,
+#footer {
+  font-family: Garmond, Georgia, serif;
+  font-weight: normal;
+  border-bottom-width: 0;
+  color: #3E4349;
+}
+div.title, caption.title { color: #596673; font-weight: bold; }
+h1 { font-size: 240%; }
+h2 { font-size: 180%; }
+h3 { font-size: 150%; }
+h4 { font-size: 130%; }
+h5 { font-size: 100%; }
+h6 { font-size: 100%; }
+#header h1 { margin-top: 0; }
+#toc {
+  color: #444444;
+  line-height: 1.5;
+  padding-top: 1.5em;
+}
+#toctitle {
+  font-size: 20px;
+}
+#toc a {
+    border-bottom: 1px dotted #999999;
+    color: #444444 !important;
+    text-decoration: none !important;
+}
+#toc a:hover {
+    border-bottom: 1px solid #6D4100;
+    color: #6D4100 !important;
+    text-decoration: none !important;
+}
+div.toclevel1 { margin-top: 0.2em; font-size: 16px; }
+div.toclevel2 { margin-top: 0.15em; font-size: 14px; }
+em, dt, td.hdlist1 { color: black; }
+strong { color: #3E4349; }
+a { color: #004B6B; text-decoration: none; border-bottom: 1px dotted #004B6B; }
+a:visited { color: #615FA0; border-bottom: 1px dotted #615FA0; }
+a:hover { color: #6D4100; border-bottom: 1px solid #6D4100; }
+div.tableblock > table, table.tableblock { border: 3px solid #E8E8E8; }
+th.tableblock, td.tableblock { border: 1px solid #E8E8E8; }
+ul > li > * { color: #3E4349; }
+pre, tt, .monospaced { font-family: Consolas,Menlo,'Deja Vu Sans Mono','Bitstream Vera Sans Mono',monospace; }
+tt, .monospaced { font-size: 0.9em; color: black;
+}
+div.exampleblock > div.content, div.sidebarblock > div.content, div.listingblock > div.content { border-width: 0 0 0 3px; border-color: #E8E8E8; }
+div.verseblock { border-left-width: 0; margin-left: 3em; }
+div.quoteblock { border-left-width: 3px; margin-left: 0; margin-right: 0;}
+div.admonitionblock td.content { border-left: 3px solid #E8E8E8; }
 </style>
 <script type="text/javascript">
 /*<![CDATA[*/
-window.onload = function(){asciidoc.footnotes(); asciidoc.toc(3);}
 var asciidoc = {  // Namespace.
 
 /////////////////////////////////////////////////////////////////////
@@ -448,6 +653,25 @@ toc: function (toclevels) {
   }
 
   var toc = document.getElementById("toc");
+  if (!toc) {
+    return;
+  }
+
+  // Delete existing TOC entries in case we're reloading the TOC.
+  var tocEntriesToRemove = [];
+  var i;
+  for (i = 0; i < toc.childNodes.length; i++) {
+    var entry = toc.childNodes[i];
+    if (entry.nodeName == 'DIV'
+     && entry.getAttribute("class")
+     && entry.getAttribute("class").match(/^toclevel/))
+      tocEntriesToRemove.push(entry);
+  }
+  for (i = 0; i < tocEntriesToRemove.length; i++) {
+    toc.removeChild(tocEntriesToRemove[i]);
+  }
+
+  // Rebuild TOC entries.
   var entries = tocEntries(document.getElementById("content"), toclevels);
   for (var i = 0; i < entries.length; ++i) {
     var entry = entries[i];
@@ -475,24 +699,44 @@ toc: function (toclevels) {
  */
 
 footnotes: function () {
-  var cont = document.getElementById("content");
+  // Delete existing footnote entries in case we're reloading the footnodes.
+  var i;
   var noteholder = document.getElementById("footnotes");
+  if (!noteholder) {
+    return;
+  }
+  var entriesToRemove = [];
+  for (i = 0; i < noteholder.childNodes.length; i++) {
+    var entry = noteholder.childNodes[i];
+    if (entry.nodeName == 'DIV' && entry.getAttribute("class") == "footnote")
+      entriesToRemove.push(entry);
+  }
+  for (i = 0; i < entriesToRemove.length; i++) {
+    noteholder.removeChild(entriesToRemove[i]);
+  }
+
+  // Rebuild footnote entries.
+  var cont = document.getElementById("content");
   var spans = cont.getElementsByTagName("span");
   var refs = {};
   var n = 0;
   for (i=0; i<spans.length; i++) {
     if (spans[i].className == "footnote") {
       n++;
-      // Use [\s\S] in place of . so multi-line matches work.
-      // Because JavaScript has no s (dotall) regex flag.
-      note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
+      var note = spans[i].getAttribute("data-note");
+      if (!note) {
+        // Use [\s\S] in place of . so multi-line matches work.
+        // Because JavaScript has no s (dotall) regex flag.
+        note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
+        spans[i].innerHTML =
+          "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
+          "' title='View footnote' class='footnote'>" + n + "</a>]";
+        spans[i].setAttribute("data-note", note);
+      }
       noteholder.innerHTML +=
         "<div class='footnote' id='_footnote_" + n + "'>" +
         "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
         n + "</a>. " + note + "</div>";
-      spans[i].innerHTML =
-        "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
-        "' title='View footnote' class='footnote'>" + n + "</a>]";
       var id =spans[i].getAttribute("id");
       if (id != null) refs["#"+id] = n;
     }
@@ -512,9 +756,32 @@ footnotes: function () {
       }
     }
   }
+},
+
+install: function(toclevels) {
+  var timerId;
+
+  function reinstall() {
+    asciidoc.footnotes();
+    if (toclevels) {
+      asciidoc.toc(toclevels);
+    }
+  }
+
+  function reinstallAndRemoveTimer() {
+    clearInterval(timerId);
+    reinstall();
+  }
+
+  timerId = setInterval(reinstall, 500);
+  if (document.addEventListener)
+    document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
+  else
+    window.onload = reinstallAndRemoveTimer;
 }
 
 }
+asciidoc.install(3);
 /*]]>*/
 </script>
 </head>
@@ -531,7 +798,7 @@ footnotes: function () {
 <div class="sectionbody">
 <div class="paragraph"><p><span class="image">
 <a class="image" href="http://www.phusion.nl/">
-<img src="images/phusion_banner.png" alt="images/phusion_banner.png" />
+<img src="images/phusion_banner.png" alt="images/phusion_banner.png">
 </a>
 </span></p></div>
 <div class="paragraph"><p>Phusion Passenger is an Nginx module, which makes deploying Ruby and Ruby on
@@ -627,7 +894,7 @@ By running the Phusion Passenger installer for Nginx. This installer will
 <li>
 <p>
 By manually configuring and compiling Nginx with Phusion Passenger support,
-   through Nginx&#8217;s <tt>--add-module</tt> configure option. Generally, using our
+   through Nginx&#8217;s <span class="monospaced">--add-module</span> configure option. Generally, using our
    installer is easier, so you should only use this method if you&#8217;re already
    familiar with compiling Nginx.
 </p>
@@ -636,7 +903,7 @@ By manually configuring and compiling Nginx with Phusion Passenger support,
 <div class="admonitionblock">
 <table><tr>
 <td class="icon">
-<img src="./images/icons/tip.png" alt="Tip" />
+<img src="./images/icons/tip.png" alt="Tip">
 </td>
 <td class="content">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
@@ -653,8 +920,8 @@ will need to tell the operating system which Ruby installation to use, prior to
 running the Phusion Passenger installer. If you only have one Ruby 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>To specify a Ruby installation, prepend your Ruby installation&#8217;s <tt>bin</tt>
-directory to the <tt>PATH</tt> environment variable. For example, if you have the
+<div class="paragraph"><p>To specify a Ruby installation, prepend your Ruby installation&#8217;s <span class="monospaced">bin</span>
+directory to the <span class="monospaced">PATH</span> environment variable. For example, if you have the
 following Ruby installations:</p></div>
 <div class="ulist"><ul>
 <li>
@@ -670,8 +937,8 @@ following Ruby installations:</p></div>
 </ul></div>
 <div class="paragraph"><p>and you want to use the latter, then type:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>export PATH=/opt/myruby/bin:$PATH</tt></pre>
+<div class="content monospaced">
+<pre>export PATH=/opt/myruby/bin:$PATH</pre>
 </div></div>
 </div>
 <div class="sect2">
@@ -685,13 +952,13 @@ downloading the source tarball.</p></div>
 <h5 id="_gem">Gem</h5>
 <div class="paragraph"><p>First, install the Phusion Passenger gem by running:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>gem install passenger</tt></pre>
+<div class="content monospaced">
+<pre>gem install passenger</pre>
 </div></div>
 <div class="paragraph"><p>Next, run the Phusion Passenger installer for Nginx:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>passenger-install-nginx-module</tt></pre>
+<div class="content monospaced">
+<pre>passenger-install-nginx-module</pre>
 </div></div>
 <div class="paragraph"><p>Please follow the instructions given by the installer.</p></div>
 </div>
@@ -701,22 +968,22 @@ downloading the source tarball.</p></div>
 <a href="http://www.modrails.com/">Phusion Passenger website</a>. Extract the tarball to
 whatever location you prefer. <strong>The Phusion Passenger files are to reside in that
 location permanently.</strong> For example, if you would like Phusion Passenger to
-reside in <tt>/opt/passenger-x.x.x</tt>, then type:</p></div>
+reside in <span class="monospaced">/opt/passenger-x.x.x</span>, then type:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>cd /opt
-tar xzvf ~/YourDownloadsFolder/passenger-x.x.x.tar.gz</tt></pre>
+<div class="content monospaced">
+<pre>cd /opt
+tar xzvf ~/YourDownloadsFolder/passenger-x.x.x.tar.gz</pre>
 </div></div>
 <div class="paragraph"><p>Next, run the Phusion Passenger installer for Nginx:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>/opt/passenger-x.x.x/bin/passenger-install-nginx-module</tt></pre>
+<div class="content monospaced">
+<pre>/opt/passenger-x.x.x/bin/passenger-install-nginx-module</pre>
 </div></div>
 <div class="paragraph"><p>Please follow the instructions given by the installer.</p></div>
 <div class="admonitionblock">
 <table><tr>
 <td class="icon">
-<img src="./images/icons/important.png" alt="Important" />
+<img src="./images/icons/important.png" alt="Important">
 </td>
 <td class="content">Please do not remove the passenger-x.x.x folder after installation.
 Furthermore, the passenger-x.x.x folder must be accessible by Nginx.</td>
@@ -729,31 +996,31 @@ Furthermore, the passenger-x.x.x folder must be accessible by Nginx.</td>
 <div class="paragraph"><p>By default, the installer is interactive. If you want to automate installation,
 then you can do so by passing various answers to the installer through command
 line options.</p></div>
-<div class="paragraph"><p>Please run the installer with <tt>--help</tt> for a list of available command line
+<div class="paragraph"><p>Please run the installer with <span class="monospaced">--help</span> for a list of available command line
 options.</p></div>
 </div>
 </div>
 <div class="sect2">
 <h3 id="_installing_phusion_passenger_for_nginx_manually">2.4. Installing Phusion Passenger for Nginx manually</h3>
 <div class="paragraph"><p>You can also install Phusion Passenger the way you install any other Nginx module.
-To do this, run Nginx&#8217;s configure script with <tt>--add-module=/path-to-passenger-root/ext/nginx</tt>.</p></div>
+To do this, run Nginx&#8217;s configure script with <span class="monospaced">--add-module=/path-to-passenger-root/ext/nginx</span>.</p></div>
 <div class="paragraph"><p>If you installed Phusion Passenger via the gem, then <em>path-to-passenger-root</em>
 can be obtained with the command:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>passenger-config --root</tt></pre>
+<div class="content monospaced">
+<pre>passenger-config --root</pre>
 </div></div>
 <div class="paragraph"><p>This will probably output something along the lines of <em>/usr/lib/ruby/gems/1.8/gems/passenger-x.x.x</em>,
-so you&#8217;ll probably have to specify something like <tt>--add-module=/usr/lib/ruby/gems/1.8/gems/passenger-x.x.x/ext/nginx</tt>.</p></div>
+so you&#8217;ll probably have to specify something like <span class="monospaced">--add-module=/usr/lib/ruby/gems/1.8/gems/passenger-x.x.x/ext/nginx</span>.</p></div>
 <div class="paragraph"><p>If you installed Phusion Passenger via a source tarball, then <em>path-to-passenger-root</em>
 is the directory which contains the Phusion Passenger source code. So if you
 extracted the Phusion Passenger source code to <em>/opt/passenger-x.x.x</em>, then you&#8217;ll
-have to specify <tt>--add-module=/opt/passenger-x.x.x/ext/nginx</tt>.</p></div>
+have to specify <span class="monospaced">--add-module=/opt/passenger-x.x.x/ext/nginx</span>.</p></div>
 <div class="paragraph"><p>After having installed Nginx with Phusion Passenger support, you must paste the following
 line into your Nginx configuration file:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>passenger_root /path-to-passenger-root;</tt></pre>
+<div class="content monospaced">
+<pre>passenger_root /path-to-passenger-root;</pre>
 </div></div>
 <div class="paragraph"><p>After having done so, restart Nginx.</p></div>
 </div>
@@ -762,13 +1029,13 @@ line into your Nginx configuration file:</p></div>
 <div class="paragraph"><p>Whether you&#8217;re upgrading/downgrading Phusion Passenger or Nginx itself (or perhaps both),
 Nginx will have to be recompiled and reinstalled. The procedure is exactly the same as
 a normal installation so just follow the instructions in section 2.3 or 2.4.</p></div>
-<div class="paragraph"><p>When following the installation instructions, eventually <tt>passenger-install-nginx-module</tt>
+<div class="paragraph"><p>When following the installation instructions, eventually <span class="monospaced">passenger-install-nginx-module</span>
 or this document will instruct you to copy &amp; paste some settings into the Nginx
 configuration file; something that looks along the lines of:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>passenger_root ...;
-passenger_ruby ...;</tt></pre>
+<div class="content monospaced">
+<pre>passenger_root ...;
+passenger_ruby ...;</pre>
 </div></div>
 <div class="paragraph"><p>Because you already had Phusion Passenger installed, you already had similar settings
 in your Nginx configuration file, just with different values. <strong>Replace</strong> the old settings with
@@ -790,8 +1057,8 @@ Nginx.</p></div>
 and comment out all Phusion Passenger configuration directives.</p></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>...
+<div class="content monospaced">
+<pre>...
 
 http {
     passenger_root /somewhere/passenger-x.x.x;
@@ -807,12 +1074,12 @@ http {
         passenger_enabled on;
         passenger_use_global_queue on;
     }
-}</tt></pre>
+}</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>...
+<div class="content monospaced">
+<pre>...
 
 http {
     # passenger_root /somewhere/passenger-x.x.x;
@@ -828,7 +1095,7 @@ http {
         # passenger_enabled on;
         # passenger_use_global_queue on;
     }
-}</tt></pre>
+}</pre>
 </div></div>
 <div class="paragraph"><p>After you&#8217;ve done this, save the file and restart Nginx.</p></div>
 </div>
@@ -840,7 +1107,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 gem, then type <tt>gem uninstall passenger</tt>.
+If you installed Phusion Passenger via a gem, then type <span class="monospaced">gem uninstall passenger</span>.
   You might have to run this as root.
 </p>
 </li>
@@ -859,7 +1126,7 @@ Nginx binary.</p></div>
 </div>
 </div>
 <div class="sect1">
-<h2 id="deploying_a_ror_app">3. Deploying a Ruby on Rails application</h2>
+<h2 id="deploying_a_ror_app">3. Deploying a Ruby on Rails 1.x or 2.x (but NOT Rails &gt;= 3) application</h2>
 <div class="sectionbody">
 <div class="paragraph"><p>Suppose you have a Ruby on Rails application in <em>/webapps/mycook</em>, and you own
 the domain <em>www.mycook.com</em>. You can either deploy your application to the
@@ -869,9 +1136,9 @@ accessible from a sub URL, such as <em>http://www.mycook.com/railsapplication</e
 <div class="admonitionblock">
 <table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note" />
+<img src="./images/icons/note.png" alt="Note">
 </td>
-<td class="content">The default <tt>RAILS_ENV</tt> environment in which deployed Rails applications
+<td class="content">The default <span class="monospaced">RAILS_ENV</span> environment in which deployed Rails applications
 are run, is &#8220;production&#8221;. You can change this by changing the
 <a href="#RailsEnv">rails_env</a> configuration option.</td>
 </tr></table>
@@ -883,8 +1150,8 @@ host&#8217;s root must point to your Ruby on Rails application&#8217;s <em>publi
 <div class="paragraph"><p>Inside the <em>server</em> block, set <em>passenger_enabled on</em>.</p></div>
 <div class="paragraph"><p>For example:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>http {
+<div class="content monospaced">
+<pre>http {
     ...
 
     server {
@@ -895,7 +1162,7 @@ host&#8217;s root must point to your Ruby on Rails application&#8217;s <em>publi
     }
 
     ...
-}</tt></pre>
+}</pre>
 </div></div>
 <div class="paragraph"><p>Then restart Nginx. The application has now been deployed.</p></div>
 </div>
@@ -903,8 +1170,8 @@ host&#8217;s root must point to your Ruby on Rails application&#8217;s <em>publi
 <h3 id="deploying_rails_to_sub_uri">3.2. Deploying to a sub URI</h3>
 <div class="paragraph"><p>Suppose that you already have a <em>server</em> virtual host entry:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>http {
+<div class="content monospaced">
+<pre>http {
     ...
 
     server {
@@ -914,21 +1181,21 @@ host&#8217;s root must point to your Ruby on Rails application&#8217;s <em>publi
     }
 
     ...
-}</tt></pre>
+}</pre>
 </div></div>
 <div class="paragraph"><p>And you want your Ruby on Rails application to be accessible from the URL
 <em>http://www.phusion.nl/rails</em>.</p></div>
 <div class="paragraph"><p>To do this, make a symlink in the virtual host&#8217;s document root, and have it
 point to your Ruby on Rails application&#8217;s <em>public</em> folder. For example:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>ln -s /webapps/mycook/public /websites/phusion/rails</tt></pre>
+<div class="content monospaced">
+<pre>ln -s /webapps/mycook/public /websites/phusion/rails</pre>
 </div></div>
 <div class="paragraph"><p>Next, set <em>passenger_enabled on</em> and add a <a href="#PassengerBaseURI">passenger_base_uri</a>
 option to the <em>server</em> block:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>http {
+<div class="content monospaced">
+<pre>http {
     ...
 
     server {
@@ -940,25 +1207,25 @@ option to the <em>server</em> block:</p></div>
     }
 
     ...
-}</tt></pre>
+}</pre>
 </div></div>
 <div class="paragraph"><p>Then restart Nginx. The application has now been deployed.</p></div>
 <div class="admonitionblock">
 <table><tr>
 <td class="icon">
-<img src="./images/icons/tip.png" alt="Tip" />
+<img src="./images/icons/tip.png" alt="Tip">
 </td>
 <td class="content">
 <div class="paragraph"><p>You can deploy multiple Rails applications under a virtual host, by specifying
 <a href="#PassengerBaseURI">passenger_base_uri</a> multiple times. For example:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>server {
+<div class="content monospaced">
+<pre>server {
     ...
     passenger_base_uri /app1;
     passenger_base_uri /app2;
     passenger_base_uri /app3;
-}</tt></pre>
+}</pre>
 </div></div>
 </td>
 </tr></table>
@@ -986,8 +1253,8 @@ By creating or modifying the file <em>tmp/restart.txt</em> in the Rails
 <div class="paragraph"><p>For example, to restart our example MyCook application, we type this in the
 command line:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>touch /webapps/mycook/tmp/restart.txt</tt></pre>
+<div class="content monospaced">
+<pre>touch /webapps/mycook/tmp/restart.txt</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
@@ -998,7 +1265,7 @@ 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
-server (e.g. with <em>ssh</em>) and type <tt>rake db:migrate RAILS_ENV=production</tt> in
+server (e.g. with <em>ssh</em>) and type <span class="monospaced">rake db:migrate RAILS_ENV=production</span> in
 a shell console, just like one would normally run migrations.</p></div>
 </div>
 <div class="sect2">
@@ -1008,7 +1275,7 @@ a shell console, just like one would normally run migrations.</p></div>
 </div>
 </div>
 <div class="sect1">
-<h2 id="deploying_a_rack_app">4. Deploying a Rack-based Ruby application</h2>
+<h2 id="deploying_a_rack_app">4. Deploying a Rack-based Ruby application (including Rails &gt;= 3)</h2>
 <div class="sectionbody">
 <div class="paragraph"><p>Phusion Passenger supports arbitrary Ruby web applications that follow the
 <a href="http://rack.rubyforge.org/">Rack</a> interface.</p></div>
@@ -1036,14 +1303,14 @@ folder must contain at least three entries:</p></div>
 </ul></div>
 <div class="paragraph"><p>So <em>/webapps/rackapp</em> must, at minimum, look like this:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>/webapps/rackapp
+<div class="content monospaced">
+<pre>/webapps/rackapp
   |
   +-- config.ru
   |
   +-- public/
   |
-  +-- tmp/</tt></pre>
+  +-- tmp/</pre>
 </div></div>
 <div class="paragraph"><p>Suppose you own the domain <em>www.rackapp.com</em>. You can either deploy your application
 to the virtual host&#8217;s root (i.e. the application will be accessible from the root URL,
@@ -1052,9 +1319,9 @@ accessible from a sub URL, such as <em>http://www.rackapp.com/rackapp</em>).</p>
 <div class="admonitionblock">
 <table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note" />
+<img src="./images/icons/note.png" alt="Note">
 </td>
-<td class="content">The default <tt>RACK_ENV</tt> environment in which deployed Rack applications
+<td class="content">The default <span class="monospaced">RACK_ENV</span> environment in which deployed Rack applications
 are run, is &#8220;production&#8221;. You can change this by changing the
 <a href="#RackEnv">rack_env</a> configuration option.</td>
 </tr></table>
@@ -1063,28 +1330,28 @@ are run, is &#8220;production&#8221;. You can change this by changing the
 <h3 id="_tutorial_example_writing_and_deploying_a_hello_world_rack_application">4.1. Tutorial/example: writing and deploying a Hello World Rack application</h3>
 <div class="paragraph"><p>First we create a Phusion Passenger-compliant Rack directory structure:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>$ mkdir /webapps/rack_example
+<div class="content monospaced">
+<pre>$ mkdir /webapps/rack_example
 $ mkdir /webapps/rack_example/public
-$ mkdir /webapps/rack_example/tmp</tt></pre>
+$ mkdir /webapps/rack_example/tmp</pre>
 </div></div>
 <div class="paragraph"><p>Next, we write a minimal "hello world" Rack application:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>$ cd /webapps/rack_example
+<div class="content monospaced">
+<pre>$ cd /webapps/rack_example
 $ some_awesome_editor config.ru
 ...type in some source code...
 $ cat config.ru
 app = proc do |env|
     [200, { "Content-Type" =&gt; "text/html" }, ["hello &lt;b&gt;world&lt;/b&gt;"]]
 end
-run app</tt></pre>
+run app</pre>
 </div></div>
 <div class="paragraph"><p>Finally, we deploy it by adding the following configuration options to
 the Nginx configuration file:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>http {
+<div class="content monospaced">
+<pre>http {
     ...
     server {
         listen 80;
@@ -1093,7 +1360,7 @@ the Nginx configuration file:</p></div>
         passenger_enabled on;
     }
     ...
-}</tt></pre>
+}</pre>
 </div></div>
 <div class="paragraph"><p>And we&#8217;re done! After an Nginx restart, the above Rack application will be available
 under the URL <em>http://www.rackexample.com/</em>.</p></div>
@@ -1105,8 +1372,8 @@ root must point to your Rack application&#8217;s <em>public</em> folder. You mus
 <em>passenger_enabled on</em> in the <em>server</em> block.</p></div>
 <div class="paragraph"><p>For example:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>http {
+<div class="content monospaced">
+<pre>http {
     ...
     server {
         listen 80;
@@ -1115,7 +1382,7 @@ root must point to your Rack application&#8217;s <em>public</em> folder. You mus
         passenger_enabled on;
     }
     ...
-}</tt></pre>
+}</pre>
 </div></div>
 <div class="paragraph"><p>Then restart Nginx. The application has now been deployed.</p></div>
 </div>
@@ -1123,8 +1390,8 @@ root must point to your Rack application&#8217;s <em>public</em> folder. You mus
 <h3 id="deploying_rack_to_sub_uri">4.3. Deploying to a sub URI</h3>
 <div class="paragraph"><p>Suppose that you already have a virtual host:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>http {
+<div class="content monospaced">
+<pre>http {
     ...
 
     server {
@@ -1135,21 +1402,21 @@ root must point to your Rack application&#8217;s <em>public</em> folder. You mus
     }
 
     ...
-}</tt></pre>
+}</pre>
 </div></div>
 <div class="paragraph"><p>And you want your Rack application to be accessible from the URL
 <em>http://www.phusion.nl/rack</em>.</p></div>
 <div class="paragraph"><p>To do this, make a symlink in the virtual host&#8217;s document root, and have it
 point to your Rack application&#8217;s <em>public</em> folder. For example:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>ln -s /webapps/rackapp/public /websites/phusion/rack</tt></pre>
+<div class="content monospaced">
+<pre>ln -s /webapps/rackapp/public /websites/phusion/rack</pre>
 </div></div>
 <div class="paragraph"><p>Next, set <em>passenger_enabled on</em> and add a <a href="#PassengerBaseURI">passenger_base_uri</a>
 option to the <em>server</em> block:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>http {
+<div class="content monospaced">
+<pre>http {
     ...
 
     server {
@@ -1161,25 +1428,25 @@ option to the <em>server</em> block:</p></div>
     }
 
     ...
-}</tt></pre>
+}</pre>
 </div></div>
 <div class="paragraph"><p>Then restart Nginx. The application has now been deployed.</p></div>
 <div class="admonitionblock">
 <table><tr>
 <td class="icon">
-<img src="./images/icons/tip.png" alt="Tip" />
+<img src="./images/icons/tip.png" alt="Tip">
 </td>
 <td class="content">
 <div class="paragraph"><p>You can deploy multiple Rack applications under a virtual host, by specifying
 <a href="#PassengerBaseURI">passenger_base_uri</a> multiple times. For example:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>server {
+<div class="content monospaced">
+<pre>server {
     ...
     passenger_base_uri /app1;
     passenger_base_uri /app2;
     passenger_base_uri /app3;
-}</tt></pre>
+}</pre>
 </div></div>
 </td>
 </tr></table>
@@ -1207,8 +1474,8 @@ By creating or modifying the file <em>tmp/restart.txt</em> in the Rack
 <div class="paragraph"><p>For example, to restart our example application, we type this in the
 command line:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>touch /webapps/rackapp/tmp/restart.txt</tt></pre>
+<div class="content monospaced">
+<pre>touch /webapps/rackapp/tmp/restart.txt</pre>
 </div></div>
 </div>
 <div class="sect2">
@@ -1217,8 +1484,8 @@ command line:</p></div>
 <div class="sect3">
 <h4 id="_camping">4.5.1. Camping</h4>
 <div class="listingblock">
-<div class="content">
-<pre><tt>require 'rubygems'
+<div class="content monospaced">
+<pre>require 'rubygems'
 require 'rack'
 require 'camping'
 
@@ -1228,37 +1495,37 @@ Camping.goes :Blog
 ...your application code here...
 ##### End Camping application
 
-run Rack::Adapter::Camping.new(Blog)</tt></pre>
+run Rack::Adapter::Camping.new(Blog)</pre>
 </div></div>
-<div class="paragraph"><p>For Camping versions 2.0 and up, using <tt>run Blog</tt> as the final line will do.</p></div>
+<div class="paragraph"><p>For Camping versions 2.0 and up, using <span class="monospaced">run Blog</span> as the final line will do.</p></div>
 </div>
 <div class="sect3">
 <h4 id="_halcyon">4.5.2. Halcyon</h4>
 <div class="listingblock">
-<div class="content">
-<pre><tt>require 'rubygems'
+<div class="content monospaced">
+<pre>require 'rubygems'
 require 'halcyon'
 $LOAD_PATH.unshift(Halcyon.root / 'lib')
 Halcyon::Runner.load_config Halcyon.root/'config'/'config.yml'
-run Halcyon::Runner.new</tt></pre>
+run Halcyon::Runner.new</pre>
 </div></div>
 </div>
 <div class="sect3">
 <h4 id="_mack">4.5.3. Mack</h4>
 <div class="listingblock">
-<div class="content">
-<pre><tt>ENV["MACK_ENV"] = ENV["RACK_ENV"]
+<div class="content monospaced">
+<pre>ENV["MACK_ENV"] = ENV["RACK_ENV"]
 load("Rakefile")
 require 'rubygems'
 require 'mack'
-run Mack::Utils::Server.build_app</tt></pre>
+run Mack::Utils::Server.build_app</pre>
 </div></div>
 </div>
 <div class="sect3">
 <h4 id="_merb">4.5.4. Merb</h4>
 <div class="listingblock">
-<div class="content">
-<pre><tt>require 'rubygems'
+<div class="content monospaced">
+<pre>require 'rubygems'
 require 'merb-core'
 
 Merb::Config.setup(
@@ -1269,30 +1536,30 @@ Merb.environment = Merb::Config[:environment]
 Merb.root = Merb::Config[:merb_root]
 Merb::BootLoader.run
 
-run Merb::Rack::Application.new</tt></pre>
+run Merb::Rack::Application.new</pre>
 </div></div>
 </div>
 <div class="sect3">
 <h4 id="_ramaze">4.5.5. Ramaze</h4>
 <div class="listingblock">
-<div class="content">
-<pre><tt>require "rubygems"
+<div class="content monospaced">
+<pre>require "rubygems"
 require "ramaze"
 Ramaze.trait[:essentials].delete Ramaze::Adapter
 require "start"
 Ramaze.start!
-run Ramaze::Adapter::Base</tt></pre>
+run Ramaze::Adapter::Base</pre>
 </div></div>
 </div>
 <div class="sect3">
 <h4 id="_sinatra">4.5.6. Sinatra</h4>
 <div class="listingblock">
-<div class="content">
-<pre><tt>require 'rubygems'
+<div class="content monospaced">
+<pre>require 'rubygems'
 require 'sinatra'
 require 'app.rb'
 
-run Sinatra::Application</tt></pre>
+run Sinatra::Application</pre>
 </div></div>
 </div>
 </div>
@@ -1326,7 +1593,7 @@ The default is <em>ruby</em>.</p></div>
 <div class="admonitionblock">
 <table><tr>
 <td class="icon">
-<img src="./images/icons/tip.png" alt="Tip" />
+<img src="./images/icons/tip.png" alt="Tip">
 </td>
 <td class="content">
 <div class="title">"What spawn method should I use?"</div>
@@ -1335,7 +1602,7 @@ understand it, as it&#8217;s mostly a technical detail. You can basically follow
 <div class="sidebarblock">
 <div class="content">
 <div class="paragraph"><p>If your application works on Mongrel, but not on Phusion Passenger, then set
-<tt>passenger_spawn_method</tt> to <em>conservative</em>. Otherwise, leave it at <em>smart-lv2</em> (the default).</p></div>
+<span class="monospaced">passenger_spawn_method</span> to <em>conservative</em>. Otherwise, leave it at <em>smart-lv2</em> (the default).</p></div>
 </div></div>
 <div class="paragraph"><p>However, we do recommend you to try to understand it. The <em>smart</em> and <em>smart-lv2</em> spawn
 methods bring many benefits.</p></div>
@@ -1539,31 +1806,31 @@ we&#8217;re currently in a state where all backend processes have 3 requests in
 </ul></div>
 <div class="paragraph"><p>The situation looks like this:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>Backend process A:  [*     ]  (1 request in queue)
+<div class="content monospaced">
+<pre>Backend process A:  [*     ]  (1 request in queue)
 Backend process B:  [***   ]  (3 requests in queue)
 Backend process C:  [***   ]  (3 requests in queue)
-Backend process D:  [***   ]  (3 requests in queue)</tt></pre>
+Backend process D:  [***   ]  (3 requests in queue)</pre>
 </div></div>
 <div class="paragraph"><p>Each process is currently serving short-running requests.</p></div>
 <div class="paragraph"><p>Phusion Passenger will forward the next request to backend process A. A will
 now have 2 items in its queue. We&#8217;ll mark this new request with an X:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>Backend process A:  [*X    ]  (2 request in queue)
+<div class="content monospaced">
+<pre>Backend process A:  [*X    ]  (2 request in queue)
 Backend process B:  [***   ]  (3 requests in queue)
 Backend process C:  [***   ]  (3 requests in queue)
-Backend process D:  [***   ]  (3 requests in queue)</tt></pre>
+Backend process D:  [***   ]  (3 requests in queue)</pre>
 </div></div>
 <div class="paragraph"><p>Assuming that B, C and D still aren&#8217;t done with their current request, the next
 HTTP request - let&#8217;s call this Y - will be forwarded to backend process A as
 well, because it has the least number of items in its queue:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>Backend process A:  [*XY   ]  (3 requests in queue)
+<div class="content monospaced">
+<pre>Backend process A:  [*XY   ]  (3 requests in queue)
 Backend process B:  [***   ]  (3 requests in queue)
 Backend process C:  [***   ]  (3 requests in queue)
-Backend process D:  [***   ]  (3 requests in queue)</tt></pre>
+Backend process D:  [***   ]  (3 requests in queue)</pre>
 </div></div>
 <div class="paragraph"><p>But if request X happens to be a long-running request that needs 60 seconds to
 complete, then we&#8217;ll have a problem. Y won&#8217;t be processed for at least 60
@@ -1618,22 +1885,22 @@ directive, and is comparable to ngx_http_proxy_module&#8217;s <em>proxy_set_head
 Nginx variables in the value are interpolated.</p></div>
 <div class="paragraph"><p>For example:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt># Application will see a CGI environment "APP_NAME" with value "my super blog".
+<div class="content monospaced">
+<pre># Application will see a CGI environment "APP_NAME" with value "my super blog".
 passenger_set_cgi_param APP_NAME "my super blog";
 
 # Nginx variables are interpolated.
-passenger_set_cgi_param EXTRA_REQUEST_METHOD method=$request_method;</tt></pre>
+passenger_set_cgi_param EXTRA_REQUEST_METHOD method=$request_method;</pre>
 </div></div>
 <div class="paragraph"><p>If you want to set an HTTP header, then you must set it in the CGI environment name
 format, i.e. <em>HTTP_*</em>:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt># !!!THIS IS WRONG!!! Don't do this!
+<div class="content monospaced">
+<pre># !!!THIS IS WRONG!!! Don't do this!
 passenger_set_cgi_param X-Forwarded-For 127.0.0.2;
 
 # Instead, write it like this:
-passenger_set_cgi_param HTTP_X_FORWARDED_FOR 127.0.0.2;</tt></pre>
+passenger_set_cgi_param HTTP_X_FORWARDED_FOR 127.0.0.2;</pre>
 </div></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
 <div class="ulist"><ul>
@@ -1667,10 +1934,10 @@ the final response. This directive allows one to force Nginx to pass those heade
 anyway, similar to how <em>proxy_pass_header</em> works.</p></div>
 <div class="paragraph"><p>For example:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>location / {
+<div class="content monospaced">
+<pre>location / {
    passenger_pass_header X-Accel-Redirect;
-}</tt></pre>
+}</pre>
 </div></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
 <div class="ulist"><ul>
@@ -1711,19 +1978,19 @@ the application response as quickly as possible and will take care of slow clien
 <div class="paragraph"><p>However, keep in mind that enabling this option will make streaming responses
 impossible. Consider for example this piece of Rails code:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>render :text =&gt; lambda { |response, output|
+<div class="content monospaced">
+<pre>render :text =&gt; lambda { |response, output|
     10.times do |i|
         output.write("entry #{i}\n")
         output.flush
         sleep 1
     end
-}</tt></pre>
+}</pre>
 </div></div>
 <div class="paragraph"><p>&#8230;or this piece of Rack code:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>class Response
+<div class="content monospaced">
+<pre>class Response
     def each
         10.times do |i|
             yield("entry #{i}\n")
@@ -1734,7 +2001,7 @@ end
 
 app = lambda do |env|
     [200, { "Content-Type" =&gt; "text/plain" }, Response.new]
-end</tt></pre>
+end</pre>
 </div></div>
 <div class="paragraph"><p>When response buffering is turned on, Phusion Passenger will wait until
 the application is done sending the entire response before forwarding it
@@ -1767,6 +2034,17 @@ In an <em>if</em> configuration scope.
 </ul></div>
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>on</em>.</p></div>
 </div>
+<div class="sect3">
+<h4 id="_passenger_buffer_size">5.5.6. passenger_buffer_size</h4>
+</div>
+<div class="sect3">
+<h4 id="_passenger_buffers">5.5.7. passenger_buffers</h4>
+</div>
+<div class="sect3">
+<h4 id="_passenger_busy_buffer_size">5.5.8. passenger_busy_buffer_size</h4>
+<div class="paragraph"><p>These options have the same effect as proxy_module&#8217;s similarly named options.
+They can be used to modify the maximum allowed HTTP header size.</p></div>
+</div>
 </div>
 <div class="sect2">
 <h3 id="_security_options">5.6. Security options</h3>
@@ -1779,7 +2057,7 @@ The default value is <em>on</em>.</p></div>
 <div class="sect3">
 <h4 id="_passenger_user_lt_username_gt">5.6.2. passenger_user &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 if the file <em>config/environment.rb</em>
+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
 that behavior and explicitly set a user to run the web application as, regardless
 of the ownership of <em>environment.rb</em>/<em>config.ru</em>.</p></div>
@@ -1916,7 +2194,7 @@ The default value is <em>6</em>.</p></div>
 <div class="admonitionblock">
 <table><tr>
 <td class="icon">
-<img src="./images/icons/tip.png" alt="Tip" />
+<img src="./images/icons/tip.png" alt="Tip">
 </td>
 <td class="content">We strongly recommend you to <a href="#reducing_memory_usage">use Ruby Enterprise Edition</a>. This allows you to reduce the memory usage of your Ruby on Rails applications
 by about 33%. And it&#8217;s not hard to install.</td>
@@ -1949,8 +2227,8 @@ the given number of processes will be kept around even when instances are being
 but <a href="#PassengerPreStart">passenger_pre_start</a> explains the rationale behind it.</p></div>
 <div class="paragraph"><p>For example, suppose that you have the following configuration:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>http {
+<div class="content monospaced">
+<pre>http {
     ...
     passenger_max_pool_size 15;
     passenger_pool_idle_time 10;
@@ -1961,7 +2239,7 @@ but <a href="#PassengerPreStart">passenger_pre_start</a> explains the rationale
         root /webapps/foobar/public;
         passenger_min_instances 3;
     }
-}</tt></pre>
+}</pre>
 </div></div>
 <div class="paragraph"><p>When you start Nginx, there are 0 application instances for <em>foobar.com</em>. Things will
 stay that way until someone visits <em>foobar.com</em>. Suppose that there is only 1 visitor.
@@ -2019,7 +2297,7 @@ more often. Since spawning is a relatively slow operation, some visitors may
 notice a small delay when they visit your Rails/Rack website. However, it will also
 free up resources used by applications more quickly.</p></div>
 <div class="paragraph"><p>The optimal value depends on the average time that a visitor spends on a single
-Rails/Rack web page. We recommend a value of <tt>2 * x</tt>, where <tt>x</tt> is the average
+Rails/Rack web page. We recommend a value of <span class="monospaced">2 * x</span>, where <span class="monospaced">x</span> is the average
 number of seconds that a visitor spends on a single Rails/Rack web page. But your
 mileage may vary.</p></div>
 <div class="paragraph"><p>When this value is set to <em>0</em>, application instances will not be shutdown unless
@@ -2082,8 +2360,8 @@ any number of times.</p></div>
 <h5 id="_example_1_basic_usage">Example 1: basic usage</h5>
 <div class="paragraph"><p>Suppose that you have the following web applications.</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>server {
+<div class="content monospaced">
+<pre>server {
     listen 80;
     server_name foo.com;
     root /webapps/foo/public;
@@ -2095,15 +2373,15 @@ server {
     server_name bar.com;
     root /webapps/bar/public;
     passenger_enabled on;
-}</tt></pre>
+}</pre>
 </div></div>
 <div class="paragraph"><p>You want both of them to be pre-started during Nginx startup. The URL for
 foo.com is <em>http://foo.com/</em> (or, equivalently, <em>http://foo.com:80/</em>) and
 the URL for bar.com is <em>http://bar.com:3500/</em>. So we add two passenger_pre_start
 directives, like this:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>server {
+<div class="content monospaced">
+<pre>server {
     listen 80;
     server_name foo.com;
     root /webapps/foo/public;
@@ -2118,38 +2396,38 @@ server {
 }
 
 passenger_pre_start http://foo.com/;           # &lt;--- added
-passenger_pre_start http://bar.com:3500/;      # &lt;--- added</tt></pre>
+passenger_pre_start http://bar.com:3500/;      # &lt;--- added</pre>
 </div></div>
 </div>
 <div class="sect4">
 <h5 id="_example_2_pre_starting_apps_that_are_deployed_in_sub_uris">Example 2: pre-starting apps that are deployed in sub-URIs</h5>
 <div class="paragraph"><p>Suppose that you have a web application deployed in a sub-URI <em>/store</em>, like this:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>server {
+<div class="content monospaced">
+<pre>server {
     listen 80;
     server_name myblog.com;
     root /webapps/wordpress;
     rails_base_uri /store;
-}</tt></pre>
+}</pre>
 </div></div>
 <div class="paragraph"><p>Then specify the <em>server_name</em> valuue followed by the sub-URI, like this:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>server {
+<div class="content monospaced">
+<pre>server {
     listen 80;
     server_name myblog.com;
     root /webapps/wordpress;
     rails_base_uri /store;
 }
 
-passenger_pre_start http://myblog.com/store;    # &lt;----- added</tt></pre>
+passenger_pre_start http://myblog.com/store;    # &lt;----- added</pre>
 </div></div>
 <div class="paragraph"><p>The sub-URI <strong>must</strong> be included; if you don&#8217;t then the directive will have no effect.
 The following example is wrong and won&#8217;t pre-start the store web application:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>passenger_pre_start http://myblog.com/;    # &lt;----- WRONG! Missing "/store" part.</tt></pre>
+<div class="content monospaced">
+<pre>passenger_pre_start http://myblog.com/;    # &lt;----- WRONG! Missing "/store" part.</pre>
 </div></div>
 </div>
 <div class="sect4">
@@ -2162,8 +2440,8 @@ after a few minutes of inactivity. If you don&#8217;t want that to happen, then
 you should combine passenger_pre_start with
 <a href="#PassengerMinInstances">passenger_min_instances</a>, like this:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>server {
+<div class="content monospaced">
+<pre>server {
     listen 80;
     server_name foo.com;
     root /webapps/foo/public;
@@ -2180,7 +2458,7 @@ server {
 }
 
 passenger_pre_start http://foo.com/;
-passenger_pre_start http://bar.com:3500/;</tt></pre>
+passenger_pre_start http://bar.com:3500/;</pre>
 </div></div>
 </div>
 <div class="sect4">
@@ -2205,18 +2483,18 @@ in example 1 resolves to 209.85.227.99; Phusion Passenger will
 send the following HTTP request to 127.0.0.1 port 3500 (and not to 209.85.227.99
 port 3500):</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>HEAD / HTTP/1.1
+<div class="content monospaced">
+<pre>HEAD / HTTP/1.1
 Host: bar.com
-Connection: close</tt></pre>
+Connection: close</pre>
 </div></div>
 <div class="paragraph"><p>Similarly, for example 2, Phusion Passenger will send the following HTTP request
 to 127.0.0.1 port 80:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>HEAD /store HTTP/1.1
+<div class="content monospaced">
+<pre>HEAD /store HTTP/1.1
 Host: myblog.com
-Connection: close</tt></pre>
+Connection: close</pre>
 </div></div>
 </div>
 <div class="sect4">
@@ -2285,7 +2563,7 @@ error messages should be written to instead.</p></div>
 <h3 id="_ruby_on_rails_specific_options">5.9. Ruby on Rails-specific options</h3>
 <div class="sect3">
 <h4 id="RailsEnv">5.9.1. rails_env &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 allows one to specify the default <span class="monospaced">RAILS_ENV</span> value.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
 <div class="ulist"><ul>
 <li>
@@ -2394,7 +2672,7 @@ In an <em>if</em> configuration scope.
 <h3 id="_rack_specific_options">5.10. Rack-specific options</h3>
 <div class="sect3">
 <h4 id="RackEnv">5.10.1. rack_env &lt;string&gt;</h4>
-<div class="paragraph"><p>This option allows one to specify the default <tt>RACK_ENV</tt> value.</p></div>
+<div class="paragraph"><p>This option allows one to specify the default <span class="monospaced">RACK_ENV</span> value.</p></div>
 <div class="paragraph"><p>This option may occur in the following places:</p></div>
 <div class="ulist"><ul>
 <li>
@@ -2439,17 +2717,17 @@ compatibility reasons.</p></div>
 maintenance and troubleshooting.</p></div>
 <div class="sect2">
 <h3 id="_inspecting_memory_usage">6.1. Inspecting memory usage</h3>
-<div class="paragraph"><p>Process inspection tools such as <tt>ps</tt> and <tt>top</tt> are useful, but they
+<div class="paragraph"><p>Process inspection tools such as <span class="monospaced">ps</span> and <span class="monospaced">top</span> are useful, but they
 <a href="http://groups.google.com/group/phusion-passenger/msg/1fd1c233456d3180">rarely show the correct memory usage</a>.
-The real memory usage is usually lower than what <tt>ps</tt> and <tt>top</tt> report.</p></div>
+The real memory usage is usually lower than what <span class="monospaced">ps</span> and <span class="monospaced">top</span> report.</p></div>
 <div class="paragraph"><p>There are many technical reasons why this is so, but an explanation is beyond
 the scope of this Users Guide. We kindly refer the interested reader to
 operating systems literature about <em>virtual memory</em> and <em>copy-on-write</em>.</p></div>
-<div class="paragraph"><p>The tool <tt>passenger-memory-stats</tt> allows one to easily analyze Phusion Passenger&#8217;s
+<div class="paragraph"><p>The tool <span class="monospaced">passenger-memory-stats</span> allows one to easily analyze Phusion Passenger&#8217;s
 and Apache&#8217;s real memory usage. For example:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>[bash@localhost root]# passenger-memory-stats
+<div class="content monospaced">
+<pre>[bash@localhost root]# passenger-memory-stats
 ------------- Apache processes --------------.
 PID    PPID  Threads  VMSize   Private  Name
 ---------------------------------------------.
@@ -2472,7 +2750,7 @@ PID    Threads  VMSize   Private  Name
 23791  1        26.8 MB  2.9 MB   Passenger ApplicationSpawner: /var/www/projects/app1-foobar
 23793  1        26.9 MB  17.1 MB  Rails: /var/www/projects/app1-foobar
 ### Processes: 4
-### Total private dirty RSS: 27.76 M</tt></pre>
+### Total private dirty RSS: 27.76 M</pre>
 </div></div>
 <div class="paragraph"><p>The <em>Private</em> or <em>private dirty RSS</em> field shows the <strong>real</strong> memory usage of processes. Here,
 we see that all the Apache worker processes only take less than 1 MB memory each.
@@ -2481,7 +2759,7 @@ This is a lot less than the 50 MB-ish memory usage as shown in the <em>VMSize</e
 <div class="admonitionblock">
 <table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note" />
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">Private dirty RSS reporting only works on Linux. Unfortunately other operating systems
 don&#8217;t provide facilities for determining processes' private dirty RSS. On non-Linux systems,
@@ -2491,11 +2769,11 @@ the Resident Set Size is reported instead.</td>
 </div>
 <div class="sect2">
 <h3 id="_inspecting_phusion_passenger_8217_s_internal_status">6.2. Inspecting Phusion Passenger&#8217;s internal status</h3>
-<div class="paragraph"><p>One can inspect Phusion Passenger&#8217;s internal status with the tool <tt>passenger-status</tt>.
+<div class="paragraph"><p>One can inspect Phusion Passenger&#8217;s internal status with the tool <span class="monospaced">passenger-status</span>.
 This tool must typically be run as root. For example:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>[bash@localhost root]# passenger-status
+<div class="content monospaced">
+<pre>[bash@localhost root]# passenger-status
 ----------- General information -----------
 max      = 6
 count    = 1
@@ -2504,7 +2782,7 @@ inactive = 1
 
 ----------- Domains -----------
 /var/www/projects/app1-foobar:
-  PID: 9617      Sessions: 0    Processed: 7       Uptime: 2m 23s</tt></pre>
+  PID: 9617      Sessions: 0    Processed: 7       Uptime: 2m 23s</pre>
 </div></div>
 <div class="paragraph"><p>The <em>general information</em> section shows the following information:</p></div>
 <div class="dlist"><dl>
@@ -2545,7 +2823,7 @@ The number of application instances that are currently <strong>not</strong> proc
 requests, i.e. are idle. Idle application instances will be shutdown after a while,
 as can be specified with <a href="#PassengerPoolIdleTime">PassengerPoolIdleTime (Apache)</a>/<a href="#PassengerPoolIdleTime">passenger_pool_idle_time (Nginx)</a> (unless this
 value is set to 0, in which case application instances are never shut down via idle
-time). The value of <em>inactive</em> equals <tt>count - active</tt>.
+time). The value of <em>inactive</em> equals <span class="monospaced">count - active</span>.
 </p>
 </dd>
 </dl></div>
@@ -2584,22 +2862,22 @@ Shows for how long the application instance has been running.
 application instances should be fairly close to each other. For example, this is fairly
 normal:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>  PID: 4281      Sessions: 2      Processed: 7      Uptime: 5m 11s
+<div class="content monospaced">
+<pre>  PID: 4281      Sessions: 2      Processed: 7      Uptime: 5m 11s
   PID: 4268      Sessions: 0      Processed: 5      Uptime: 4m 52s
   PID: 4265      Sessions: 1      Processed: 6      Uptime: 5m 38s
-  PID: 4275      Sessions: 1      Processed: 7      Uptime: 3m 14s</tt></pre>
+  PID: 4275      Sessions: 1      Processed: 7      Uptime: 3m 14s</pre>
 </div></div>
 <div class="paragraph"><p>But if you see a "spike", i.e. an application instance has an unusually high number of
 sessions compared to the others, then there might be a problem:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>  PID: 4281      Sessions: 2      Processed: 7      Uptime: 5m 11s
+<div class="content monospaced">
+<pre>  PID: 4281      Sessions: 2      Processed: 7      Uptime: 5m 11s
   PID: 17468     Sessions: 8 &lt;-+  Processed: 2      Uptime: 4m 47s
   PID: 4265      Sessions: 1   |  Processed: 6      Uptime: 5m 38s
   PID: 4275      Sessions: 1   |  Processed: 7      Uptime: 3m 14s
                                |
-                               +---- "spike"</tt></pre>
+                               +---- "spike"</pre>
 </div></div>
 <div class="paragraph"><p>Possible reasons why spikes can occur:</p></div>
 <div class="olist arabic"><ol class="arabic">
@@ -2633,7 +2911,7 @@ the Apache error log.</p></div>
 <div class="admonitionblock">
 <table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note" />
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">It is safe to kill application instances, even in live environments. Phusion Passenger
 will restart killed application instances, as if nothing bad happened.</td>
@@ -2668,15 +2946,15 @@ Other debugging use cases.
 </ul></div>
 <div class="paragraph"><p>All individual application processes are accessible via HTTP, so you can use standard
 HTTP tools like <em>curl</em>. The exact addresses can be obtained with the command
-<tt>passenger-status --verbose</tt>. These sockets are all bound to 127.0.0.1, but the port
+<span class="monospaced">passenger-status --verbose</span>. These sockets are all bound to 127.0.0.1, but the port
 number is dynamically assigned. As a security measure, the sockets are also protected
 with a process-specific random password, which you can see in the
-<tt>passenger-status --verbose</tt> output. This password must be sent through the
+<span class="monospaced">passenger-status --verbose</span> output. This password must be sent through the
 &#8220;X-Passenger-Connect-Password&#8221; HTTP header.</p></div>
 <div class="paragraph"><p>Example:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>bash# passenger-status --verbose
+<div class="content monospaced">
+<pre>bash# passenger-status --verbose
 ----------- General information -----------
 max      = 6
 count    = 2
@@ -2692,7 +2970,7 @@ Waiting on global queue: 0
       Password: nFfVOX1F8LjZ90HJh28Sd_htJOsgRsNne2QXKf8NIXw
   * PID: 24250   Sessions: 0    Processed: 4       Uptime: 1s
       URL     : http://127.0.0.1:57933
-      Password: _RGXlQ9EGDGJKLevQ_qflUtF1KmxEo2UiRzMwIE1sBY</tt></pre>
+      Password: _RGXlQ9EGDGJKLevQ_qflUtF1KmxEo2UiRzMwIE1sBY</pre>
 </div></div>
 <div class="paragraph"><p>Here we see that the web application <em>rack.test</em> has two processes.
 Process 24235 is accessible via <a href="http://127.0.0.1:58122">http://127.0.0.1:58122</a>, and
@@ -2700,8 +2978,8 @@ process 24250 is accessible via <a href="http://127.0.0.1:57933">http://127.0.0.
 <div class="paragraph"><p>To access 24235 we must send its password, <em>nFfVOX1F8LjZ90HJh28Sd_htJOsgRsNne2QXKf8NIXw</em>,
 through the <em>X-Passenger-Connect-Password</em> HTTP header, like this:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>bash# curl -H "X-Passenger-Connect-Password: nFfVOX1F8LjZ90HJh28Sd_htJOsgRsNne2QXKf8NIXw" http://127.0.0.1:58122/</tt></pre>
+<div class="content monospaced">
+<pre>bash# curl -H "X-Passenger-Connect-Password: nFfVOX1F8LjZ90HJh28Sd_htJOsgRsNne2QXKf8NIXw" http://127.0.0.1:58122/</pre>
 </div></div>
 </div>
 </div>
@@ -2762,8 +3040,8 @@ Please visit the website for details.</p></div>
 The following Capistrano recipe demonstrates Phusion Passenger support.
 It assumes that you&#8217;re using Git as version control system.</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>set :application, "myapp"
+<div class="content monospaced">
+<pre>set :application, "myapp"
 set :domain,      "example.com"
 set :repository,  "ssh://#{domain}/path-to-your-git-repo/#{application}.git"
 set :use_sudo,    false
@@ -2787,7 +3065,7 @@ namespace :deploy do
   task :restart, :roles =&gt; :app do
     run "touch #{current_release}/tmp/restart.txt"
   end
-end</tt></pre>
+end</pre>
 </div></div>
 </div>
 <div class="sect2">
@@ -2804,15 +3082,15 @@ If you have a <em>.bundle/environment.rb</em> in your application root, then Phu
 <li>
 <p>
 Otherwise, if you have a <em>Gemfile</em>, then Phusion Passenger will automatically call
-  <tt>Bundler.setup()</tt> before loading your application.
+  <span class="monospaced">Bundler.setup()</span> before loading your application.
 </p>
 </li>
 </ul></div>
-<div class="paragraph"><p>It&#8217;s possible that your application also calls <tt>Bundler.setup</tt> during loading, e.g. in
+<div class="paragraph"><p>It&#8217;s possible that your application also calls <span class="monospaced">Bundler.setup</span> during loading, e.g. in
 <em>config.ru</em> or in <em>config/boot.rb</em>. This is the case with Rails 3, and is also the case if you
 modified your <em>config/boot.rb</em> according to the
 <a href="http://gembundler.com/rails23.html">Bundler Rails 2.3 instructions</a>.
-This leads to <tt>Bundler.setup</tt> being called twice, once before the application startup file
+This leads to <span class="monospaced">Bundler.setup</span> being called twice, once before the application startup file
 is required and once during application startup. However this is harmless and doesn&#8217;t
 have any negative effects.</p></div>
 <div class="paragraph"><p>Phusion Passenger assumes that you&#8217;re using Bundler &gt;= 0.9.5. If you don&#8217;t want Phusion
@@ -2847,8 +3125,8 @@ move it to <em>/usr/local/passenger/</em>, then do this:</p></div>
 Run the following command:
 </p>
 <div class="listingblock">
-<div class="content">
-<pre><tt>mv /opt/passenger /usr/local/passenger</tt></pre>
+<div class="content monospaced">
+<pre>mv /opt/passenger /usr/local/passenger</pre>
 </div></div>
 </li>
 <li>
@@ -2856,8 +3134,8 @@ Run the following command:
 Edit your Apache configuration file, and set:
 </p>
 <div class="listingblock">
-<div class="content">
-<pre><tt>PassengerRoot /usr/local/passenger</tt></pre>
+<div class="content monospaced">
+<pre>PassengerRoot /usr/local/passenger</pre>
 </div></div>
 </li>
 </ol></div>
@@ -2868,8 +3146,8 @@ Edit your Apache configuration file, and set:
 specific Ruby on Rails version. You can install a specific version with
 this command:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>gem install rails -v X.X.X</tt></pre>
+<div class="content monospaced">
+<pre>gem install rails -v X.X.X</pre>
 </div></div>
 <div class="paragraph"><p>where <em>X.X.X</em> is the version number of Ruby on Rails.</p></div>
 <div class="paragraph"><p>All of these versions will exist in parallel, and will not conflict with each
@@ -2887,7 +3165,7 @@ application, as long as <em>always_restart.txt</em> exists.</p></div>
 <div class="admonitionblock">
 <table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note" />
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">If you&#8217;re just developing a Rails application then you probably don&#8217;t need
 this feature. If you set <em>RailsEnv development</em> in your Apache configuration,
@@ -2921,14 +3199,14 @@ So relative URIs usually don&#8217;t work well with layout templates.</p></div>
 <div class="paragraph"><p>The second and highly recommended way is to always use Rails helper methods to
 output tags for static assets. These helper methods automatically take care
 of prepending the base URI that you&#8217;ve deployed the application to. For images
-there is <tt>image_tag</tt>, for JavaScript there is <tt>javascript_include_tag</tt> and for
-CSS there is <tt>stylesheet_link_tag</tt>. In the above example you would simply remove
+there is <span class="monospaced">image_tag</span>, for JavaScript there is <span class="monospaced">javascript_include_tag</span> and for
+CSS there is <span class="monospaced">stylesheet_link_tag</span>. In the above example you would simply remove
 the <em>&lt;img&gt;</em> HTML tag and replace it with inline Ruby like this:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>&lt;%= image_tag("foo.jpg") %&gt;</tt></pre>
+<div class="content monospaced">
+<pre>&lt;%= image_tag("foo.jpg") %&gt;</pre>
 </div></div>
-<div class="paragraph"><p>This will generate the proper image tag to <tt>$RAILS_ROOT/public/images/foo.jpg</tt>
+<div class="paragraph"><p>This will generate the proper image tag to <span class="monospaced">$RAILS_ROOT/public/images/foo.jpg</span>
 so that your images will always work no matter what sub-URI you&#8217;ve deployed to.</p></div>
 <div class="paragraph"><p>These helper methods are more valuable than you may think. For example they also
 append a timestamp to the URI to better facilitate HTTP caching. For more information,
@@ -2987,8 +3265,8 @@ able to serve, and how it knows what kind of web application it is (e.g. Rails o
 <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 class="content monospaced">
+<pre>dirname(DocumentRoot) + "/config/environment.rb"</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>
@@ -3027,13 +3305,13 @@ Phusion Passenger will look for <em>config.ru</em> instead of <em>config/environ
 Attribution-Share Alike 3.0 Unported License</a>.</p></div>
 <div class="paragraph"><p><span class="image">
 <a class="image" href="http://creativecommons.org/licenses/by-sa/3.0/">
-<img src="images/by_sa.png" alt="images/by_sa.png" />
+<img src="images/by_sa.png" alt="images/by_sa.png">
 </a>
 </span></p></div>
 <div class="paragraph"><p>Phusion Passenger is brought to you by <a href="http://www.phusion.nl/">Phusion</a>.</p></div>
 <div class="paragraph"><p><span class="image">
 <a class="image" href="http://www.phusion.nl/">
-<img src="images/phusion_banner.png" alt="images/phusion_banner.png" />
+<img src="images/phusion_banner.png" alt="images/phusion_banner.png">
 </a>
 </span></p></div>
 <div class="paragraph"><p>Phusion Passenger is a trademark of Hongli Lai &amp; Ninh Bui.</p></div>
@@ -3047,10 +3325,10 @@ Attribution-Share Alike 3.0 Unported License</a>.</p></div>
 <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
-pointed to by <tt>RAILS_ROOT</tt>. For example, take the following directory structure:</p></div>
+pointed to by <span class="monospaced">RAILS_ROOT</span>. For example, take the following directory structure:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>/apps/foo/       &lt;------ This is the Rails application's application root!
+<div class="content monospaced">
+<pre>/apps/foo/       &lt;------ This is the Rails application's application root!
    |
    +- app/
    |   |
@@ -3070,13 +3348,13 @@ pointed to by <tt>RAILS_ROOT</tt>. For example, take the following directory str
    |   |
    |   +- ...
    |
-   +- ...</tt></pre>
+   +- ...</pre>
 </div></div>
 <div class="paragraph"><p>In case of Rack applications, this is the directory that contains <em>config.ru</em>.
 For example, take the following directory structure:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>/apps/bar/      &lt;----- This is the Rack application's application root!
+<div class="content monospaced">
+<pre>/apps/bar/      &lt;----- This is the Rack application's application root!
    |
    +- public/
    |    |
@@ -3084,13 +3362,13 @@ For example, take the following directory structure:</p></div>
    |
    +- config.ru
    |
-   +- ...</tt></pre>
+   +- ...</pre>
 </div></div>
 <div class="paragraph"><p>In case of Python (WSGI) applications, this is the directory that contains
 <em>passenger_wsgi.py</em>. For example, take the following directory structure:</p></div>
 <div class="listingblock">
-<div class="content">
-<pre><tt>/apps/baz/      &lt;----- This is the WSGI application's application root!
+<div class="content monospaced">
+<pre>/apps/baz/      &lt;----- This is the WSGI application's application root!
    |
    +- public/
    |    |
@@ -3098,7 +3376,7 @@ For example, take the following directory structure:</p></div>
    |
    +- passenger_wsgi.py
    |
-   +- ...</tt></pre>
+   +- ...</pre>
 </div></div>
 </div>
 </div>
@@ -3135,7 +3413,7 @@ programmers jargon, Phusion Passenger calls fork(), but not exec().</p></div>
 <div class="admonitionblock">
 <table><tr>
 <td class="icon">
-<img src="./images/icons/note.png" alt="Note" />
+<img src="./images/icons/note.png" alt="Note">
 </td>
 <td class="content">Smart spawning is supported for all Ruby applications but not for WSGI applications.</td>
 </tr></table>
@@ -3144,8 +3422,8 @@ programmers jargon, Phusion Passenger calls fork(), but not exec().</p></div>
 because each worker process has its own private copy of the Rails application
 as well as the Rails framework. This wastes memory as well as startup time.</p></div>
 <div class="paragraph"><p><span class="image">
-<img src="images/conservative_spawning.png" alt="Worker processes and conservative spawning" />
-</span><br />
+<img src="images/conservative_spawning.png" alt="Worker processes and conservative spawning">
+</span><br>
 <em>Figure: Worker processes and conservative spawning. Each worker process has its
 own private copy of the application code and Rails framework code.</em></p></div>
 <div class="paragraph"><p>It is possible to make the different worker processes share the memory occupied
@@ -3170,8 +3448,8 @@ processes will share as much common
 memory as possible. That is, they will all share the same application and Rails
 framework code.</p></div>
 <div class="paragraph"><p><span class="image">
-<img src="images/smart-lv2.png" alt="images/smart-lv2.png" />
-</span><br />
+<img src="images/smart-lv2.png" alt="images/smart-lv2.png">
+</span><br>
 <em>Figure: Worker processes and the smart-lv2 spawn method. All worker processes,
 as well as the ApplicationSpawner, share the same application code and Rails
 framework code.</em></p></div>
@@ -3255,7 +3533,7 @@ may potentially cause problems.</p></div>
 <div class="paragraph"><p>The problem commonly involves socket connections that are unintentially being
 shared. You can fix it by closing and reestablishing the connection when Phusion
 Passenger is creating a new worker process. Phusion Passenger provides the API
-call <tt>PhusionPassenger.on_event(:starting_worker_process)</tt> to do so. So you
+call <span class="monospaced">PhusionPassenger.on_event(:starting_worker_process)</span> to do so. So you
 could insert the following code in your <em>environment.rb</em>:</p></div>
 <div class="listingblock">
 <div class="content"><!-- Generator: GNU source-highlight 2.11.1
@@ -3281,22 +3559,22 @@ encounter any database issues when using smart spawning mode.</p></div>
 <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>
 <div class="literalblock">
-<div class="content">
-<pre><tt>+--------------------+
+<div class="content monospaced">
+<pre>+--------------------+
 | ApplicationSpawner |-----------[Memcached server]
-+--------------------+</tt></pre>
++--------------------+</pre>
 </div></div>
 <div class="paragraph"><p>Phusion Passenger then proceeds with creating a new Rails worker process, which
 is to process incoming HTTP requests. The result will look like this:</p></div>
 <div class="literalblock">
-<div class="content">
-<pre><tt>+--------------------+
+<div class="content monospaced">
+<pre>+--------------------+
 | ApplicationSpawner |------+----[Memcached server]
 +--------------------+      |
                             |
 +--------------------+      |
 | Worker process 1   |-----/
-+--------------------+</tt></pre>
++--------------------+</pre>
 </div></div>
 <div class="paragraph"><p>Since a <em>fork()</em> makes a (virtual) complete copy of a process, all its file
 descriptors will be copied as well. What we see here is that ApplicationSpawner
@@ -3305,8 +3583,8 @@ and Worker process 1 both share the same connection to Memcached.</p></div>
 spawn another worker process. It does so by forking ApplicationSpawner. The
 result is now as follows:</p></div>
 <div class="literalblock">
-<div class="content">
-<pre><tt>+--------------------+
+<div class="content monospaced">
+<pre>+--------------------+
 | ApplicationSpawner |------+----[Memcached server]
 +--------------------+      |
                             |
@@ -3316,7 +3594,7 @@ result is now as follows:</p></div>
                             |
 +--------------------+      |
 | Worker process 2   |-----/
-+--------------------+</tt></pre>
++--------------------+</pre>
 </div></div>
 <div class="paragraph"><p>As you can see, Worker process 1 and Worker process 2 have the same Memcache
 connection.</p></div>
@@ -3332,8 +3610,8 @@ recognize. In other words: the data from both handlers get interleaved. And thus
 Memcached is forced to handle this as an error.</p></div>
 <div class="paragraph"><p>This problem can be solved by reestablishing the connection to Memcached after forking:</p></div>
 <div class="literalblock">
-<div class="content">
-<pre><tt>+--------------------+
+<div class="content monospaced">
+<pre>+--------------------+
 | ApplicationSpawner |------+----[Memcached server]
 +--------------------+      |                   |
                             |                   |
@@ -3347,7 +3625,7 @@ Memcached is forced to handle this as an error.</p></div>
 | Worker process 2   |-----/      connection    |
 +--------------------+                          |
           |                                     |
-          +-------------------------------------+</tt></pre>
+          +-------------------------------------+</pre>
 </div></div>
 <div class="paragraph"><p>Worker process 2 now has its own, separate communication channel with Memcached.
 The code in <em>environment.rb</em> looks like this:</p></div>
@@ -3385,7 +3663,7 @@ Memcached example, doesn&#8217;t help.</p></div>
 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.
 You need to revive them when a new worker process is created. Use the
-<tt>:starting_worker_process</tt> event that Phusion Passenger provides, like this:</p></div>
+<span class="monospaced">:starting_worker_process</span> event that Phusion Passenger provides, like this:</p></div>
 <div class="listingblock">
 <div class="content"><!-- Generator: GNU source-highlight 2.11.1
 by Lorenzo Bettini
@@ -3417,16 +3695,16 @@ of <em>active_record/base.rb</em> located in <em>RAILS_ROOT/lib/patches</em>, an
 <em>RAILS_ROOT/lib/patches</em> comes first in the Ruby load path. When conservative
 spawning is used, the patched version of <em>base.rb</em> is properly loaded. When
 <em>smart</em> (not <em>smart-lv2</em>) spawning is used, the original <em>base.rb</em> is used
-because it was already loaded, so a subsequent <tt>require "active_record/base"</tt>
+because it was already loaded, so a subsequent <span class="monospaced">require "active_record/base"</span>
 has no effect.</p></div>
 </div>
 </div>
 </div>
 </div>
-<div id="footnotes"><hr /></div>
+<div id="footnotes"><hr></div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2010-12-05 20:52:52 CET
+Last updated 2011-08-03 11:00:00 CEST
 </div>
 </div>
 </body>