passenger 5.0.14 → 5.0.15

checksums.yaml

@@ -1,15 +1,15 @@
 ---
 !binary "U0hBMQ==":
   metadata.gz: !binary |-
-    ZTUyMzc2Mjc1MzllNDY0ZDM0M2I2YjIyNjYxN2U3MTEwNjc4ODNlOQ==
+    ODZjYzJlNjU3ZTVlODhjZGNlY2ZjYTIxZWUyMjQzZTIwNDQ1ZTIzNg==
   data.tar.gz: !binary |-
-    ODVlYTIxYzU5ODRiMDY2YTlmYTk5MGE1ODY0ZTIwNGQzMDkzMWE0NQ==
+    NWU1NGVmMTNiNGNjYmM0Y2E0MWE3YmM4MTAyZDVhZmNiNTFiMGZmZg==
 SHA512:
   metadata.gz: !binary |-
-    ZGYxMGIwZDI1MTZkYjI0MmY2NjgyOTM3ZjUzZjg5YmJmMjZlOWI4YjBlMzgz
-    ODEyOGU0NDY3ODA5MmFmZWE1N2U5ZWMzYzY1MTczMGY5ODQ2ZjEwNWMyNjAx
-    NGI0YjgxMGY2Yjk5ZjRiMjM2OTgwN2RmOTFkOWRhM2VlMjc1OGM=
+    ZGYzZTY5MmQzMjVjZmU3NGI0YjYxYTM1ZWIzY2I0YTk5ZmUwYTNlOGI5MDRm
+    OTk3MDc1MjNiZTJmZGVjOTY5OTQzYWM5NDEzN2Q5YTU0OGEyMWUwYTZkZGZi
+    YjRjMThjZmQ2OTdhZGE1ZTEwYjUwZGYyNmVhZWRjOGFlMGFlZmE=
   data.tar.gz: !binary |-
-    NGI3MTllM2JlOTQ3MjI1MzZmM2ZmMjdlNGQwMzQ1ZTRkOTcwZTc0OTU3MDgx
-    ZjA4NTJkMWU3YTdiYmQ2Y2VhNWFlNjZmOWI5N2NiZjViODBlZGQ5YzU4OWYw
-    MzgzMzVmNzQ4Y2UzM2YzM2JiZmJjMTNjOWQ4MGY0OGRkMmI2YmY=
+    NmE0MmU1OGZhOTM2ZTI3OGU2ZTFmMjIxZDIxYTZkMGUwM2I5ZjYyOGRmOTAx
+    NDkxODE1OGNkMDhmZTQxMWFkMDY2OTdhMTJkYzIwODE3ZDEzNjMyOWFlYjY0
+    MWM0NmI2OGFhNzAwMWFjZTNmOTE3NWM0YTM0NDEyMDk0MTgwMDU=

checksums.yaml.gz.asc

@@ -2,11 +2,11 @@
 Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
 Comment: GPGTools - http://gpgtools.org
 
-iQEcBAABAgAGBQJVpfw2AAoJECrHRaUKISqMNQ0IALwBrQrKoKjMGWtIShDJkcnO
-pyySi3t1XAFoAyedHVCNu85k4EzRFX4AdzCys2xutG348CKa0LmPoluGM1xeTvk/
-zrbVmRuMOt/7syef+9uqdVR3dcUrlqg0QoS5ysWFpjk4WX/RM7pcbVylx4NM5n/x
-A+uJFlvjzA18p6Teoos8LwRDfdywyQEKfthiAEqN/RPeOBl9AoZ9EyCZb4bHOjfx
-5unb5UlaxiaZa+MQgjbXq5kjwvgsgykWh1U8fcWxoUs7c/Oxtt0FoOOdoSb7c6fU
-tFlw4e642szl49RcOk8soj+tgOcUQYOpbyoZ9nlUqCesOvsOr6YnMdcAWh48Ql8=
-=hqMn
+iQEcBAABAgAGBQJVuJ34AAoJECrHRaUKISqMAv4H/2a7GvsZ/7rREszICP9/2hpE
+LJvK5PsjZHpM1xLyjGAeVP+h6WYanTUXhGYa57S1hEcxauF7SV6vQatSIWxNrmEy
+VjWXzSbJmaGc+MzOd/FaRXnHK2bNp/7QVsgrmOl50JA8dqD2Ub6kVmZ8iUH7Aa1m
+sp6Itegjs6C7wZuyaepQnyA6rOpvMnncZS/cY0UgucGriE++2wHYvgi/17nckP8t
+IUpX9T3LwporEUv1TDqszLnI2EVCrgW7Efm7/wVBLtp5pcwQOzQZB6VrB2flgZXc
+1fl1G2euM8zLrDc7iaXw1aceGdnB0wrJ3UhYebGkNkphir2fGD8Zj1pCjRfpCZk=
+=8Zp2
 -----END PGP SIGNATURE-----

data.tar.gz.asc

@@ -2,11 +2,11 @@
 Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
 Comment: GPGTools - http://gpgtools.org
 
-iQEcBAABAgAGBQJVpfw1AAoJECrHRaUKISqM2AAH/0H0z/5TLWyFnWd3ZipZ5yX/
-Ls373qV5k+PaHBHjHDti7d+/nRXFVXFTxbRRDbxuHvX7s/7o6yuligBKJTG9H5NQ
-JZ4ezdeq03WVzmuLuR/yw3vN1yCm85ouQY94HwTrxK/v6NQJn/qXro/47oDwp2h4
-b0FNsHfSDx2d8t91nyX+MRxdJzQ78d2Q36V/1usRHQcupxxMFd2AkW7KGc+OSaM4
-hREU8tsMgCDBcxTmFEsgwpOa8vGQG835PZvDEXDvw7SflKQhx6GV2lOhHJh5fMWN
-m0qyEdmM8nzfTU8oPI/51oMUAEh9kmWKrpkWrHU9cVdVunjPi9vpoxVOAOTY3WA=
-=NoNs
+iQEcBAABAgAGBQJVuJ34AAoJECrHRaUKISqM6soIALpuDRkmefIcwE9Tq/vrVE4/
+KsV/qPlJ6izfkfJhIAaQ8AZfXRzWV6vXD05FN91G7n7qgrBJbrd1ClS8lNEiey1C
+PM/o/0gGwJi5eIgPmtqhwLqjEhr561w5yKyW61d8NTiF0yEAX0w+XVKXfnmTjUb3
+H9uZJnFqBBMhaFHttqVtjB563+D+sK3YrqaDjzOS8bO7QgHv/G622/6bcnFMIqn6
+46drtEF3yuEWXTmu2JHBK4g169lzQKYlSMWj+PuWdzxZ4j4LVtWovw8qgISzwMrC
+1JVo0DcMM+q5/va8GtHHGrI1ozWqAF2Bfv3VDZ8hiq4YICi8hcNWD5c4cc7rewQ=
+=sIbu
 -----END PGP SIGNATURE-----

data/CHANGELOG

@@ -1,3 +1,12 @@
+Release 5.0.15
+--------------
+
+ * Support SHA256 digests for the Rails asset pipeline, as used by Sprockets 3.x.
+ * Support for JRuby 9.0.0.0. Closes GH-1562.
+ * Fixes some bugs in Union Station support, which causes some data (such as controller information and exceptions) to not be logged.
+ * The old Users Guides have been deprecated in favor of the [Passenger Library](https://www.phusionpassenger.com/library/). The Users Guides now redirect to appropriate sections in the Passenger Library.
+
+
 Release 5.0.14
 --------------
 

data/INSTALL.md

@@ -2,6 +2,6 @@
 
 Please read README.md for installation instructions.
 
-If you're having trouble installing Phusion Passenger, please refer to [the manual](http://www.modrails.com/documentation/Users%20guide.html).
+If you're having trouble installing Phusion Passenger, please refer to [the documentation](https://www.phusionpassenger.com/).
 
 Documentation and support resources are also available on [the website](https://www.phusionpassenger.com/documentation_and_support).

data/LICENSE

@@ -1,4 +1,4 @@
-Copyright (c) 2010-2013 Phusion
+Copyright (c) 2010-2015 Phusion Holding B.V.
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

data/README.md

@@ -16,7 +16,7 @@ Please follow [the installation instructions on the website](https://www.phusion
 
 ### Installing the source directly from git
 
-If you mean to install the latest version of Passenger directly from this git repository, then you should run one of the following commands. Installing from the git repository is basically the same as the tarball installation method, as [described in the manual](https://www.phusionpassenger.com/documentation/Users%20guide.html#installation).
+If you mean to install the latest version of Passenger directly from this git repository, then you should run one of the following commands. Installing from the git repository is basically the same as the tarball installation method, as [described in the manual](https://www.phusionpassenger.com/library/install/).
 
     ./bin/passenger-install-apache2-module
 

data/bin/passenger-install-apache2-module

@@ -103,12 +103,12 @@ class Installer < PhusionPassenger::AbstractInstaller
     return [specs, ids]
   end
 
-  def users_guide_path
-    return PhusionPassenger.apache2_doc_path
+  def install_doc_url
+    "https://www.phusionpassenger.com/library/install/apache/"
   end
 
-  def users_guide_url
-    return APACHE2_DOC_URL
+  def troubleshooting_doc_url
+    "https://www.phusionpassenger.com/library/admin/apache/troubleshooting/"
   end
 
   def run_steps
@@ -849,18 +849,14 @@ private
   def show_deployment_example
     new_screen
     render_template 'apache2/deployment_example',
-      :users_guide_path => users_guide_path,
-      :users_guide_url => users_guide_url,
+      :deployment_guide_url => "https://www.phusionpassenger.com/library/deploy/apache/deploy/",
       :phusion_website => PHUSION_WEBSITE,
-      :passenger_website => PASSENGER_WEBSITE,
-      :languages => @languages
+      :passenger_website => PASSENGER_WEBSITE
   end
 
   def show_possible_solutions_for_compilation_and_installation_problems
     new_screen
     render_template 'apache2/possible_solutions_for_compilation_and_installation_problems',
-      :users_guide_path => users_guide_path,
-      :users_guide_url => users_guide_url,
       :support_url => SUPPORT_URL
   end
 

data/bin/passenger-install-nginx-module

@@ -1,6 +1,6 @@
 #!/usr/bin/env ruby
 #  Phusion Passenger - https://www.phusionpassenger.com/
-#  Copyright (c) 2010-2014 Phusion
+#  Copyright (c) 2010-2015 Phusion
 #
 #  "Phusion Passenger" is a trademark of Hongli Lai & Ninh Bui.
 #
@@ -79,12 +79,12 @@ class Installer < PhusionPassenger::AbstractInstaller
     return [specs, ids]
   end
 
-  def users_guide_path
-    return PhusionPassenger.nginx_doc_path
+  def install_doc_url
+    "https://www.phusionpassenger.com/library/install/nginx/"
   end
 
-  def users_guide_url
-    return NGINX_DOC_URL
+  def troubleshooting_doc_url
+    "https://www.phusionpassenger.com/library/admin/nginx/troubleshooting/"
   end
 
   def run_steps
@@ -498,8 +498,7 @@ private
     line
     puts
     render_template 'nginx/deployment_example',
-      :users_guide_path => users_guide_path,
-      :users_guide_url => users_guide_url,
+      :deployment_guide_url => "https://www.phusionpassenger.com/library/deploy/nginx/deploy/",
       :phusion_website => PHUSION_WEBSITE,
       :passenger_website => PASSENGER_WEBSITE
   end
@@ -508,8 +507,6 @@ private
     line
     puts
     render_template 'nginx/possible_solutions_for_compilation_and_installation_problems',
-      :users_guide_path => users_guide_path,
-      :users_guide_url => users_guide_url,
       :support_url => SUPPORT_URL
   end
 

data/doc/CloudLicensingConfiguration.html

@@ -136,222 +136,7 @@
 
       <h1>Phusion Passenger Enterprise cloud licensing configuration</h1>
 
-<p>When using the <a href="https://www.phusionpassenger.com/enterprise">Phusion Passenger Enterprise</a> cloud license, you are billed per server per hour. There is a mechanism which automatically reports usage to the Phusion licensing server. This is implemented by sending a certain HTTPS request to the Phusion Passenger website, https://www.phusionpassenger.com, every 15 minutes, on every server that Phusion Passenger Enterprise is running with a cloud license.</p>
-
-<p>Sometimes, this manner of reporting usage data is not desirable, e.g. because of organizational security policies. For example, the servers that run Phusion Passenger Enterprise might block all outgoing traffic, or the network intrusion detection system might flag the usage reports as suspicious. To address these concerns, Phusion Passenger Enterprise 4.0.54 and later provide the ability to report usage through periodic batch jobs.</p>
-
-<h2>Conceptual overview</h2>
-
-<p>The setup works as follows:</p>
-
-<ol>
-<li>Phusion Passenger Enterprise stores usage data on the local disk, but does not send them to the Phusion licensing server.</li>
-<li>On each server that runs Phusion Passenger Enterprise, a batch job A generates a package from the usage data that's stored on disk.</li>
-<li>All these packages are copied to another machine (let's call this "Reporter"), e.g. through SCP, USB stick, etc. The reporter machine may be any machine that you choose, as long as it can access the Phusion licensing server. The method of copying does not matter.</li>
-<li>On the reporter machine, a batch job B uploads all these packages to the Phusion licensing server.</li>
-</ol>
-
-
-<p><img src="images/cloud_licensing_batch_job.png" alt="Conceptual overview" /></p>
-
-<h2>Phase 1: setting up web servers</h2>
-
-<p>Follow these instructions on each server running Phusion Passenger Enterprise with a cloud license.</p>
-
-<ol>
-<li><p>Login to the web server and open a superuser shell. For example:</p>
-
-<pre><code>bash$ sudo -H bash
-</code></pre>
-
-<p>Or, if you're an RVM user, use rvmsudo instead of sudo:</p>
-
-<pre><code>bash$ rvmsudo -H bash
-</code></pre></li>
-<li><p>Add the following configuration to your Apache or Nginx configuration file:</p>
-
-<pre><code># Apache
-PassengerCtl licensing_data_points_auto_send false
-
-# Nginx
-passenger_ctl licensing_data_points_auto_send false;
-</code></pre>
-
-<p>Then restart Apache/Nginx. This configuration tells Phusion Passenger Enterprise not to automatically send usage data to the Phusion licensing server.</p></li>
-<li><p>Find out what user the Passenger core process is running as.</p>
-
-<p>First, look for the PID of the Passenger core process.</p>
-
-<pre><code>bash# passenger-memory-stats
-...
------- Passenger processes ------
-PID    VMSize     Resident  Name
----------------------------------
-11243  2405.8 MB  2.7 MB    Passenger: core
-...
-</code></pre>
-
-<p>Then use <code>ps</code> to determine what user it's running as. Usually, it's running as root.</p>
-
-<pre><code>bash# ps -o pid,user -p 11243
-  PID USER
-11245 root
-</code></pre></li>
-<li><p>Create a directory in which to store usage data packages. For example:</p>
-
-<pre><code>bash# mkdir /var/lib/passenger-enterprise-usage
-</code></pre>
-
-<p>Ensure that it's owned by the user that the core runs as, and make it owner-accessible only:</p>
-
-<pre><code>bash# chown root: /var/lib/passenger-enterprise-usage
-bash# chmod 700 /var/lib/passenger-enterprise-usage
-</code></pre></li>
-<li><p>Create a script inside the previous directory for generating a usage data package, and for copying packages to the reporter machine. This script is part of batch job A.</p>
-
-<pre><code>bash# touch /var/lib/passenger-enterprise-usage/script
-bash# chmod +x /var/lib/passenger-enterprise-usage/script
-bash# editor /var/lib/passenger-enterprise-usage/script
-</code></pre>
-
-<p>The script should contain:</p>
-
-<pre><code>#!/bin/bash
-set -e
-
-REPORTER_MACHINE=foo@reporter-machine-host-name
-HOSTNAME=`hostname`
-DATE=`date +%s`
-
-set -x
-passenger-config package-cloud-usage /var/lib/passenger-enterprise-usage/$HOSTNAME-$DATE.tar.gz
-scp /var/lib/passenger-enterprise-usage/*.tar.gz $REPORTER_MACHINE:passenger-enterprise-usage/
-rm -f /var/lib/passenger-enterprise-usage/*.tar.gz
-</code></pre>
-
-<p>Here, <code>foo@reporter-machine-host-name</code> specifies which reporter machine you want to copy the package to, and which username you want to use to login to the reporter machine. Replace this with an appropriate value.</p>
-
-<p><strong>Notes about SSH keys</strong>: don't forget to setup SSH keys so that the script can scp to the reporter machine. The script will be run as the user that the Passenger core is running as.</p>
-
-<p><strong>Notes about PATH</strong>: the above script assumes that the <code>passenger-config</code> command is in PATH. This is always the case if you installed Passenger Enterprise using Debian or RPM packages, but may not be the case if you installed it using RubyGems or tarball. If it's not in PATH, or when in doubt, you should specify the full path to passenger-config. You can find out where passenger-config is using <code>which</code>. For example:</p>
-
-<pre><code>bash# which passenger-config
-/opt/passenger-enterprise-x.x.x/bin/passenger-config
-</code></pre>
-
-<p>Then the script should call:</p>
-
-<pre><code>/opt/passenger-enterprise-x.x.x/bin/passenger-config package-cloud-usage ...
-</code></pre></li>
-<li><p>Open the crontab of the user that the Passenger core is running as. For example, if the core is running as root:</p>
-
-<pre><code>bash# sudo -u root -H crontab -e
-</code></pre></li>
-<li><p>Insert the following entry into the crontab, so that the script is invoked on the 1st of every month:</p>
-
-<pre><code>0 0 1 * * /var/lib/passenger-enterprise-usage/script
-</code></pre></li>
-<li><p>Ensure that <code>/var/lib/passenger-enterprise-usage/script</code> is run during system shutdown, as the user that the Passenger core is running as. On most Linux systems, this can be achieved by as follows:</p>
-
-<pre><code>bash# touch /etc/init.d/passenger-enterprise-cloud-license
-bash# chmod +x /etc/init.d/passenger-enterprise-cloud-license
-bash# ln -s /etc/init.d/passenger-enterprise-cloud-license /etc/rc0.d/K00passenger-enterprise-cloud-license
-bash# ln -s /etc/init.d/passenger-enterprise-cloud-license /etc/rc6.d/K00passenger-enterprise-cloud-license
-bash# editor /etc/init.d/passenger-enterprise-cloud-license
-</code></pre>
-
-<p>If the Passenger core is running as root, then <code>/etc/init.d/passenger-enterprise-cloud-license</code> should contain:</p>
-
-<pre><code>#!/bin/bash
-set -e
-exec /var/lib/passenger-enterprise-usage/script
-</code></pre>
-
-<p>If the Passenger core is not running as root, then it should contain:</p>
-
-<pre><code>#!/bin/bash
-set -e
-exec sudo -u PROPER_USERNAME_HERE -H /var/lib/passenger-enterprise-usage/script
-</code></pre>
-
-<p>Or, if you're an RVM user, use rvmsudo instead of sudo:</p>
-
-<pre><code>#!/bin/bash
-set -e
-exec rvmsudo -u PROPER_USERNAME_HERE -H /var/lib/passenger-enterprise-usage/script
-</code></pre>
-
-<p><strong>Note:</strong> If your operating system does not respect /etc/rcX.d, please consult your operating system's manual to learn how to run <code>/var/lib/passenger-enterprise-usage/script</code> during system shutdown.</p></li>
-</ol>
-
-
-<h2>Phase 2: setting up the "reporter" machine</h2>
-
-<p>In phase 1, you've setup web servers to scp usage data packages to the reporter machine, by logging into the reporter machine as a certain user. Let's call that user "foo".</p>
-
-<ol>
-<li><p>Login to the reporter machine as user foo.</p></li>
-<li><p>Create a directory that the web servers can scp into:</p>
-
-<pre><code>bash$ mkdir ~/passenger-enterprise-usage
-bash$ chmod 700 ~/passenger-enterprise-usage
-</code></pre></li>
-<li><p>Install the <a href="https://github.com/phusion/passenger-enterprise-bulk-send-cloud-usage">passenger-enterprise-bulk-send-cloud-usage</a> tool:</p>
-
-<pre><code>bash$ cd ~
-bash$ curl -L -O https://github.com/phusion/passenger-enterprise-bulk-send-cloud-usage/archive/master.tar.gz
-bash$ tar xzvf master.tar.gz &amp;&amp; rm master.tar.gz
-</code></pre></li>
-<li><p>Open the crontab of user foo:</p>
-
-<pre><code>bash$ crontab -e
-</code></pre></li>
-<li><p>Insert the following entry into the crontab to upload usage data packages on the 1st of every month:</p>
-
-<pre><code>0 1 1 * * ~/passenger-enterprise-bulk-send-cloud-usage/passenger-enterprise-bulk-send-cloud-usage --delete ~/passenger-enterprise-usage-*.tar.gz
-</code></pre>
-
-<p>This crontab entry is batch job B as described in the conceptual overview.</p>
-
-<p>Note that this command is run at 1 AM: 1 hour after the web servers have generated usage data packages and copied them over to the reporter machine. You <em>must</em> therefore ensure that the clocks on the web servers and the reporter machine are properly synchronized, and that they are set to the same time zone.</p></li>
-</ol>
-
-
-<h2>Phase 3: testing</h2>
-
-<p>Once the web servers and the reporter machine are all setup, you can test whether the setup works correctly.</p>
-
-<ol>
-<li><p>On each web server, run <code>/var/lib/passenger-enterprise-usage/script</code> as the user that the Passenger core runs as. For example, if the core is running as root:</p>
-
-<pre><code>sudo -u root -H /var/lib/passenger-enterprise-usage/script
-</code></pre>
-
-<p>Or, if you're an RVM user, use rvmsudo instead of sudo:</p>
-
-<pre><code>rvmsudo -u root -H /var/lib/passenger-enterprise-usage/script
-</code></pre>
-
-<p>You should see output like this:</p>
-
-<pre><code>+ passenger-config package-cloud-usage /var/lib/passenger-enterprise-usage/myhostname-1415377926.tar.gz
-+ scp /var/lib/passenger-enterprise-usage/myhostname-1415377310.tar.gz hongli@localhost:passenger-enterprise-usage/
-myhostname-1415377310.tar.gz                     100%  605     0.6KB/s   00:00
-+ rm -f /var/lib/passenger-enterprise-usage/myhostname-1415377310.tar.gz
-</code></pre></li>
-<li><p>Login to the reporter machine as the "foo" user (as described in phase 2) and run:</p>
-
-<pre><code>~/passenger-enterprise-bulk-send-cloud-usage-master/passenger-enterprise-bulk-send-cloud-usage --delete ~/passenger-enterprise-usage/*.tar.gz
-</code></pre>
-
-<p>You should see output like this:</p>
-
-<pre><code>---- Uploading ~/passenger-enterprise-usage/myhostname-1415377310.tar.gz -----
-Success!
-Deleting ~/passenger-enterprise-usage/myhostname-1415377310.tar.gz
-</code></pre></li>
-<li><p>Login to the <a href="https://www.phusionpassenger.com/orders">Phusion Passenger Enterprise Customer Area</a>. Under "Cloud subscription status", click "View usage details". Verify that usage has been properly registered.</p></li>
-</ol>
+<p>This documentation has moved. Please visit <a href="https://www.phusionpassenger.com/library/config/cloud_licensing_configuration/">https://www.phusionpassenger.com/library/config/cloud<em>licensing</em>configuration/</a></p>
 
 
       <footer>

data/doc/CloudLicensingConfiguration.txt.md

@@ -1,194 +1,3 @@
 # Phusion Passenger Enterprise cloud licensing configuration
 
-When using the [Phusion Passenger Enterprise](https://www.phusionpassenger.com/enterprise) cloud license, you are billed per server per hour. There is a mechanism which automatically reports usage to the Phusion licensing server. This is implemented by sending a certain HTTPS request to the Phusion Passenger website, https://www.phusionpassenger.com, every 15 minutes, on every server that Phusion Passenger Enterprise is running with a cloud license.
-
-Sometimes, this manner of reporting usage data is not desirable, e.g. because of organizational security policies. For example, the servers that run Phusion Passenger Enterprise might block all outgoing traffic, or the network intrusion detection system might flag the usage reports as suspicious. To address these concerns, Phusion Passenger Enterprise 4.0.54 and later provide the ability to report usage through periodic batch jobs.
-
-## Conceptual overview
-
-The setup works as follows:
-
- 1. Phusion Passenger Enterprise stores usage data on the local disk, but does not send them to the Phusion licensing server.
- 2. On each server that runs Phusion Passenger Enterprise, a batch job A generates a package from the usage data that's stored on disk.
- 3. All these packages are copied to another machine (let's call this "Reporter"), e.g. through SCP, USB stick, etc. The reporter machine may be any machine that you choose, as long as it can access the Phusion licensing server. The method of copying does not matter.
- 4. On the reporter machine, a batch job B uploads all these packages to the Phusion licensing server.
-
-![Conceptual overview](images/cloud_licensing_batch_job.png)
-
-## Phase 1: setting up web servers
-
-Follow these instructions on each server running Phusion Passenger Enterprise with a cloud license.
-
- 1. Login to the web server and open a superuser shell. For example:
-
-        bash$ sudo -H bash
-
-    Or, if you're an RVM user, use rvmsudo instead of sudo:
-
-        bash$ rvmsudo -H bash
-
- 2. Add the following configuration to your Apache or Nginx configuration file:
-
-        # Apache
-        PassengerCtl licensing_data_points_auto_send false
-
-        # Nginx
-        passenger_ctl licensing_data_points_auto_send false;
-
-    Then restart Apache/Nginx. This configuration tells Phusion Passenger Enterprise not to automatically send usage data to the Phusion licensing server.
-
- 3. Find out what user the Passenger core process is running as.
-
-    First, look for the PID of the Passenger core process.
-
-        bash# passenger-memory-stats
-        ...
-        ------ Passenger processes ------
-        PID    VMSize     Resident  Name
-        ---------------------------------
-        11243  2405.8 MB  2.7 MB    Passenger: core
-        ...
-
-    Then use `ps` to determine what user it's running as. Usually, it's running as root.
-
-        bash# ps -o pid,user -p 11243
-          PID USER
-        11245 root
-
- 4. Create a directory in which to store usage data packages. For example:
-
-        bash# mkdir /var/lib/passenger-enterprise-usage
-
-    Ensure that it's owned by the user that the core runs as, and make it owner-accessible only:
-
-        bash# chown root: /var/lib/passenger-enterprise-usage
-        bash# chmod 700 /var/lib/passenger-enterprise-usage
-
- 5. Create a script inside the previous directory for generating a usage data package, and for copying packages to the reporter machine. This script is part of batch job A.
-
-        bash# touch /var/lib/passenger-enterprise-usage/script
-        bash# chmod +x /var/lib/passenger-enterprise-usage/script
-        bash# editor /var/lib/passenger-enterprise-usage/script
-
-    The script should contain:
-
-        #!/bin/bash
-        set -e
-
-        REPORTER_MACHINE=foo@reporter-machine-host-name
-        HOSTNAME=`hostname`
-        DATE=`date +%s`
-
-        set -x
-        passenger-config package-cloud-usage /var/lib/passenger-enterprise-usage/$HOSTNAME-$DATE.tar.gz
-        scp /var/lib/passenger-enterprise-usage/*.tar.gz $REPORTER_MACHINE:passenger-enterprise-usage/
-        rm -f /var/lib/passenger-enterprise-usage/*.tar.gz
-
-    Here, `foo@reporter-machine-host-name` specifies which reporter machine you want to copy the package to, and which username you want to use to login to the reporter machine. Replace this with an appropriate value.
-
-    **Notes about SSH keys**: don't forget to setup SSH keys so that the script can scp to the reporter machine. The script will be run as the user that the Passenger core is running as.
-
-    **Notes about PATH**: the above script assumes that the `passenger-config` command is in PATH. This is always the case if you installed Passenger Enterprise using Debian or RPM packages, but may not be the case if you installed it using RubyGems or tarball. If it's not in PATH, or when in doubt, you should specify the full path to passenger-config. You can find out where passenger-config is using `which`. For example:
-
-        bash# which passenger-config
-        /opt/passenger-enterprise-x.x.x/bin/passenger-config
-
-    Then the script should call:
-
-        /opt/passenger-enterprise-x.x.x/bin/passenger-config package-cloud-usage ...
-
- 6. Open the crontab of the user that the Passenger core is running as. For example, if the core is running as root:
-
-        bash# sudo -u root -H crontab -e
-
- 7. Insert the following entry into the crontab, so that the script is invoked on the 1st of every month:
-
-        0 0 1 * * /var/lib/passenger-enterprise-usage/script
-
- 8. Ensure that `/var/lib/passenger-enterprise-usage/script` is run during system shutdown, as the user that the Passenger core is running as. On most Linux systems, this can be achieved by as follows:
-
-        bash# touch /etc/init.d/passenger-enterprise-cloud-license
-        bash# chmod +x /etc/init.d/passenger-enterprise-cloud-license
-        bash# ln -s /etc/init.d/passenger-enterprise-cloud-license /etc/rc0.d/K00passenger-enterprise-cloud-license
-        bash# ln -s /etc/init.d/passenger-enterprise-cloud-license /etc/rc6.d/K00passenger-enterprise-cloud-license
-        bash# editor /etc/init.d/passenger-enterprise-cloud-license
-
-    If the Passenger core is running as root, then `/etc/init.d/passenger-enterprise-cloud-license` should contain:
-
-        #!/bin/bash
-        set -e
-        exec /var/lib/passenger-enterprise-usage/script
-
-    If the Passenger core is not running as root, then it should contain:
-
-        #!/bin/bash
-        set -e
-        exec sudo -u PROPER_USERNAME_HERE -H /var/lib/passenger-enterprise-usage/script
-
-    Or, if you're an RVM user, use rvmsudo instead of sudo:
-
-        #!/bin/bash
-        set -e
-        exec rvmsudo -u PROPER_USERNAME_HERE -H /var/lib/passenger-enterprise-usage/script
-
-    **Note:** If your operating system does not respect /etc/rcX.d, please consult your operating system's manual to learn how to run `/var/lib/passenger-enterprise-usage/script` during system shutdown.
-
-## Phase 2: setting up the "reporter" machine
-
-In phase 1, you've setup web servers to scp usage data packages to the reporter machine, by logging into the reporter machine as a certain user. Let's call that user "foo".
-
- 1. Login to the reporter machine as user foo.
-
- 2. Create a directory that the web servers can scp into:
-
-        bash$ mkdir ~/passenger-enterprise-usage
-        bash$ chmod 700 ~/passenger-enterprise-usage
-
- 3. Install the [passenger-enterprise-bulk-send-cloud-usage](https://github.com/phusion/passenger-enterprise-bulk-send-cloud-usage) tool:
-
-        bash$ cd ~
-        bash$ curl -L -O https://github.com/phusion/passenger-enterprise-bulk-send-cloud-usage/archive/master.tar.gz
-        bash$ tar xzvf master.tar.gz && rm master.tar.gz
-
- 4. Open the crontab of user foo:
-
-        bash$ crontab -e
-
- 5. Insert the following entry into the crontab to upload usage data packages on the 1st of every month:
-
-        0 1 1 * * ~/passenger-enterprise-bulk-send-cloud-usage/passenger-enterprise-bulk-send-cloud-usage --delete ~/passenger-enterprise-usage-*.tar.gz
-
-    This crontab entry is batch job B as described in the conceptual overview.
-
-    Note that this command is run at 1 AM: 1 hour after the web servers have generated usage data packages and copied them over to the reporter machine. You *must* therefore ensure that the clocks on the web servers and the reporter machine are properly synchronized, and that they are set to the same time zone.
-
-## Phase 3: testing
-
-Once the web servers and the reporter machine are all setup, you can test whether the setup works correctly.
-
- 1. On each web server, run `/var/lib/passenger-enterprise-usage/script` as the user that the Passenger core runs as. For example, if the core is running as root:
-
-        sudo -u root -H /var/lib/passenger-enterprise-usage/script
-
-    Or, if you're an RVM user, use rvmsudo instead of sudo:
-
-        rvmsudo -u root -H /var/lib/passenger-enterprise-usage/script
-
-    You should see output like this:
-
-        + passenger-config package-cloud-usage /var/lib/passenger-enterprise-usage/myhostname-1415377926.tar.gz
-        + scp /var/lib/passenger-enterprise-usage/myhostname-1415377310.tar.gz hongli@localhost:passenger-enterprise-usage/
-        myhostname-1415377310.tar.gz                     100%  605     0.6KB/s   00:00
-        + rm -f /var/lib/passenger-enterprise-usage/myhostname-1415377310.tar.gz
-
- 2. Login to the reporter machine as the "foo" user (as described in phase 2) and run:
-
-        ~/passenger-enterprise-bulk-send-cloud-usage-master/passenger-enterprise-bulk-send-cloud-usage --delete ~/passenger-enterprise-usage/*.tar.gz
-
-    You should see output like this:
-
-        ---- Uploading ~/passenger-enterprise-usage/myhostname-1415377310.tar.gz -----
-        Success!
-        Deleting ~/passenger-enterprise-usage/myhostname-1415377310.tar.gz
-
- 3. Login to the [Phusion Passenger Enterprise Customer Area](https://www.phusionpassenger.com/orders). Under "Cloud subscription status", click "View usage details". Verify that usage has been properly registered.
+This documentation has moved. Please visit [https://www.phusionpassenger.com/library/config/cloud_licensing_configuration/](https://www.phusionpassenger.com/library/config/cloud_licensing_configuration/)