passenger 5.0.6 → 5.0.7

data/doc/Users guide Nginx.idmap.txt

@@ -138,29 +138,31 @@
 
 7.3.3. passenger_nodejs <filename>	=>	passenger-nodejs-filename--16hzjsv
 
-7.3.4. passenger_app_env <string>	=>	passenger-app-env-string--qjeimp
+7.3.4. passenger_meteor_app_settings <filename>	=>	passenger-meteor-app-settings-filename--1toqnaz
 
-7.3.5. rails_env <string>	=>	rails-env-string--jlh7v9
+7.3.5. passenger_app_env <string>	=>	passenger-app-env-string--qjeimp
 
-7.3.6. rack_env <string>	=>	rack-env-string--tqmrt0
+7.3.6. rails_env <string>	=>	rails-env-string--jlh7v9
 
-7.3.7. passenger_app_root <path/to/root>	=>	passenger-app-root-path-to-root--1dbudc6
+7.3.7. rack_env <string>	=>	rack-env-string--tqmrt0
 
-7.3.8. passenger_app_group_name <name>	=>	passenger-app-group-name-name--11jrx8u
+7.3.8. passenger_app_root <path/to/root>	=>	passenger-app-root-path-to-root--1dbudc6
 
-7.3.9. passenger_app_type <name>	=>	passenger-app-type-name--g9zccv
+7.3.9. passenger_app_group_name <name>	=>	passenger-app-group-name-name--11jrx8u
 
-7.3.10. passenger_startup_file <filename>	=>	passenger-startup-file-filename--y4gy1m
+7.3.10. passenger_app_type <name>	=>	passenger-app-type-name--g9zccv
 
-7.3.11. passenger_spawn_method <string>	=>	passenger-spawn-method-string--1sc6njl
+7.3.11. passenger_startup_file <filename>	=>	passenger-startup-file-filename--y4gy1m
 
-7.3.12. passenger_env_var <name> <value>	=>	passenger-env-var-name-value--y8e7wh
+7.3.12. passenger_spawn_method <string>	=>	passenger-spawn-method-string--1sc6njl
 
-7.3.13. passenger_load_shell_envvars <on|off>	=>	passenger-load-shell-envvars-on-off--fw5u4l
+7.3.13. passenger_env_var <name> <value>	=>	passenger-env-var-name-value--y8e7wh
 
-7.3.14. passenger_rolling_restarts <on|off>	=>	passenger-rolling-restarts
+7.3.14. passenger_load_shell_envvars <on|off>	=>	passenger-load-shell-envvars-on-off--fw5u4l
 
-7.3.15. passenger_resist_deployment_errors <on|off>	=>	passenger-resist-deployment-errors-on-off--k9yf1
+7.3.15. passenger_rolling_restarts <on|off>	=>	passenger-rolling-restarts
+
+7.3.16. passenger_resist_deployment_errors <on|off>	=>	passenger-resist-deployment-errors-on-off--k9yf1
 
 7.4. Security options	=>	security-options-1bv93g4
 
@@ -312,7 +314,7 @@
 
 10.2. Copy-on-write memory support (reducing memory consumption of Ruby applications)	=>	reducing-memory-consumption-of-ruby-on-rails-applications-by-33--1o3z66q
 
-10.3. Capistrano recipe	=>	capistrano-recipe-pfn4qu
+10.3. Tuning for Server Sent Events and WebSockets	=>	tuning-for-server-sent-events-and-websockets-8ec9td
 
 10.4. Bundler support	=>	bundler-support-19v1h43
 

data/doc/Users guide Nginx.txt

@@ -568,6 +568,14 @@ include::users_guide_snippets/since_version.txt[]
 
 This option allows one to specify the Node.js command to use. See <<PassengerRuby,passenger_ruby>> for more information. The default value is 'node', meaning that the Node.js command will be looked up according to the `PATH` environment variable.
 
+==== passenger_meteor_app_settings <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]]
 ==== passenger_app_env <string>
 This option sets the value of the following environment variables:

data/doc/Users guide Standalone.html

@@ -1138,17 +1138,21 @@ pre {
 <div class="foo toclevel3"><a href="#_generic_troubleshooting_tips">7.1. Generic troubleshooting tips</a></div>
 <div class="foo toclevel3"><a href="#_upon_uploading_a_file_phusion_passenger_reports_client_body_temp_00000000xx_failed_2_no_such_file_or_directory">7.2. Upon uploading a file, Phusion Passenger reports "client_body_temp/00000000xx failed (2: No such file or directory)"</a></div>
 <div class="foo toclevel3"><a href="#_i_get_command_not_found_when_running_a_phusion_passenger_command_through_sudo">7.3. I get "command not found" when running a Phusion Passenger command through sudo</a></div>
-<div class="foo toclevel2"><a href="#about_environment_variables">8. Appendix: About environment variables</a></div>
-<div class="foo toclevel3"><a href="#_working_with_environment_variables">8.1. Working with environment variables</a></div>
-<div class="foo toclevel3"><a href="#the_path_env_var">8.2. The PATH environment variable</a></div>
-<div class="foo toclevel4"><a href="#_adding_phusion_passenger_8217_s_administration_tools_to_path">8.2.1. Adding Phusion Passenger’s administration tools to PATH</a></div>
-<div class="foo toclevel3"><a href="#_making_environment_variables_permanent">8.3. Making environment variables permanent</a></div>
-<div class="foo toclevel4"><a href="#_bash">8.3.1. bash</a></div>
-<div class="foo toclevel4"><a href="#_apache">8.3.2. Apache</a></div>
-<div class="foo toclevel4"><a href="#_nginx">8.3.3. Nginx</a></div>
-<div class="foo toclevel4"><a href="#_cron">8.3.4. cron</a></div>
-<div class="foo toclevel4"><a href="#env_vars_passenger_apps">8.3.5. Phusion Passenger-served apps</a></div>
-<div class="foo toclevel3"><a href="#env_vars_and_sudo">8.4. Environment variables and sudo</a></div>
+<div class="foo toclevel2"><a href="#_under_the_hood">8. Under the hood</a></div>
+<div class="foo toclevel3"><a href="#relationship_with_ruby">8.1. Phusion Passenger and its relationship with Ruby</a></div>
+<div class="foo toclevel4"><a href="#_how_ruby_is_used">8.1.1. How Ruby is used</a></div>
+<div class="foo toclevel4"><a href="#_when_the_system_has_multiple_ruby_interpreters">8.1.2. When the system has multiple Ruby interpreters</a></div>
+<div class="foo toclevel2"><a href="#about_environment_variables">9. Appendix: About environment variables</a></div>
+<div class="foo toclevel3"><a href="#_working_with_environment_variables">9.1. Working with environment variables</a></div>
+<div class="foo toclevel3"><a href="#the_path_env_var">9.2. The PATH environment variable</a></div>
+<div class="foo toclevel4"><a href="#_adding_phusion_passenger_8217_s_administration_tools_to_path">9.2.1. Adding Phusion Passenger’s administration tools to PATH</a></div>
+<div class="foo toclevel3"><a href="#_making_environment_variables_permanent">9.3. Making environment variables permanent</a></div>
+<div class="foo toclevel4"><a href="#_bash">9.3.1. bash</a></div>
+<div class="foo toclevel4"><a href="#_apache">9.3.2. Apache</a></div>
+<div class="foo toclevel4"><a href="#_nginx">9.3.3. Nginx</a></div>
+<div class="foo toclevel4"><a href="#_cron">9.3.4. cron</a></div>
+<div class="foo toclevel4"><a href="#env_vars_passenger_apps">9.3.5. Phusion Passenger-served apps</a></div>
+<div class="foo toclevel3"><a href="#env_vars_and_sudo">9.4. Environment variables and sudo</a></div>
 </div>
 </div>
 <div id="content">
@@ -1467,6 +1471,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">
@@ -1522,6 +1545,7 @@ Install the packages:
 </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">
@@ -2892,7 +2916,141 @@ $ rvmsudo /somewhere/bin/passenger-status</pre>
 </div>
 </div>
 <div class="sect1">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="about_environment_variables"></span><h2 data-comment-topic="appendix-about-environment-variables-1ct91x3" data-anchor="about_environment_variables">8. Appendix: About environment variables</h2>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_under_the_hood"></span><h2 data-comment-topic="under-the-hood-ub7j3q" data-anchor="_under_the_hood">8. Under the hood</h2>
+<div class="sectionbody">
+<div class="sect2">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="relationship_with_ruby"></span><h3 data-comment-topic="phusion-passenger-and-its-relationship-with-ruby-1usvd0o" data-anchor="relationship_with_ruby">8.1. Phusion Passenger and its relationship with Ruby</h3>
+<div class="sect3">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_how_ruby_is_used"></span><h4 data-comment-topic="how-ruby-is-used-1saha86" data-anchor="_how_ruby_is_used">8.1.1. How Ruby is used</h4>
+<div class="paragraph"><p>Phusion Passenger’s core is written in C++ for performance and memory efficiency. It supports web applications written in any language. Phusion Passenger requires Ruby, its usage of Ruby is minimal in order to maximize performance and to minimize memory usage.</p></div>
+<div class="ulist"><ul>
+<li>
+<p>
+Phusion Passenger’s installer, build system and administration tools are written in Ruby.
+</p>
+</li>
+<li>
+<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>)
+</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">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_when_the_system_has_multiple_ruby_interpreters"></span><h4 data-comment-topic="when-the-system-has-multiple-ruby-interpreters-acf6d" data-anchor="_when_the_system_has_multiple_ruby_interpreters">8.1.2. When the system has multiple Ruby interpreters</h4>
+<div class="paragraph"><p>Phusion Passenger may be installed with any Ruby interpreter. Once installed, you can run Phusion Passenger’s Ruby parts under any Ruby interpreter you want, even if that Ruby interpreter was not the one you originally installed Phusion Passenger with.</p></div>
+<div class="paragraph"><p>The reason for this is that Phusion Passenger does not dynamically link to Ruby: Phusion Passenger uses Ruby entirely out-of-process. Thus you can switch to any Ruby interpreter you want during runtime, without recompiling Phusion Passenger, and without worrying about what Ruby you used to install Phusion Passenger.</p></div>
+<div class="paragraph"><p>Phusion Passenger is also capable of running Ruby web applications under any Ruby interpreter you want. So it is not important which Ruby you use to install Phusion Passenger: it will work regardless. Please refer to the documentation for the
+<a href="#PassengerRuby">passenger_ruby</a>
+directive to learn how run different web applications under different Ruby interpreters.</p></div>
+<div class="paragraph">
+<div class="title">Caveat: RVM and RVM gemsets</div>
+<p>There is however one caveat if you happen to be using RVM or RVM gemsets. When you <span class="monospaced">gem install</span> Phusion Passenger using RVM, then RVM will install Phusion Passenger into the <strong>currently active RVM Ruby and gemset</strong>. This means that Phusion Passenger commands - such as <span class="monospaced">passenger</span>, <span class="monospaced">passenger-install-xxx-module</span> and <span class="monospaced">passenger-status</span> - are available in that same RVM Ruby and gemset only. When you switch Ruby interpreter, or when you switch gemset, the Phusion Passenger commands will no longer be available, and you will get a <span class="monospaced">command not found</span> error. Here’s an example which demonstrates the problem.</p>
+</div>
+<div class="listingblock">
+<div class="title">"Command not found" problem demonstration</div>
+<div class="content">
+<!-- Generator: GNU source-highlight 2.11.1
+by Lorenzo Bettini
+http://www.lorenzobettini.it
+http://www.gnu.org/software/src-highlite -->
+<pre><tt><span style="font-style: italic"><span style="color: #9A1900">## Install Phusion Passenger (open source edition) using Ruby 1.9.3</span></span>
+<span style="font-style: italic"><span style="color: #9A1900">## and the 'business' gemset</span></span>
+$ rvm use <span style="color: #993399">1.9</span><span style="color: #990000">.</span><span style="color: #993399">3</span>
+Using /home/phusion<span style="color: #990000">/.</span>rvm/gems/ruby-<span style="color: #993399">1.9</span><span style="color: #990000">.</span><span style="color: #993399">3</span>-p<span style="color: #993399">429</span>
+$ rvm gemset create business
+$ rvm gemset use business
+Using ruby-<span style="color: #993399">1.9</span><span style="color: #990000">.</span><span style="color: #993399">3</span>-p<span style="color: #993399">429</span> with gemset business
+$ curl -O https<span style="color: #990000">:</span>//s<span style="color: #993399">3</span><span style="color: #990000">.</span>amazonaws<span style="color: #990000">.</span>com/phusion-passenger/releases/gem_bootstrap<span style="color: #990000">.</span>sh
+$ <span style="font-weight: bold"><span style="color: #0000FF">eval</span></span> <span style="color: #FF0000">"`sh gem_bootstrap.sh`"</span>
+$ gem install passenger
+
+<span style="font-style: italic"><span style="color: #9A1900">## Verify that passenger works</span></span>
+$ passenger --version
+Phusion Passenger version <span style="color: #993399">4.0</span><span style="color: #990000">.</span><span style="color: #993399">14</span>
+
+<span style="font-style: italic"><span style="color: #9A1900">## Switch to a different RVM gemset. You will get a `command not found`</span></span>
+$ rvm gemset use default
+Using ruby-<span style="color: #993399">1.9</span><span style="color: #990000">.</span><span style="color: #993399">3</span>-p<span style="color: #993399">429</span> with gemset default
+$ passenger --version
+bash<span style="color: #990000">:</span> passenger<span style="color: #990000">:</span> <span style="font-weight: bold"><span style="color: #0000FF">command</span></span> not found
+
+<span style="font-style: italic"><span style="color: #9A1900">## Switch to a different Ruby interpreter. You will also get</span></span>
+<span style="font-style: italic"><span style="color: #9A1900">## a `command not found`</span></span>
+$ rvm use <span style="color: #993399">2.0</span><span style="color: #990000">.</span><span style="color: #993399">0</span>
+Using /home/phusion<span style="color: #990000">/.</span>rvm/gems/ruby-<span style="color: #993399">2.0</span><span style="color: #990000">.</span><span style="color: #993399">0</span>-p<span style="color: #993399">195</span>
+$ passenger --version
+bash<span style="color: #990000">:</span> passenger<span style="color: #990000">:</span> <span style="font-weight: bold"><span style="color: #0000FF">command</span></span> not found
+
+<span style="font-style: italic"><span style="color: #9A1900">## Switch back to the Ruby and gemset that you installed Phusion</span></span>
+<span style="font-style: italic"><span style="color: #9A1900">## Passenger with, and verify that it works again</span></span>
+$ rvm use <span style="color: #993399">1.9</span><span style="color: #990000">.</span><span style="color: #993399">3</span>
+Using /home/phusion<span style="color: #990000">/.</span>rvm/gems/ruby-<span style="color: #993399">2.0</span><span style="color: #990000">.</span><span style="color: #993399">0</span>-p<span style="color: #993399">195</span>
+$ rvm gemset use business
+Using ruby-<span style="color: #993399">1.9</span><span style="color: #990000">.</span><span style="color: #993399">3</span>-p<span style="color: #993399">429</span> with gemset business
+$ passenger --version
+Phusion Passenger version <span style="color: #993399">4.0</span><span style="color: #990000">.</span><span style="color: #993399">14</span></tt></pre>
+</div>
+</div>
+<div class="paragraph">
+<div class="title">Solutions</div>
+<p>There are several ways to solve this problem:</p>
+</div>
+<div class="olist arabic"><ol class="arabic">
+<li>
+<p>
+Permanently add Phusion Passenger’s command directory to your PATH, so that your shell can always find them even when you switch RVM Ruby or gemset. If you don’t know what PATH means, please read <a href="#about_environment_variable">About environment variables</a> first.
+</p>
+<div class="paragraph"><p>The drawback is that you have to redo this every time you upgrade Phusion Passenger, because the Phusion Passenger directory filename is dependent on the version number.</p></div>
+<div class="paragraph"><p>First, identify the location of the Phusion Passenger command directory, like this:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>$ echo `passenger-config --root`/bin
+/home/phusion/.rvm/gems/ruby-1.9.3-p429/gems/passenger-4.0.15/bin</pre>
+</div>
+</div>
+<div class="paragraph"><p>Next, add the directory that you’ve found to your current shell’s PATH:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>$ export PATH=/home/phusion/.rvm/gems/ruby-1.9.3-p429/gems/passenger-4.0.15/bin:$PATH</pre>
+</div>
+</div>
+<div class="paragraph"><p>Finally, make the change permanent by appending the above command to your bash startup file:</p></div>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>$ echo 'export PATH=/home/phusion/.rvm/gems/ruby-1.9.3-p429/gems/passenger-4.0.15/bin:$PATH' &gt;&gt; ~/.bashrc</pre>
+</div>
+</div>
+</li>
+<li>
+<p>
+Switch back to the RVM Ruby and gemset that you installed Phusion Passenger with, before running any Phusion Passenger command.
+</p>
+</li>
+<li>
+<p>
+Prepend any Phusion Passenger command with <span class="monospaced">rvm-exec RUBY_NAME@GEMSET_NAME ruby -S</span>. If the relevant Phusion Passenger command also needs root privileges, then prepend <span class="monospaced">rvmsudo</span> before that. For example:
+</p>
+<div class="listingblock">
+<div class="content monospaced">
+<pre>rvm-exec 1.9.3@business ruby -S passenger --version
+rvmsudo rvm-exec 1.9.3@business ruby -S passenger-install-apache2-module</pre>
+</div>
+</div>
+</li>
+</ol></div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="about_environment_variables"></span><h2 data-comment-topic="appendix-about-environment-variables-1ct91x3" data-anchor="about_environment_variables">9. Appendix: About environment variables</h2>
 <div class="sectionbody">
 <div class="paragraph"><p>Environment variables are named values that affect how the system works. For example they tell the system where to look for commands (the <span class="monospaced">PATH</span> variable) or where to look for libraries (<span class="monospaced">LD_LIBRARY_PATH</span>). Their names are often in all-uppercase. Sometimes people refer to an environment variable with a dollar sign <span class="monospaced">$</span> in front, but that’s the same thing: when people say "the $PATH environment variable" they mean "the PATH environment variable". This is because the dollar sign <span class="monospaced">$</span> is a shell syntax for refering to an environment variable, as you will learn later.</p></div>
 <div class="paragraph"><p>Environment variables are set on a <strong>per-process</strong> basis, but they are <strong>inherited</strong> by child processes. This means that if you set environment variables in process A, another already running process B will not see these new environment variables. But if A spawns a child process C, then C will have all environment variables that A had. If you once again change the environment variables in A, then C will not see the changes.</p></div>
@@ -2923,7 +3081,7 @@ $ rvmsudo /somewhere/bin/passenger-status</pre>
 </tr></table>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_working_with_environment_variables"></span><h3 data-comment-topic="working-with-environment-variables-11cmwlv" data-anchor="_working_with_environment_variables">8.1. Working with environment variables</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_working_with_environment_variables"></span><h3 data-comment-topic="working-with-environment-variables-11cmwlv" data-anchor="_working_with_environment_variables">9.1. Working with environment variables</h3>
 <div class="paragraph"><p>You can see all environment variables in your shell by running the following command:</p></div>
 <div class="listingblock">
 <div class="content">
@@ -3005,7 +3163,7 @@ http://www.gnu.org/software/src-highlite -->
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="the_path_env_var"></span><h3 data-comment-topic="the-path-environment-variable-yzfn3k" data-anchor="the_path_env_var">8.2. The PATH environment variable</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="the_path_env_var"></span><h3 data-comment-topic="the-path-environment-variable-yzfn3k" data-anchor="the_path_env_var">9.2. The PATH environment variable</h3>
 <div class="paragraph"><p>The <span class="monospaced">PATH</span> environment variable dictates where the system looks for command. It is a colon-separated list of directories. If you get a "command not found" error while you know that the command is installed, then setting <span class="monospaced">PATH</span> will help. For example suppose that the command <span class="monospaced">frobnicator</span> is in <span class="monospaced">/opt/local/bin</span>:</p></div>
 <div class="listingblock">
 <div class="content">
@@ -3052,7 +3210,7 @@ user@localhost bash$ frobnicator
 </div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_adding_phusion_passenger_8217_s_administration_tools_to_path"></span><h4 data-comment-topic="adding-phusion-passenger-s-administration-tools-to-path-d7k5mh" data-anchor="_adding_phusion_passenger_8217_s_administration_tools_to_path">8.2.1. Adding Phusion Passenger’s administration tools to PATH</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_adding_phusion_passenger_8217_s_administration_tools_to_path"></span><h4 data-comment-topic="adding-phusion-passenger-s-administration-tools-to-path-d7k5mh" data-anchor="_adding_phusion_passenger_8217_s_administration_tools_to_path">9.2.1. Adding Phusion Passenger’s administration tools to PATH</h4>
 <div class="paragraph"><p>If you get a "command not found" error when invoking one of the Phusion Passenger administration tools (e.g. <span class="monospaced">passenger-status</span> or <span class="monospaced">passenger-memory-stats</span> then that means the tools are not in <span class="monospaced">PATH</span>, so you need to add them.</p></div>
 <div class="ulist"><ul>
 <li>
@@ -3122,10 +3280,10 @@ $ sudo find . -name passenger-status
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_making_environment_variables_permanent"></span><h3 data-comment-topic="making-environment-variables-permanent-mkq46d" data-anchor="_making_environment_variables_permanent">8.3. Making environment variables permanent</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_making_environment_variables_permanent"></span><h3 data-comment-topic="making-environment-variables-permanent-mkq46d" data-anchor="_making_environment_variables_permanent">9.3. Making environment variables permanent</h3>
 <div class="paragraph"><p>When you exit your shell, the evironment variable changes are lost. There is no standard method to set environment variables system-wide, so you have to set them in different configuration files for different services.</p></div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_bash"></span><h4 data-comment-topic="bash-hmcscc" data-anchor="_bash">8.3.1. bash</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_bash"></span><h4 data-comment-topic="bash-hmcscc" data-anchor="_bash">9.3.1. bash</h4>
 <div class="paragraph"><p>To make environment variables permanent for future bash sessions <strong>for the current user</strong>, add them to your <span class="monospaced">~/.bashrc</span>:</p></div>
 <div class="listingblock">
 <div class="content">
@@ -3143,12 +3301,13 @@ 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>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_apache"></span><h4 data-comment-topic="apache-15y3bm0" data-anchor="_apache">8.3.2. Apache</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_apache"></span><h4 data-comment-topic="apache-15y3bm0" data-anchor="_apache">9.3.2. Apache</h4>
 <div class="admonitionblock">
 <table><tr>
 <td class="icon">
@@ -3163,7 +3322,7 @@ echo <span style="color: #FF0000">'export PATH=/usr/local/bin:$PATH'</span> <spa
 <div class="paragraph"><p>On other systems, or if you did not install Apache through the system’s package manager, the configuration file for environment variables is specific to the vendor that supplied Apache. There may not even be such a configuration file. You should contact the vendor for support.</p></div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_nginx"></span><h4 data-comment-topic="nginx-uarf27" data-anchor="_nginx">8.3.3. Nginx</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_nginx"></span><h4 data-comment-topic="nginx-uarf27" data-anchor="_nginx">9.3.3. Nginx</h4>
 <div class="admonitionblock">
 <table><tr>
 <td class="icon">
@@ -3185,7 +3344,7 @@ then you should edit that script to define the environment variables. Those init
 </div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_cron"></span><h4 data-comment-topic="cron-6272ar" data-anchor="_cron">8.3.4. cron</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="_cron"></span><h4 data-comment-topic="cron-6272ar" data-anchor="_cron">9.3.4. cron</h4>
 <div class="paragraph"><p>To make environment variables permanent for cron jobs, add those variables to the relevant crontab. But note that inside crontabs you cannot refer to existing environment variables with the <span class="monospaced">$</span> syntax because crontabs are not shell scripts. You have to specify the entire value.</p></div>
 <div class="listingblock">
 <div class="title">What to put in "crontab -e"</div>
@@ -3208,7 +3367,7 @@ PATH=/usr/bin:/usr/local/bin
 </div>
 </div>
 <div class="sect3">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="env_vars_passenger_apps"></span><h4 data-comment-topic="phusion-passenger-served-apps-127wbl2" data-anchor="env_vars_passenger_apps">8.3.5. Phusion Passenger-served apps</h4>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="env_vars_passenger_apps"></span><h4 data-comment-topic="phusion-passenger-served-apps-127wbl2" data-anchor="env_vars_passenger_apps">9.3.5. Phusion Passenger-served apps</h4>
 <div class="paragraph"><p>You can pass environment variables to Phusion Passenger-served apps through various methods:</p></div>
 <div class="ulist"><ul>
 <li>
@@ -3218,7 +3377,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>
@@ -3260,7 +3419,7 @@ os<span style="color: #990000">.</span>environ<span style="color: #990000">[</sp
 </div>
 </div>
 <div class="sect2">
-<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="env_vars_and_sudo"></span><h3 data-comment-topic="environment-variables-and-sudo-znzmif" data-anchor="env_vars_and_sudo">8.4. Environment variables and sudo</h3>
+<a href="javascript:void(0)" class="comments empty" title="Add a comment"><span class="count"></span></a><span class="anchor_helper" id="env_vars_and_sudo"></span><h3 data-comment-topic="environment-variables-and-sudo-znzmif" data-anchor="env_vars_and_sudo">9.4. Environment variables and sudo</h3>
 <div class="admonitionblock">
 <table><tr>
 <td class="icon">

data/doc/Users guide Standalone.idmap.txt

@@ -96,25 +96,33 @@
 
 7.3. I get "command not found" when running a Phusion Passenger command through sudo	=>	i-get-command-not-found-when-running-a-phusion-passenger-command-through-sudo-14k8kde
 
-8. Appendix: About environment variables	=>	appendix-about-environment-variables-1ct91x3
+8. Under the hood	=>	under-the-hood-ub7j3q
 
-8.1. Working with environment variables	=>	working-with-environment-variables-11cmwlv
+8.1. Phusion Passenger and its relationship with Ruby	=>	phusion-passenger-and-its-relationship-with-ruby-1usvd0o
 
-8.2. The PATH environment variable	=>	the-path-environment-variable-yzfn3k
+8.1.1. How Ruby is used	=>	how-ruby-is-used-1saha86
 
-8.2.1. Adding Phusion Passenger’s administration tools to PATH	=>	adding-phusion-passenger-s-administration-tools-to-path-d7k5mh
+8.1.2. When the system has multiple Ruby interpreters	=>	when-the-system-has-multiple-ruby-interpreters-acf6d
 
-8.3. Making environment variables permanent	=>	making-environment-variables-permanent-mkq46d
+9. Appendix: About environment variables	=>	appendix-about-environment-variables-1ct91x3
 
-8.3.1. bash	=>	bash-hmcscc
+9.1. Working with environment variables	=>	working-with-environment-variables-11cmwlv
 
-8.3.2. Apache	=>	apache-15y3bm0
+9.2. The PATH environment variable	=>	the-path-environment-variable-yzfn3k
 
-8.3.3. Nginx	=>	nginx-uarf27
+9.2.1. Adding Phusion Passenger’s administration tools to PATH	=>	adding-phusion-passenger-s-administration-tools-to-path-d7k5mh
 
-8.3.4. cron	=>	cron-6272ar
+9.3. Making environment variables permanent	=>	making-environment-variables-permanent-mkq46d
 
-8.3.5. Phusion Passenger-served apps	=>	phusion-passenger-served-apps-127wbl2
+9.3.1. bash	=>	bash-hmcscc
 
-8.4. Environment variables and sudo	=>	environment-variables-and-sudo-znzmif
+9.3.2. Apache	=>	apache-15y3bm0
+
+9.3.3. Nginx	=>	nginx-uarf27
+
+9.3.4. cron	=>	cron-6272ar
+
+9.3.5. Phusion Passenger-served apps	=>	phusion-passenger-served-apps-127wbl2
+
+9.4. Environment variables and sudo	=>	environment-variables-and-sudo-znzmif
 

data/doc/Users guide Standalone.txt

@@ -415,6 +415,10 @@ Any options that you pass to the `passenger` command will affect all deployed we
 
 include::users_guide_snippets/troubleshooting/default.txt[]
 
+== Under the hood
+
+include::users_guide_snippets/under_the_hood/relationship_with_ruby.txt[]
+
 [[about_environment_variables]]
 == Appendix: About environment variables
 

data/doc/users_guide_snippets/environment_variables.txt

@@ -167,6 +167,7 @@ echo 'export PATH=/usr/local/bin:$PATH' >> ~/.bashrc
 To make them permanent for future bash sessions **for all users**, add them to `/etc/bashrc`.
 
 NOTE: Depending on the system, the bashrc file may have a different filename. On Debian and Ubuntu, it's `/etc/bash.bashrc`.
+NOTE: Make sure your `~/.bashrc` is actually included by your `~/.profile`, which might not be the case if you created the user with `useradd` instead of `adduser` for example
 
 ==== Apache
 
@@ -225,7 +226,7 @@ PATH=/usr/bin:/usr/local/bin
 You can pass environment variables to Phusion Passenger-served apps through various methods:
 
  * When running Apache, use the `PassEnv` and `SetEnv` directives of link:http://httpd.apache.org/docs/2.4/mod/mod_env.html[mod_env]. This is supported starting from Phusion Passenger 4.0.
- * When running Nginx, use the <<passenger_env_var,passenger_env_var>> directive.
+ * When running Nginx, use the <<PassengerEnvVar,passenger_env_var>> directive.
  * Through your `bashrc`. Starting from version 4.0, Phusion Passenger 4.0 spawns applications through bash and inherit all bash environment variables. Phusion Passenger Standalone tends to be started from the shell and thus inherits all environment variables set by the shell.
  * Through Apache and Nginx, as described earlier in this chapter. Any environment variables that you set on Apache and Nginx itself are inherited by Phusion Passenger, and thus by Phusion Passenger-served apps as well.
  * Through the application itself. Most programming languages provide APIs for setting environment variables. For example in Ruby you can write:

data/doc/users_guide_snippets/installation.txt

@@ -124,6 +124,18 @@ sudo chmod 600 /etc/apt/sources.list.d/passenger.list
 sudo apt-get update
 --------------------------------------------------------------
 
+5. (Optional) If using `unattended-upgrades`, add our APT repository to the list of `Allowed-Origins` for upgrades, `/etc/apt/apt.conf.d/50unattended-upgrades`:
++
+[source,sh]
+--------------------------------------------------------------
+// Automatically upgrade packages from these (origin:archive) pairs
+Unattended-Upgrade::Allowed-Origins {
+  // To check "Origin:" and "Suite:", you could use e.g.: 
+  // grep "Origin\|Suite" /var/lib/apt/lists/oss-binaries.phusionpassenger.com*
+  "Phusion:stable";
+};
+--------------------------------------------------------------
+
 ==== Installing packages
 
 ifdef::nginx[]
@@ -210,11 +222,13 @@ sudo apt-get install passenger-enterprise
 --------------------------------------------------------------
 endif::[]
 
+You can now proceed with a chapter for Deploying your (specific type of) application. 
+
 ifdef::nginx[]
 [[inserting_passenger_root_for_apt]]
 ==== Inserting `passenger_root` into nginx.conf
 
-During step 3 of the 'Installing packages' subsection, you were instructed to uncomment the <<PassengerRoot,passenger_root>> directive in `/etc/nginx/nginx.conf`. If there is no commented version in there, then you need to insert it yourself.
+If there is no <<PassengerRoot,passenger_root>> directive in `/etc/nginx/nginx.conf`, you can insert it yourself as follows:
 
 First, run the following command and take note of its output:
 
@@ -239,7 +253,6 @@ http {
 }
 -------------------------------------------------------------
 
-Once you're done editing nginx.conf, continue with step 4.
 endif::nginx[]