passenger 5.0.6 → 5.0.7

data/doc/Users guide Apache.html

@@ -1166,18 +1166,19 @@ using the command line.</p></div>
 <div class="foo toclevel4"><a href="#PassengerRuby">7.4.1. PassengerRuby &lt;filename&gt;</a></div>
 <div class="foo toclevel4"><a href="#_passengerpython_lt_filename_gt">7.4.2. PassengerPython &lt;filename&gt;</a></div>
 <div class="foo toclevel4"><a href="#_passengernodejs_lt_filename_gt">7.4.3. PassengerNodejs &lt;filename&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerAppEnv">7.4.4. PassengerAppEnv &lt;string&gt;</a></div>
-<div class="foo toclevel4"><a href="#rails_env">7.4.5. RailsEnv &lt;string&gt;</a></div>
-<div class="foo toclevel4"><a href="#rack_env">7.4.6. RackEnv &lt;string&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerAppRoot">7.4.7. PassengerAppRoot &lt;path/to/root&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerAppGroupName">7.4.8. PassengerAppGroupName &lt;name&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerAppType">7.4.9. PassengerAppType &lt;name&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerStartupFile">7.4.10. PassengerStartupFile &lt;filename&gt;</a></div>
-<div class="foo toclevel4"><a href="#_passengerrestartdir_lt_directory_gt">7.4.11. PassengerRestartDir &lt;directory&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerSpawnMethod">7.4.12. PassengerSpawnMethod &lt;string&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerLoadShellEnvvars">7.4.13. PassengerLoadShellEnvvars &lt;on|off&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerRollingRestarts">7.4.14. PassengerRollingRestarts &lt;on|off&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerResistDeploymentErrors">7.4.15. PassengerResistDeploymentErrors &lt;on|off&gt;</a></div>
+<div class="foo toclevel4"><a href="#_passengermeteorappsettings_lt_filename_gt">7.4.4. PassengerMeteorAppSettings &lt;filename&gt;</a></div>
+<div class="foo toclevel4"><a href="#PassengerAppEnv">7.4.5. PassengerAppEnv &lt;string&gt;</a></div>
+<div class="foo toclevel4"><a href="#rails_env">7.4.6. RailsEnv &lt;string&gt;</a></div>
+<div class="foo toclevel4"><a href="#rack_env">7.4.7. RackEnv &lt;string&gt;</a></div>
+<div class="foo toclevel4"><a href="#PassengerAppRoot">7.4.8. PassengerAppRoot &lt;path/to/root&gt;</a></div>
+<div class="foo toclevel4"><a href="#PassengerAppGroupName">7.4.9. PassengerAppGroupName &lt;name&gt;</a></div>
+<div class="foo toclevel4"><a href="#PassengerAppType">7.4.10. PassengerAppType &lt;name&gt;</a></div>
+<div class="foo toclevel4"><a href="#PassengerStartupFile">7.4.11. PassengerStartupFile &lt;filename&gt;</a></div>
+<div class="foo toclevel4"><a href="#_passengerrestartdir_lt_directory_gt">7.4.12. PassengerRestartDir &lt;directory&gt;</a></div>
+<div class="foo toclevel4"><a href="#PassengerSpawnMethod">7.4.13. PassengerSpawnMethod &lt;string&gt;</a></div>
+<div class="foo toclevel4"><a href="#PassengerLoadShellEnvvars">7.4.14. PassengerLoadShellEnvvars &lt;on|off&gt;</a></div>
+<div class="foo toclevel4"><a href="#PassengerRollingRestarts">7.4.15. PassengerRollingRestarts &lt;on|off&gt;</a></div>
+<div class="foo toclevel4"><a href="#PassengerResistDeploymentErrors">7.4.16. PassengerResistDeploymentErrors &lt;on|off&gt;</a></div>
 <div class="foo toclevel3"><a href="#_security_options">7.5. Security options</a></div>
 <div class="foo toclevel4"><a href="#PassengerUserSwitching">7.5.1. PassengerUserSwitching &lt;on|off&gt;</a></div>
 <div class="foo toclevel4"><a href="#PassengerUser">7.5.2. PassengerUser &lt;username&gt;</a></div>
@@ -1261,7 +1262,7 @@ using the command line.</p></div>
 <div class="foo toclevel4"><a href="#_caveats_amp_troubleshooting">10.1.3. Caveats &amp; troubleshooting</a></div>
 <div class="foo toclevel4"><a href="#finding_out_app_user">10.1.4. Finding out what user an application is running as</a></div>
 <div class="foo toclevel3"><a href="#reducing_memory_usage">10.2. Copy-on-write memory support (reducing memory consumption of Ruby applications)</a></div>
-<div class="foo toclevel3"><a href="#capistrano">10.3. Capistrano recipe</a></div>
+<div class="foo toclevel3"><a href="#tuning_sse_websockets">10.3. Tuning for Server Sent Events and WebSockets</a></div>
 <div class="foo toclevel3"><a href="#bundler_support">10.4. Bundler support</a></div>
 <div class="foo toclevel4"><a href="#add_passenger_to_gemfile">10.4.1. Does Phusion Passenger itself need to be added to the Gemfile?</a></div>
 <div class="foo toclevel3"><a href="#_installing_multiple_ruby_on_rails_versions">10.5. Installing multiple Ruby on Rails versions</a></div>
@@ -1634,6 +1635,25 @@ sudo apt-get update</pre>
 </div>
 </div>
 </li>
+<li>
+<p>
+(Optional) If using <span class="monospaced">unattended-upgrades</span>, add our APT repository to the list of <span class="monospaced">Allowed-Origins</span> for upgrades, <span class="monospaced">/etc/apt/apt.conf.d/50unattended-upgrades</span>:
+</p>
+<div class="listingblock">
+<div class="content">
+<!-- Generator: GNU source-highlight 2.11.1
+by Lorenzo Bettini
+http://www.lorenzobettini.it
+http://www.gnu.org/software/src-highlite -->
+<pre><tt><span style="color: #990000">//</span> Automatically upgrade packages from these <span style="color: #990000">(</span>origin<span style="color: #990000">:</span>archive<span style="color: #990000">)</span> pairs
+Unattended-Upgrade<span style="color: #990000">::</span>Allowed-Origins {
+  <span style="color: #990000">//</span> To check <span style="color: #FF0000">"Origin:"</span> and <span style="color: #FF0000">"Suite:"</span><span style="color: #990000">,</span> you could use e<span style="color: #990000">.</span>g<span style="color: #990000">.:</span>
+  <span style="color: #990000">//</span> grep <span style="color: #FF0000">"Origin</span><span style="color: #CC33CC">\|</span><span style="color: #FF0000">Suite"</span> /var/lib/apt/lists/oss-binaries<span style="color: #990000">.</span>phusionpassenger<span style="color: #990000">.</span>com<span style="color: #990000">*</span>
+  <span style="color: #FF0000">"Phusion:stable"</span><span style="color: #990000">;</span>
+}<span style="color: #990000">;</span></tt></pre>
+</div>
+</div>
+</li>
 </ol></div>
 </div>
 <div class="sect3">
@@ -1711,6 +1731,7 @@ sudo apache2ctl stop; sudo apache2ctl start</pre>
 </ol></div>
 </dd>
 </dl></div>
+<div class="paragraph"><p>You can now proceed with a chapter for Deploying your (specific type of) application.</p></div>
 </div>
 </div>
 <div class="sect2">
@@ -3457,7 +3478,13 @@ Do you want to know which command to use for a different Ruby interpreter? 'rvm
 <div class="paragraph"><p>This option allows one to specify the Node.js command to use. See <a href="#PassengerRuby">PassengerRuby</a> for more information. The default value is <em>node</em>, meaning that the Node.js command will be looked up according to the <span class="monospaced">PATH</span> environment variable.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerAppEnv"></span><h4 data-comment-topic="passengerappenv-string--s3ojlc" data-anchor="PassengerAppEnv">7.4.4. PassengerAppEnv &lt;string&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_passengermeteorappsettings_lt_filename_gt"></span><h4 data-comment-topic="passengermeteorappsettings-filename--inl1bd" data-anchor="_passengermeteorappsettings_lt_filename_gt">7.4.4. PassengerMeteorAppSettings &lt;filename&gt;</h4>
+<div class="paragraph"><p><strong>Introduced in version 5.0.7.</strong></p></div>
+<div class="paragraph"><p>When using a Meteor application in non-bundled mode, use this option to specify a (JSON) file with settings for the application. Meteor will be started with the <span class="monospaced">--settings</span> parameter set to this option.</p></div>
+<div class="paragraph"><p>N.B. For bundled mode, Meteor requires you to put applications settings in the <span class="monospaced">METEOR_SETTINGS</span> environment variable.</p></div>
+</div>
+<div class="sect3">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerAppEnv"></span><h4 data-comment-topic="passengerappenv-string--s3ojlc" data-anchor="PassengerAppEnv">7.4.5. PassengerAppEnv &lt;string&gt;</h4>
 <div class="paragraph"><p>This option sets the value of the following environment variables:</p></div>
 <div class="ulist"><ul>
 <li>
@@ -3516,15 +3543,15 @@ In <em>.htaccess</em>, if <span class="monospaced">AllowOverride Options</span>
 <div class="paragraph"><p>In each place, it may be specified at most once.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="rails_env"></span><h4 data-comment-topic="railsenv-string--1b0xxvu" data-anchor="rails_env">7.4.5. RailsEnv &lt;string&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="rails_env"></span><h4 data-comment-topic="railsenv-string--1b0xxvu" data-anchor="rails_env">7.4.6. RailsEnv &lt;string&gt;</h4>
 <div class="paragraph"><p>An alias for <a href="#PassengerAppEnv">PassengerAppEnv</a>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="rack_env"></span><h4 data-comment-topic="rackenv-string--vve9py" data-anchor="rack_env">7.4.6. RackEnv &lt;string&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="rack_env"></span><h4 data-comment-topic="rackenv-string--vve9py" data-anchor="rack_env">7.4.7. RackEnv &lt;string&gt;</h4>
 <div class="paragraph"><p>An alias for <a href="#PassengerAppEnv">PassengerAppEnv</a>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerAppRoot"></span><h4 data-comment-topic="passengerapproot-path-to-root--uf24yd" data-anchor="PassengerAppRoot">7.4.7. PassengerAppRoot &lt;path/to/root&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerAppRoot"></span><h4 data-comment-topic="passengerapproot-path-to-root--uf24yd" data-anchor="PassengerAppRoot">7.4.8. PassengerAppRoot &lt;path/to/root&gt;</h4>
 <div class="paragraph"><p>By default, Phusion Passenger assumes that the application’s root directory
 is the parent directory of the <em>public</em> directory. This option allows one to
 specify the application’s root independently from the DocumentRoot, which
@@ -3567,8 +3594,8 @@ In <em>.htaccess</em>, if <span class="monospaced">AllowOverride Options</span>
 </div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerAppGroupName"></span><h4 data-comment-topic="passenger-app-group-name-name--6unn5c" data-anchor="PassengerAppGroupName">7.4.8. PassengerAppGroupName &lt;name&gt;</h4>
-<div class="paragraph"><p>Sets the name of the application group that the current application should belong to. Its default value is the <a href="#PassengerRoot">application root</a>, plus (if it is set), the <a href="#PassengerAppEnv">application environment name</a>.</p></div>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerAppGroupName"></span><h4 data-comment-topic="passenger-app-group-name-name--6unn5c" data-anchor="PassengerAppGroupName">7.4.9. PassengerAppGroupName &lt;name&gt;</h4>
+<div class="paragraph"><p>Sets the name of the application group that the current application should belong to. Its default value is the <a href="#application_root">application root</a>, plus (if it is set), the <a href="#PassengerAppEnv">application environment name</a>.</p></div>
 <div class="paragraph"><p>Phusion Passenger stores and caches most application spawning settings — such as environment variables, process limits, etc — on a per-app-group-name basis. This means that if you want to start two versions of your application, with each version having different environment variables, then you must assign them under different application group names.</p></div>
 <div class="paragraph"><p>For example, consider a situation in which you are running multiple versions of the same app, with each version intended for a different customer. You use the <span class="monospaced">CUSTOMER_NAME</span> environment variable to tell the app which customer that version should serve.</p></div>
 <div class="listingblock">
@@ -3652,7 +3679,7 @@ In <em>.htaccess</em>, if <span class="monospaced">AllowOverride Options</span>
 <div class="paragraph"><p>In each place, it may be specified at most once.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerAppType"></span><h4 data-comment-topic="passengerapptype-name--62jzqf" data-anchor="PassengerAppType">7.4.9. PassengerAppType &lt;name&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerAppType"></span><h4 data-comment-topic="passengerapptype-name--62jzqf" data-anchor="PassengerAppType">7.4.10. PassengerAppType &lt;name&gt;</h4>
 <div class="paragraph"><p><strong>Introduced in version 4.0.25.</strong></p></div>
 <div class="paragraph"><p>By default, Phusion Passenger autodetects the type of the application, e.g. whether it’s a Ruby, Python, Node.js or Meteor app. If it’s unable to autodetect the type of the application (e.g. because you’ve specified a custom <a href="#PassengerStartupFile">PassengerStartupFile</a>) then you can use this option to force Phusion Passenger to recognize the application as a specific type.</p></div>
 <div class="paragraph"><p>Allowed values are:</p></div>
@@ -3718,7 +3745,7 @@ In <em>.htaccess</em>.
 </div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerStartupFile"></span><h4 data-comment-topic="passengerstartupfile-filename--14vhvn9" data-anchor="PassengerStartupFile">7.4.10. PassengerStartupFile &lt;filename&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerStartupFile"></span><h4 data-comment-topic="passengerstartupfile-filename--14vhvn9" data-anchor="PassengerStartupFile">7.4.11. PassengerStartupFile &lt;filename&gt;</h4>
 <div class="paragraph"><p><strong>Introduced in version 4.0.25.</strong></p></div>
 <div class="paragraph"><p>This option specifies the startup file that Phusion Passenger should use when loading the application.</p></div>
 <div class="paragraph"><p>Every application has a <strong>startup file</strong> or <strong>entry point file</strong>: a file where the application begins execution. Some languages have widely accepted conventions about how such a file should be called (e.g. Ruby, with its <span class="monospaced">config.ru</span>). Other languages have somewhat-accepted conventions (e.g. Node.js, with its <span class="monospaced">app.js</span>). In these cases, Phusion Passenger reuses these conventions, and executes applications through those files.</p></div>
@@ -3807,7 +3834,7 @@ In <em>.htaccess</em>.
 </div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_passengerrestartdir_lt_directory_gt"></span><h4 data-comment-topic="passengerrestartdir-directory--1fmhmv0" data-anchor="_passengerrestartdir_lt_directory_gt">7.4.11. PassengerRestartDir &lt;directory&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_passengerrestartdir_lt_directory_gt"></span><h4 data-comment-topic="passengerrestartdir-directory--1fmhmv0" data-anchor="_passengerrestartdir_lt_directory_gt">7.4.12. PassengerRestartDir &lt;directory&gt;</h4>
 <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
@@ -3881,7 +3908,7 @@ allow the attacker to cause a Denial-of-Service.</p>
 directory that’s readable by Apache, but only writable by administrators.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerSpawnMethod"></span><h4 data-comment-topic="passengerspawnmethod-string--sodg2y" data-anchor="PassengerSpawnMethod">7.4.12. PassengerSpawnMethod &lt;string&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerSpawnMethod"></span><h4 data-comment-topic="passengerspawnmethod-string--sodg2y" data-anchor="PassengerSpawnMethod">7.4.13. PassengerSpawnMethod &lt;string&gt;</h4>
 <div class="admonitionblock">
 <table><tr>
 <td class="icon">
@@ -3964,7 +3991,7 @@ In a virtual host configuration block.
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>smart</em>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerLoadShellEnvvars"></span><h4 data-comment-topic="passengerloadshellenvvars-on-off--1290yz1" data-anchor="PassengerLoadShellEnvvars">7.4.13. PassengerLoadShellEnvvars &lt;on|off&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerLoadShellEnvvars"></span><h4 data-comment-topic="passengerloadshellenvvars-on-off--1290yz1" data-anchor="PassengerLoadShellEnvvars">7.4.14. PassengerLoadShellEnvvars &lt;on|off&gt;</h4>
 <div class="paragraph"><p><strong>Introduced in version 4.0.20.</strong></p></div>
 <div class="paragraph"><p>Enables or disables the loading of shell environment variables before spawning the application.</p></div>
 <div class="paragraph"><p>If this option is turned on, and the user’s shell is <span class="monospaced">bash</span>, then applications are loaded by running them with <span class="monospaced">bash -l -c</span>. Otherwise, they are loaded by running them directly from the <span class="monospaced">PassengerHelperAgent</span> process.</p></div>
@@ -3994,7 +4021,7 @@ In <em>.htaccess</em>, if <span class="monospaced">AllowOverride Options</span>
 <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">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerRollingRestarts"></span><h4 data-comment-topic="passengerrollingrestarts" data-anchor="PassengerRollingRestarts">7.4.14. PassengerRollingRestarts &lt;on|off&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerRollingRestarts"></span><h4 data-comment-topic="passengerrollingrestarts" data-anchor="PassengerRollingRestarts">7.4.15. PassengerRollingRestarts &lt;on|off&gt;</h4>
 <div class="paragraph"><p><strong>This feature is only available in <a href="https://www.phusionpassenger.com/enterprise">Phusion Passenger Enterprise</a>. It was introduced in version 3.0.0. <a href="https://www.phusionpassenger.com/download">Buy Phusion Passenger Enterprise here.</a></strong></p></div>
 <div class="paragraph"><p>Enables or disables support for rolling restarts through restart.txt. Normally when you
 restart an application by touching restart.txt, Phusion Passenger would
@@ -4081,7 +4108,7 @@ In <em>.htaccess</em>, if <span class="monospaced">AllowOverride Options</span>
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>off</em>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerResistDeploymentErrors"></span><h4 data-comment-topic="passengerresistdeploymenterrors" data-anchor="PassengerResistDeploymentErrors">7.4.15. PassengerResistDeploymentErrors &lt;on|off&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerResistDeploymentErrors"></span><h4 data-comment-topic="passengerresistdeploymenterrors" data-anchor="PassengerResistDeploymentErrors">7.4.16. PassengerResistDeploymentErrors &lt;on|off&gt;</h4>
 <div class="paragraph"><p><strong>This feature is only available in <a href="https://www.phusionpassenger.com/enterprise">Phusion Passenger Enterprise</a>. It was introduced in version 3.0.0. <a href="https://www.phusionpassenger.com/download">Buy Phusion Passenger Enterprise here.</a></strong></p></div>
 <div class="paragraph"><p>Enables or disables resistance against deployment errors.</p></div>
 <div class="paragraph"><p>Suppose you’ve upgraded your application and you’ve issues a command to restart it (by touching restart.txt), but the application code contains an error that prevents Phusion Passenger from successfully spawning a process (e.g. a syntax error). Phusion Passenger would normally display an error message in response to this.</p></div>
@@ -6599,39 +6626,29 @@ MRI Ruby &gt;= 2.0. Versions prior to 2.0 did not have a copy-on-write friendly
 </ul></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="capistrano"></span><h3 data-comment-topic="capistrano-recipe-syzgo7" data-anchor="capistrano">10.3. Capistrano recipe</h3>
-<div class="paragraph"><p>Phusion Passenger can be combined with <a href="http://capify.org/">Capistrano</a>.
-The following Capistrano recipe demonstrates Phusion Passenger support.
-It assumes that you’re using Git as version control system.</p></div>
-<div class="listingblock">
-<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
-set :deploy_to,   "/path-to-your-web-app-directory/#{application}"
-set :scm,         "git"
-
-role :app, domain
-role :web, domain
-role :db,  domain, :primary =&gt; true
-
-namespace :deploy do
-  task :start, :roles =&gt; :app do
-    run "touch #{current_release}/tmp/restart.txt"
-  end
-
-  task :stop, :roles =&gt; :app do
-    # Do nothing.
-  end
-
-  desc "Restart Application"
-  task :restart, :roles =&gt; :app do
-    run "touch #{current_release}/tmp/restart.txt"
-  end
-end</pre>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="tuning_sse_websockets"></span><h3 data-comment-topic="tuning-for-server-sent-events-and-websockets-1hy6qa9" data-anchor="tuning_sse_websockets">10.3. Tuning for Server Sent Events and WebSockets</h3>
+<div class="paragraph"><p>Phusion Passenger supports Server Sent Events (SSE) and WebSockets out of the box with no configuration, but there are some things you need to know.</p></div>
+<div class="paragraph"><p>First, WebSockets are <a href="https://github.com/phusion/passenger/issues/1202">not yet supported when using the Apache integration mode</a>.</p></div>
+<div class="paragraph"><p>Second, for Ruby apps only, you need to insert a configuration snippet inside your <span class="monospaced">config.ru</span>:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre><strong>if</strong> defined?(PhusionPassenger)
+  PhusionPassenger.advertised_concurrency_level = 0
+<strong>end</strong></pre>
 </div>
 </div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="./images/icons/note.png" alt="Note">
+</td>
+<td class="content">
+<div class="paragraph"><p>This snippet tells Passenger that your Ruby app will handle SSE and WebSockets. In response, Passenger will adjust the connection concurrency settings for your app. Without this configuration snippet, SSE and WebSockets still work, but with degraded performance.</p></div>
+<div class="paragraph"><p>This configuration snippet is currently necessary because of the way Passenger is implemented. We are <a href="https://github.com/phusion/passenger/issues/1195">working on improving this mechanism</a>. One day, the above configuration snippet will no longer be necessary. For now, you should include the above configuration snippet for optimal SSE and WebSocket performance.</p></div>
+</td>
+</tr></table>
+</div>
+<div class="paragraph"><p>Finally, you can find Passenger SSE and WebSocket demo apps on <a href="https://www.phusionpassenger.com/documentation_and_support">the Passenger documentation overview page</a>, under section "Demos".</p></div>
 </div>
 <div class="sect2">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="bundler_support"></span><h3 data-comment-topic="bundler-support-cf72ih" data-anchor="bundler_support">10.4. Bundler support</h3>
@@ -7478,25 +7495,13 @@ Phusion Passenger’s installer, build system and administration tools are writt
 <p>
 Certain internally used tools, such as the crash handler (which generates a backtrace in case Phusion Passenger crash) and the prespawn script (used to implement
 <a href="#PassengerPreStart">PassengerPreStart</a>)
-are written in Ruby as well.
-</p>
-</li>
-<li>
-<p>
-Ruby web application support is implemented in Ruby.
-</p>
-</li>
-<li>
-<p>
-If you use <a href="#flying_passenger">Flying Passenger</a>, then the Flying Passenger daemon is written in Ruby. The daemon is a small (less than 500 lines of code) and offloads most tasks to the C++ core.
-</p>
-</li>
-<li>
-<p>
-If you use <a href="Users%20guide%20Standalone.html">Phusion Passenger Standalone</a>, then the frontend (the <span class="monospaced">passenger</span> command) is written in Ruby. The frontend is small (less than 1500 lines of code) and offloads most tasks to the C++ core.
 </p>
 </li>
 </ul></div>
+<div class="paragraph"><p>are written in Ruby as well.
+ * Ruby web application support is implemented in Ruby.
+ * If you use <a href="#flying_passenger">Flying Passenger</a>, then the Flying Passenger daemon is written in Ruby. The daemon is a small (less than 500 lines of code) and offloads most tasks to the C<span class="monospaced"> core.
+ * If you use <a href="Users%20guide%20Standalone.html">Phusion Passenger Standalone</a>, then the frontend (the <span class="monospaced">passenger</span> command) is written in Ruby. The frontend is small (less than 1500 lines of code) and offloads most tasks to the C</span> core.</p></div>
 <div class="paragraph"><p>Other than the aforementioned aspects, Phusion Passenger does not use Ruby during normal operation. For example, if you run Python WSGI web applications on Phusion Passenger, then there will be (almost) no Ruby code running on the system.</p></div>
 </div>
 <div class="sect3">
@@ -8275,7 +8280,8 @@ echo <span style="color: #FF0000">'export PATH=/usr/local/bin:$PATH'</span> <spa
 <td class="icon">
 <img src="./images/icons/note.png" alt="Note">
 </td>
-<td class="content">Depending on the system, the bashrc file may have a different filename. On Debian and Ubuntu, it’s <span class="monospaced">/etc/bash.bashrc</span>.</td>
+<td class="content">Depending on the system, the bashrc file may have a different filename. On Debian and Ubuntu, it’s <span class="monospaced">/etc/bash.bashrc</span>.
+NOTE: Make sure your <span class="monospaced">~/.bashrc</span> is actually included by your <span class="monospaced">~/.profile</span>, which might not be the case if you created the user with <span class="monospaced">useradd</span> instead of <span class="monospaced">adduser</span> for example</td>
 </tr></table>
 </div>
 </div>
@@ -8351,7 +8357,7 @@ When running Apache, use the <span class="monospaced">PassEnv</span> and <span c
 </li>
 <li>
 <p>
-When running Nginx, use the <a href="#passenger_env_var">passenger_env_var</a> directive.
+When running Nginx, use the <a href="#PassengerEnvVar">passenger_env_var</a> directive.
 </p>
 </li>
 <li>

data/doc/Users guide Apache.idmap.txt

@@ -136,29 +136,31 @@
 
 7.4.3. PassengerNodejs <filename>	=>	passengernodejs-filename--2mjb1j
 
-7.4.4. PassengerAppEnv <string>	=>	passengerappenv-string--s3ojlc
+7.4.4. PassengerMeteorAppSettings <filename>	=>	passengermeteorappsettings-filename--inl1bd
 
-7.4.5. RailsEnv <string>	=>	railsenv-string--1b0xxvu
+7.4.5. PassengerAppEnv <string>	=>	passengerappenv-string--s3ojlc
 
-7.4.6. RackEnv <string>	=>	rackenv-string--vve9py
+7.4.6. RailsEnv <string>	=>	railsenv-string--1b0xxvu
 
-7.4.7. PassengerAppRoot <path/to/root>	=>	passengerapproot-path-to-root--uf24yd
+7.4.7. RackEnv <string>	=>	rackenv-string--vve9py
 
-7.4.8. PassengerAppGroupName <name>	=>	passenger-app-group-name-name--6unn5c
+7.4.8. PassengerAppRoot <path/to/root>	=>	passengerapproot-path-to-root--uf24yd
 
-7.4.9. PassengerAppType <name>	=>	passengerapptype-name--62jzqf
+7.4.9. PassengerAppGroupName <name>	=>	passenger-app-group-name-name--6unn5c
 
-7.4.10. PassengerStartupFile <filename>	=>	passengerstartupfile-filename--14vhvn9
+7.4.10. PassengerAppType <name>	=>	passengerapptype-name--62jzqf
 
-7.4.11. PassengerRestartDir <directory>	=>	passengerrestartdir-directory--1fmhmv0
+7.4.11. PassengerStartupFile <filename>	=>	passengerstartupfile-filename--14vhvn9
 
-7.4.12. PassengerSpawnMethod <string>	=>	passengerspawnmethod-string--sodg2y
+7.4.12. PassengerRestartDir <directory>	=>	passengerrestartdir-directory--1fmhmv0
 
-7.4.13. PassengerLoadShellEnvvars <on|off>	=>	passengerloadshellenvvars-on-off--1290yz1
+7.4.13. PassengerSpawnMethod <string>	=>	passengerspawnmethod-string--sodg2y
 
-7.4.14. PassengerRollingRestarts <on|off>	=>	passengerrollingrestarts
+7.4.14. PassengerLoadShellEnvvars <on|off>	=>	passengerloadshellenvvars-on-off--1290yz1
 
-7.4.15. PassengerResistDeploymentErrors <on|off>	=>	passengerresistdeploymenterrors
+7.4.15. PassengerRollingRestarts <on|off>	=>	passengerrollingrestarts
+
+7.4.16. PassengerResistDeploymentErrors <on|off>	=>	passengerresistdeploymenterrors
 
 7.5. Security options	=>	security-options-1pb75ho
 
@@ -326,7 +328,7 @@
 
 10.2. Copy-on-write memory support (reducing memory consumption of Ruby applications)	=>	reducing-memory-consumption-of-ruby-on-rails-applications-by-33--1ubxnq0
 
-10.3. Capistrano recipe	=>	capistrano-recipe-syzgo7
+10.3. Tuning for Server Sent Events and WebSockets	=>	tuning-for-server-sent-events-and-websockets-1hy6qa9
 
 10.4. Bundler support	=>	bundler-support-cf72ih
 

data/doc/Users guide Apache.txt

@@ -583,6 +583,14 @@ include::users_guide_snippets/since_version.txt[]
 
 This option allows one to specify the Node.js command to use. See <<PassengerRuby,PassengerRuby>> for more information. The default value is 'node', meaning that the Node.js command will be looked up according to the `PATH` environment variable.
 
+==== PassengerMeteorAppSettings <filename>
+:version: 5.0.7
+include::users_guide_snippets/since_version.txt[]
+
+When using a Meteor application in non-bundled mode, use this option to specify a (JSON) file with settings for the application. Meteor will be started with the `--settings` parameter set to this option. 
+
+N.B. For bundled mode, Meteor requires you to put applications settings in the `METEOR_SETTINGS` environment variable.
+
 [[PassengerAppEnv]]
 ==== PassengerAppEnv <string> ====
 This option sets the value of the following environment variables:
@@ -648,7 +656,7 @@ Example:
 
 [[PassengerAppGroupName]]
 ==== PassengerAppGroupName <name>
-Sets the name of the application group that the current application should belong to. Its default value is the <<PassengerRoot,application root>>, plus (if it is set), the <<PassengerAppEnv,application environment name>>.
+Sets the name of the application group that the current application should belong to. Its default value is the <<application_root,application root>>, plus (if it is set), the <<PassengerAppEnv,application environment name>>.
 
 Phusion Passenger stores and caches most application spawning settings -- such as environment variables, process limits, etc -- on a per-app-group-name basis. This means that if you want to start two versions of your application, with each version having different environment variables, then you must assign them under different application group names.
 

data/doc/Users guide Nginx.html

@@ -1167,18 +1167,19 @@ using the command line.</p></div>
 <div class="foo toclevel4"><a href="#PassengerRuby">7.3.1. passenger_ruby &lt;filename&gt;</a></div>
 <div class="foo toclevel4"><a href="#_passenger_python_lt_filename_gt">7.3.2. passenger_python &lt;filename&gt;</a></div>
 <div class="foo toclevel4"><a href="#_passenger_nodejs_lt_filename_gt">7.3.3. passenger_nodejs &lt;filename&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerAppEnv">7.3.4. passenger_app_env &lt;string&gt;</a></div>
-<div class="foo toclevel4"><a href="#RailsEnv">7.3.5. rails_env &lt;string&gt;</a></div>
-<div class="foo toclevel4"><a href="#RackEnv">7.3.6. rack_env &lt;string&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerAppRoot">7.3.7. passenger_app_root &lt;path/to/root&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerAppGroupName">7.3.8. passenger_app_group_name &lt;name&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerAppType">7.3.9. passenger_app_type &lt;name&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerStartupFile">7.3.10. passenger_startup_file &lt;filename&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerSpawnMethod">7.3.11. passenger_spawn_method &lt;string&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerEnvVar">7.3.12. passenger_env_var &lt;name&gt; &lt;value&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerLoadShellEnvvars">7.3.13. passenger_load_shell_envvars &lt;on|off&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerRollingRestarts">7.3.14. passenger_rolling_restarts &lt;on|off&gt;</a></div>
-<div class="foo toclevel4"><a href="#PassengerResistDeploymentErrors">7.3.15. passenger_resist_deployment_errors &lt;on|off&gt;</a></div>
+<div class="foo toclevel4"><a href="#_passenger_meteor_app_settings_lt_filename_gt">7.3.4. passenger_meteor_app_settings &lt;filename&gt;</a></div>
+<div class="foo toclevel4"><a href="#PassengerAppEnv">7.3.5. passenger_app_env &lt;string&gt;</a></div>
+<div class="foo toclevel4"><a href="#RailsEnv">7.3.6. rails_env &lt;string&gt;</a></div>
+<div class="foo toclevel4"><a href="#RackEnv">7.3.7. rack_env &lt;string&gt;</a></div>
+<div class="foo toclevel4"><a href="#PassengerAppRoot">7.3.8. passenger_app_root &lt;path/to/root&gt;</a></div>
+<div class="foo toclevel4"><a href="#PassengerAppGroupName">7.3.9. passenger_app_group_name &lt;name&gt;</a></div>
+<div class="foo toclevel4"><a href="#PassengerAppType">7.3.10. passenger_app_type &lt;name&gt;</a></div>
+<div class="foo toclevel4"><a href="#PassengerStartupFile">7.3.11. passenger_startup_file &lt;filename&gt;</a></div>
+<div class="foo toclevel4"><a href="#PassengerSpawnMethod">7.3.12. passenger_spawn_method &lt;string&gt;</a></div>
+<div class="foo toclevel4"><a href="#PassengerEnvVar">7.3.13. passenger_env_var &lt;name&gt; &lt;value&gt;</a></div>
+<div class="foo toclevel4"><a href="#PassengerLoadShellEnvvars">7.3.14. passenger_load_shell_envvars &lt;on|off&gt;</a></div>
+<div class="foo toclevel4"><a href="#PassengerRollingRestarts">7.3.15. passenger_rolling_restarts &lt;on|off&gt;</a></div>
+<div class="foo toclevel4"><a href="#PassengerResistDeploymentErrors">7.3.16. passenger_resist_deployment_errors &lt;on|off&gt;</a></div>
 <div class="foo toclevel3"><a href="#_security_options">7.4. Security options</a></div>
 <div class="foo toclevel4"><a href="#PassengerUserSwitching">7.4.1. passenger_user_switching &lt;on|off&gt;</a></div>
 <div class="foo toclevel4"><a href="#PassengerUser">7.4.2. passenger_user &lt;username&gt;</a></div>
@@ -1254,7 +1255,7 @@ using the command line.</p></div>
 <div class="foo toclevel4"><a href="#_caveats_amp_troubleshooting">10.1.3. Caveats &amp; troubleshooting</a></div>
 <div class="foo toclevel4"><a href="#finding_out_app_user">10.1.4. Finding out what user an application is running as</a></div>
 <div class="foo toclevel3"><a href="#reducing_memory_usage">10.2. Copy-on-write memory support (reducing memory consumption of Ruby applications)</a></div>
-<div class="foo toclevel3"><a href="#capistrano">10.3. Capistrano recipe</a></div>
+<div class="foo toclevel3"><a href="#tuning_sse_websockets">10.3. Tuning for Server Sent Events and WebSockets</a></div>
 <div class="foo toclevel3"><a href="#bundler_support">10.4. Bundler support</a></div>
 <div class="foo toclevel4"><a href="#add_passenger_to_gemfile">10.4.1. Does Phusion Passenger itself need to be added to the Gemfile?</a></div>
 <div class="foo toclevel3"><a href="#_installing_multiple_ruby_on_rails_versions">10.5. Installing multiple Ruby on Rails versions</a></div>
@@ -1640,6 +1641,25 @@ sudo apt-get update</pre>
 </div>
 </div>
 </li>
+<li>
+<p>
+(Optional) If using <span class="monospaced">unattended-upgrades</span>, add our APT repository to the list of <span class="monospaced">Allowed-Origins</span> for upgrades, <span class="monospaced">/etc/apt/apt.conf.d/50unattended-upgrades</span>:
+</p>
+<div class="listingblock">
+<div class="content">
+<!-- Generator: GNU source-highlight 2.11.1
+by Lorenzo Bettini
+http://www.lorenzobettini.it
+http://www.gnu.org/software/src-highlite -->
+<pre><tt><span style="color: #990000">//</span> Automatically upgrade packages from these <span style="color: #990000">(</span>origin<span style="color: #990000">:</span>archive<span style="color: #990000">)</span> pairs
+Unattended-Upgrade<span style="color: #990000">::</span>Allowed-Origins {
+  <span style="color: #990000">//</span> To check <span style="color: #FF0000">"Origin:"</span> and <span style="color: #FF0000">"Suite:"</span><span style="color: #990000">,</span> you could use e<span style="color: #990000">.</span>g<span style="color: #990000">.:</span>
+  <span style="color: #990000">//</span> grep <span style="color: #FF0000">"Origin</span><span style="color: #CC33CC">\|</span><span style="color: #FF0000">Suite"</span> /var/lib/apt/lists/oss-binaries<span style="color: #990000">.</span>phusionpassenger<span style="color: #990000">.</span>com<span style="color: #990000">*</span>
+  <span style="color: #FF0000">"Phusion:stable"</span><span style="color: #990000">;</span>
+}<span style="color: #990000">;</span></tt></pre>
+</div>
+</div>
+</li>
 </ol></div>
 </div>
 <div class="sect3">
@@ -1735,10 +1755,11 @@ Restart Nginx:
 </ol></div>
 </dd>
 </dl></div>
+<div class="paragraph"><p>You can now proceed with a chapter for Deploying your (specific type of) application.</p></div>
 </div>
 <div class="sect3">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="inserting_passenger_root_for_apt"></span><h4 data-comment-topic="inserting-passenger-root-into-nginx-conf--1pmj19o" data-anchor="inserting_passenger_root_for_apt">2.3.3. Inserting <span class="monospaced">passenger_root</span> into nginx.conf</h4>
-<div class="paragraph"><p>During step 3 of the <em>Installing packages</em> subsection, you were instructed to uncomment the <a href="#PassengerRoot">passenger_root</a> directive in <span class="monospaced">/etc/nginx/nginx.conf</span>. If there is no commented version in there, then you need to insert it yourself.</p></div>
+<div class="paragraph"><p>If there is no <a href="#PassengerRoot">passenger_root</a> directive in <span class="monospaced">/etc/nginx/nginx.conf</span>, you can insert it yourself as follows:</p></div>
 <div class="paragraph"><p>First, run the following command and take note of its output:</p></div>
 <div class="listingblock">
 <div class="content monospaced">
@@ -1762,7 +1783,6 @@ http {
 }</pre>
 </div>
 </div>
-<div class="paragraph"><p>Once you’re done editing nginx.conf, continue with step 4.</p></div>
 </div>
 </div>
 <div class="sect2">
@@ -3489,7 +3509,13 @@ Do you want to know which command to use for a different Ruby interpreter? 'rvm
 <div class="paragraph"><p>This option allows one to specify the Node.js command to use. See <a href="#PassengerRuby">passenger_ruby</a> for more information. The default value is <em>node</em>, meaning that the Node.js command will be looked up according to the <span class="monospaced">PATH</span> environment variable.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerAppEnv"></span><h4 data-comment-topic="passenger-app-env-string--qjeimp" data-anchor="PassengerAppEnv">7.3.4. passenger_app_env &lt;string&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_passenger_meteor_app_settings_lt_filename_gt"></span><h4 data-comment-topic="passenger-meteor-app-settings-filename--1toqnaz" data-anchor="_passenger_meteor_app_settings_lt_filename_gt">7.3.4. passenger_meteor_app_settings &lt;filename&gt;</h4>
+<div class="paragraph"><p><strong>Introduced in version 5.0.7.</strong></p></div>
+<div class="paragraph"><p>When using a Meteor application in non-bundled mode, use this option to specify a (JSON) file with settings for the application. Meteor will be started with the <span class="monospaced">--settings</span> parameter set to this option.</p></div>
+<div class="paragraph"><p>N.B. For bundled mode, Meteor requires you to put applications settings in the <span class="monospaced">METEOR_SETTINGS</span> environment variable.</p></div>
+</div>
+<div class="sect3">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerAppEnv"></span><h4 data-comment-topic="passenger-app-env-string--qjeimp" data-anchor="PassengerAppEnv">7.3.5. passenger_app_env &lt;string&gt;</h4>
 <div class="paragraph"><p>This option sets the value of the following environment variables:</p></div>
 <div class="ulist"><ul>
 <li>
@@ -3548,15 +3574,15 @@ In an <em>if</em> configuration scope.
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>production</em>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="RailsEnv"></span><h4 data-comment-topic="rails-env-string--jlh7v9" data-anchor="RailsEnv">7.3.5. rails_env &lt;string&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="RailsEnv"></span><h4 data-comment-topic="rails-env-string--jlh7v9" data-anchor="RailsEnv">7.3.6. rails_env &lt;string&gt;</h4>
 <div class="paragraph"><p>An alias for <a href="#PassengerAppEnv">passenger_app_env</a>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="RackEnv"></span><h4 data-comment-topic="rack-env-string--tqmrt0" data-anchor="RackEnv">7.3.6. rack_env &lt;string&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="RackEnv"></span><h4 data-comment-topic="rack-env-string--tqmrt0" data-anchor="RackEnv">7.3.7. rack_env &lt;string&gt;</h4>
 <div class="paragraph"><p>An alias for <a href="#PassengerAppEnv">passenger_app_env</a>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerAppRoot"></span><h4 data-comment-topic="passenger-app-root-path-to-root--1dbudc6" data-anchor="PassengerAppRoot">7.3.7. passenger_app_root &lt;path/to/root&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerAppRoot"></span><h4 data-comment-topic="passenger-app-root-path-to-root--1dbudc6" data-anchor="PassengerAppRoot">7.3.8. passenger_app_root &lt;path/to/root&gt;</h4>
 <div class="paragraph"><p><strong>Introduced in version 4.0.0.</strong></p></div>
 <div class="paragraph"><p>By default, Phusion Passenger assumes that the application’s root directory
 is the parent directory of the <em>public</em> directory. This option allows one to
@@ -3601,7 +3627,7 @@ In an <em>if</em> configuration scope.
 </div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerAppGroupName"></span><h4 data-comment-topic="passenger-app-group-name-name--11jrx8u" data-anchor="PassengerAppGroupName">7.3.8. passenger_app_group_name &lt;name&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerAppGroupName"></span><h4 data-comment-topic="passenger-app-group-name-name--11jrx8u" data-anchor="PassengerAppGroupName">7.3.9. passenger_app_group_name &lt;name&gt;</h4>
 <div class="paragraph"><p>Sets the name of the application group that the current application should belong to. Its default value is the virtual host’s root directory, plus (if it is set), the <a href="#PassengerAppEnv">application environment name</a>.</p></div>
 <div class="paragraph"><p>Phusion Passenger stores and caches most application spawning settings — such as environment variables, process limits, etc — on a per-app-group-name basis. This means that if you want to start two versions of your application, with each version having different environment variables, then you must assign them under different application group names.</p></div>
 <div class="paragraph"><p>For example, consider a situation in which you are running multiple versions of the same app, with each version intended for a different customer. You use the <span class="monospaced">CUSTOMER_NAME</span> environment variable to tell the app which customer that version should serve.</p></div>
@@ -3698,7 +3724,7 @@ In an <em>if</em> configuration scope.
 <div class="paragraph"><p>In each place, it may be specified at most once.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerAppType"></span><h4 data-comment-topic="passenger-app-type-name--g9zccv" data-anchor="PassengerAppType">7.3.9. passenger_app_type &lt;name&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerAppType"></span><h4 data-comment-topic="passenger-app-type-name--g9zccv" data-anchor="PassengerAppType">7.3.10. passenger_app_type &lt;name&gt;</h4>
 <div class="paragraph"><p><strong>Introduced in version 4.0.25.</strong></p></div>
 <div class="paragraph"><p>By default, Phusion Passenger autodetects the type of the application, e.g. whether it’s a Ruby, Python, Node.js or Meteor app. If it’s unable to autodetect the type of the application (e.g. because you’ve specified a custom <a href="#PassengerStartupFile">passenger_startup_file</a>) then you can use this option to force Phusion Passenger to recognize the application as a specific type.</p></div>
 <div class="paragraph"><p>Allowed values are:</p></div>
@@ -3764,7 +3790,7 @@ In an <em>if</em> configuration scope.
 </div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerStartupFile"></span><h4 data-comment-topic="passenger-startup-file-filename--y4gy1m" data-anchor="PassengerStartupFile">7.3.10. passenger_startup_file &lt;filename&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerStartupFile"></span><h4 data-comment-topic="passenger-startup-file-filename--y4gy1m" data-anchor="PassengerStartupFile">7.3.11. passenger_startup_file &lt;filename&gt;</h4>
 <div class="paragraph"><p><strong>Introduced in version 4.0.25.</strong></p></div>
 <div class="paragraph"><p>This option specifies the startup file that Phusion Passenger should use when loading the application.</p></div>
 <div class="paragraph"><p>Every application has a <strong>startup file</strong> or <strong>entry point file</strong>: a file where the application begins execution. Some languages have widely accepted conventions about how such a file should be called (e.g. Ruby, with its <span class="monospaced">config.ru</span>). Other languages have somewhat-accepted conventions (e.g. Node.js, with its <span class="monospaced">app.js</span>). In these cases, Phusion Passenger reuses these conventions, and executes applications through those files.</p></div>
@@ -3854,7 +3880,7 @@ In an <em>if</em> configuration scope.
 </div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerSpawnMethod"></span><h4 data-comment-topic="passenger-spawn-method-string--1sc6njl" data-anchor="PassengerSpawnMethod">7.3.11. passenger_spawn_method &lt;string&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerSpawnMethod"></span><h4 data-comment-topic="passenger-spawn-method-string--1sc6njl" data-anchor="PassengerSpawnMethod">7.3.12. passenger_spawn_method &lt;string&gt;</h4>
 <div class="admonitionblock">
 <table><tr>
 <td class="icon">
@@ -3947,7 +3973,7 @@ In an <em>if</em> configuration scope.
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>smart</em>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerEnvVar"></span><h4 data-comment-topic="passenger-env-var-name-value--y8e7wh" data-anchor="PassengerEnvVar">7.3.12. passenger_env_var &lt;name&gt; &lt;value&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerEnvVar"></span><h4 data-comment-topic="passenger-env-var-name-value--y8e7wh" data-anchor="PassengerEnvVar">7.3.13. passenger_env_var &lt;name&gt; &lt;value&gt;</h4>
 <div class="paragraph"><p><strong>Introduced in version 5.0.0.</strong></p></div>
 <div class="paragraph"><p>Sets environment variables to pass to the application. Environment variables are only set during application loading.</p></div>
 <div class="paragraph"><p>Example:</p></div>
@@ -3989,7 +4015,7 @@ In an <em>if</em> configuration scope.
 <div class="paragraph"><p>In each place, it may be specified multiple times.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerLoadShellEnvvars"></span><h4 data-comment-topic="passenger-load-shell-envvars-on-off--fw5u4l" data-anchor="PassengerLoadShellEnvvars">7.3.13. passenger_load_shell_envvars &lt;on|off&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerLoadShellEnvvars"></span><h4 data-comment-topic="passenger-load-shell-envvars-on-off--fw5u4l" data-anchor="PassengerLoadShellEnvvars">7.3.14. passenger_load_shell_envvars &lt;on|off&gt;</h4>
 <div class="paragraph"><p><strong>Introduced in version 4.0.20.</strong></p></div>
 <div class="paragraph"><p>Enables or disables the loading of shell environment variables before spawning the application.</p></div>
 <div class="paragraph"><p>If this option is turned on, and the user’s shell is <span class="monospaced">bash</span>, then applications are loaded by running them with <span class="monospaced">bash -l -c</span>. Otherwise, they are loaded by running them directly from the <span class="monospaced">PassengerHelperAgent</span> process.</p></div>
@@ -4019,7 +4045,7 @@ In an <em>if</em> configuration scope.
 <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">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerRollingRestarts"></span><h4 data-comment-topic="passenger-rolling-restarts" data-anchor="PassengerRollingRestarts">7.3.14. passenger_rolling_restarts &lt;on|off&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerRollingRestarts"></span><h4 data-comment-topic="passenger-rolling-restarts" data-anchor="PassengerRollingRestarts">7.3.15. passenger_rolling_restarts &lt;on|off&gt;</h4>
 <div class="paragraph"><p><strong>This feature is only available in <a href="https://www.phusionpassenger.com/enterprise">Phusion Passenger Enterprise</a>. It was introduced in version 3.0.0. <a href="https://www.phusionpassenger.com/download">Buy Phusion Passenger Enterprise here.</a></strong></p></div>
 <div class="paragraph"><p>Enables or disables support for rolling restarts through restart.txt. Normally when you
 restart an application by touching restart.txt, Phusion Passenger would
@@ -4106,7 +4132,7 @@ In an <em>if</em> configuration scope.
 <div class="paragraph"><p>In each place, it may be specified at most once. The default value is <em>off</em>.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerResistDeploymentErrors"></span><h4 data-comment-topic="passenger-resist-deployment-errors-on-off--k9yf1" data-anchor="PassengerResistDeploymentErrors">7.3.15. passenger_resist_deployment_errors &lt;on|off&gt;</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="PassengerResistDeploymentErrors"></span><h4 data-comment-topic="passenger-resist-deployment-errors-on-off--k9yf1" data-anchor="PassengerResistDeploymentErrors">7.3.16. passenger_resist_deployment_errors &lt;on|off&gt;</h4>
 <div class="paragraph"><p><strong>This feature is only available in <a href="https://www.phusionpassenger.com/enterprise">Phusion Passenger Enterprise</a>. It was introduced in version 3.0.0. <a href="https://www.phusionpassenger.com/download">Buy Phusion Passenger Enterprise here.</a></strong></p></div>
 <div class="paragraph"><p>Enables or disables resistance against deployment errors.</p></div>
 <div class="paragraph"><p>Suppose you’ve upgraded your application and you’ve issued a command to restart it (e.g. by touching restart.txt), but the application code contains an error that prevents Phusion Passenger from successfully spawning a process (e.g. a syntax error). Phusion Passenger would normally display an error message in response to this.</p></div>
@@ -6534,39 +6560,29 @@ MRI Ruby &gt;= 2.0. Versions prior to 2.0 did not have a copy-on-write friendly
 </ul></div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="capistrano"></span><h3 data-comment-topic="capistrano-recipe-pfn4qu" data-anchor="capistrano">10.3. Capistrano recipe</h3>
-<div class="paragraph"><p>Phusion Passenger can be combined with <a href="http://capify.org/">Capistrano</a>.
-The following Capistrano recipe demonstrates Phusion Passenger support.
-It assumes that you’re using Git as version control system.</p></div>
-<div class="listingblock">
-<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
-set :deploy_to,   "/path-to-your-web-app-directory/#{application}"
-set :scm,         "git"
-
-role :app, domain
-role :web, domain
-role :db,  domain, :primary =&gt; true
-
-namespace :deploy do
-  task :start, :roles =&gt; :app do
-    run "touch #{current_release}/tmp/restart.txt"
-  end
-
-  task :stop, :roles =&gt; :app do
-    # Do nothing.
-  end
-
-  desc "Restart Application"
-  task :restart, :roles =&gt; :app do
-    run "touch #{current_release}/tmp/restart.txt"
-  end
-end</pre>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="tuning_sse_websockets"></span><h3 data-comment-topic="tuning-for-server-sent-events-and-websockets-8ec9td" data-anchor="tuning_sse_websockets">10.3. Tuning for Server Sent Events and WebSockets</h3>
+<div class="paragraph"><p>Phusion Passenger supports Server Sent Events (SSE) and WebSockets out of the box with no configuration, but there are some things you need to know.</p></div>
+<div class="paragraph"><p>First, WebSockets are <a href="https://github.com/phusion/passenger/issues/1202">not yet supported when using the Apache integration mode</a>.</p></div>
+<div class="paragraph"><p>Second, for Ruby apps only, you need to insert a configuration snippet inside your <span class="monospaced">config.ru</span>:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre><strong>if</strong> defined?(PhusionPassenger)
+  PhusionPassenger.advertised_concurrency_level = 0
+<strong>end</strong></pre>
 </div>
 </div>
+<div class="admonitionblock">
+<table><tr>
+<td class="icon">
+<img src="./images/icons/note.png" alt="Note">
+</td>
+<td class="content">
+<div class="paragraph"><p>This snippet tells Passenger that your Ruby app will handle SSE and WebSockets. In response, Passenger will adjust the connection concurrency settings for your app. Without this configuration snippet, SSE and WebSockets still work, but with degraded performance.</p></div>
+<div class="paragraph"><p>This configuration snippet is currently necessary because of the way Passenger is implemented. We are <a href="https://github.com/phusion/passenger/issues/1195">working on improving this mechanism</a>. One day, the above configuration snippet will no longer be necessary. For now, you should include the above configuration snippet for optimal SSE and WebSocket performance.</p></div>
+</td>
+</tr></table>
+</div>
+<div class="paragraph"><p>Finally, you can find Passenger SSE and WebSocket demo apps on <a href="https://www.phusionpassenger.com/documentation_and_support">the Passenger documentation overview page</a>, under section "Demos".</p></div>
 </div>
 <div class="sect2">
 <a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="bundler_support"></span><h3 data-comment-topic="bundler-support-19v1h43" data-anchor="bundler_support">10.4. Bundler support</h3>
@@ -7415,25 +7431,13 @@ Phusion Passenger’s installer, build system and administration tools are writt
 <p>
 Certain internally used tools, such as the crash handler (which generates a backtrace in case Phusion Passenger crash) and the prespawn script (used to implement
 <a href="#PassengerPreStart">passenger_pre_start</a>)
-are written in Ruby as well.
-</p>
-</li>
-<li>
-<p>
-Ruby web application support is implemented in Ruby.
-</p>
-</li>
-<li>
-<p>
-If you use <a href="#flying_passenger">Flying Passenger</a>, then the Flying Passenger daemon is written in Ruby. The daemon is a small (less than 500 lines of code) and offloads most tasks to the C++ core.
-</p>
-</li>
-<li>
-<p>
-If you use <a href="Users%20guide%20Standalone.html">Phusion Passenger Standalone</a>, then the frontend (the <span class="monospaced">passenger</span> command) is written in Ruby. The frontend is small (less than 1500 lines of code) and offloads most tasks to the C++ core.
 </p>
 </li>
 </ul></div>
+<div class="paragraph"><p>are written in Ruby as well.
+ * Ruby web application support is implemented in Ruby.
+ * If you use <a href="#flying_passenger">Flying Passenger</a>, then the Flying Passenger daemon is written in Ruby. The daemon is a small (less than 500 lines of code) and offloads most tasks to the C<span class="monospaced"> core.
+ * If you use <a href="Users%20guide%20Standalone.html">Phusion Passenger Standalone</a>, then the frontend (the <span class="monospaced">passenger</span> command) is written in Ruby. The frontend is small (less than 1500 lines of code) and offloads most tasks to the C</span> core.</p></div>
 <div class="paragraph"><p>Other than the aforementioned aspects, Phusion Passenger does not use Ruby during normal operation. For example, if you run Python WSGI web applications on Phusion Passenger, then there will be (almost) no Ruby code running on the system.</p></div>
 </div>
 <div class="sect3">
@@ -8184,7 +8188,8 @@ echo <span style="color: #FF0000">'export PATH=/usr/local/bin:$PATH'</span> <spa
 <td class="icon">
 <img src="./images/icons/note.png" alt="Note">
 </td>
-<td class="content">Depending on the system, the bashrc file may have a different filename. On Debian and Ubuntu, it’s <span class="monospaced">/etc/bash.bashrc</span>.</td>
+<td class="content">Depending on the system, the bashrc file may have a different filename. On Debian and Ubuntu, it’s <span class="monospaced">/etc/bash.bashrc</span>.
+NOTE: Make sure your <span class="monospaced">~/.bashrc</span> is actually included by your <span class="monospaced">~/.profile</span>, which might not be the case if you created the user with <span class="monospaced">useradd</span> instead of <span class="monospaced">adduser</span> for example</td>
 </tr></table>
 </div>
 </div>
@@ -8260,7 +8265,7 @@ When running Apache, use the <span class="monospaced">PassEnv</span> and <span c
 </li>
 <li>
 <p>
-When running Nginx, use the <a href="#passenger_env_var">passenger_env_var</a> directive.
+When running Nginx, use the <a href="#PassengerEnvVar">passenger_env_var</a> directive.
 </p>
 </li>
 <li>