passenger 4.0.60 → 5.0.0.beta1

data/lib/phusion_passenger/standalone/runtime_locator.rb

@@ -1,170 +0,0 @@
-# encoding: utf-8
-#  Phusion Passenger - https://www.phusionpassenger.com/
-#  Copyright (c) 2013 Phusion
-#
-#  "Phusion Passenger" is a trademark of Hongli Lai & Ninh Bui.
-#
-#  Permission is hereby granted, free of charge, to any person obtaining a copy
-#  of this software and associated documentation files (the "Software"), to deal
-#  in the Software without restriction, including without limitation the rights
-#  to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-#  copies of the Software, and to permit persons to whom the Software is
-#  furnished to do so, subject to the following conditions:
-#
-#  The above copyright notice and this permission notice shall be included in
-#  all copies or substantial portions of the Software.
-#
-#  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-#  IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-#  FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-#  AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-#  LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-#  OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-#  THE SOFTWARE.
-
-PhusionPassenger.require_passenger_lib 'platform_info/binary_compatibility'
-PhusionPassenger.require_passenger_lib 'utils/json'
-require 'etc'
-
-module PhusionPassenger
-module Standalone
-
-# Helper class for locating runtime files used by Passenger Standalone.
-class RuntimeLocator
-	attr_reader :runtime_dir
-
-	def initialize(runtime_dir, nginx_version = PhusionPassenger::PREFERRED_NGINX_VERSION)
-		@runtime_dir = runtime_dir || default_runtime_dir
-		@nginx_version = nginx_version
-	end
-
-	def self.looks_like_support_dir?(dir)
-		File.exist?("#{dir}/agents/PassengerWatchdog") &&
-			File.exist?("#{dir}/common/libboost_oxt.a") &&
-			File.exist?("#{dir}/common/libpassenger_common/ApplicationPool2/Implementation.o")
-	end
-
-	def reload
-		@has_support_dir = @has_nginx_binary = false
-	end
-
-	# Returns the directory in which Passenger Standalone
-	# support binaries are stored, or nil if not installed.
-	def find_support_dir
-		return @support_dir if @has_support_dir
-
-		if PhusionPassenger.originally_packaged?
-			if debugging?
-				@support_dir = PhusionPassenger.buildout_dir
-			else
-				dir = "#{@runtime_dir}/#{version}/support-#{cxx_compat_id}"
-				if self.class.looks_like_support_dir?(dir)
-					@support_dir = dir
-				else
-					@support_dir = nil
-				end
-			end
-		else
-			@support_dir = PhusionPassenger.lib_dir
-		end
-		@has_support_dir = true
-		return @support_dir
-	end
-
-	# Returns the path to the Nginx binary that Passenger Standalone
-	# may use, or nil if not installed.
-	def find_nginx_binary
-		return @nginx_binary if @has_nginx_binary
-
-		if File.exist?(config_filename)
-			config = PhusionPassenger::Utils::JSON.parse(File.read(config_filename))
-		else
-			config = {}
-		end
-		if result = config["nginx_binary"]
-			@nginx_binary = result
-		elsif PhusionPassenger.natively_packaged? && @nginx_version == PhusionPassenger::PREFERRED_NGINX_VERSION
-			@nginx_binary = "#{PhusionPassenger.lib_dir}/PassengerWebHelper"
-		else
-			filename = "#{@runtime_dir}/#{version}/webhelper-#{@nginx_version}-#{cxx_compat_id}/PassengerWebHelper"
-			if File.exist?(filename)
-				@nginx_binary = filename
-			else
-				@nginx_binary = nil
-			end
-		end
-		@has_nginx_binary = true
-		return @nginx_binary
-	end
-
-	def find_agents_dir
-		return "#{find_support_dir}/agents"
-	end
-
-	def find_lib_dir
-		return find_support_dir
-	end
-
-	def everything_installed?
-		return find_support_dir && find_nginx_binary
-	end
-
-	def install_targets
-		result = []
-		result << :nginx if find_nginx_binary.nil?
-		result << :support_binaries if find_support_dir.nil?
-		return result
-	end
-
-	# Returns the directory to which support binaries may be installed,
-	# in case the RuntimeInstaller is to be invoked.
-	def support_dir_install_destination
-		if PhusionPassenger.originally_packaged?
-			if debugging?
-				return "#{PhusionPassenger.lib_dir}/common/libpassenger_common"
-			else
-				return "#{@runtime_dir}/#{version}/support-#{cxx_compat_id}"
-			end
-		else
-			return nil
-		end
-	end
-
-	# Returns the directory to which the Nginx binary may be installed,
-	# in case the RuntimeInstaller is to be invoked.
-	def nginx_binary_install_destination
-		return "#{@runtime_dir}/#{version}/webhelper-#{@nginx_version}-#{cxx_compat_id}"
-	end
-
-private
-	def default_runtime_dir
-		if Process.uid == 0
-			# It is important that the default runtime dir for the root user
-			# is a publicly accessible directory, because when --user is given,
-			# the agents are run as non-root users.
-			return "/var/lib/#{GLOBAL_NAMESPACE_DIRNAME}/standalone"
-		else
-			home = Etc.getpwuid.dir
-			return "#{home}/#{USER_NAMESPACE_DIRNAME}/standalone"
-		end
-	end
-
-	def debugging?
-		return ['yes', 'y', 'true', '1'].include?(ENV['PASSENGER_DEBUG'].to_s.downcase)
-	end
-
-	def version
-		return PhusionPassenger::VERSION_STRING
-	end
-
-	def cxx_compat_id
-		return PlatformInfo.cxx_binary_compatibility_id
-	end
-
-	def config_filename
-		return "#{@runtime_dir}/config.json"
-	end
-end
-
-end # module Standalone
-end # module PhusionPassenger

data/lib/phusion_passenger/standalone/utils.rb

@@ -1,58 +0,0 @@
-#  Phusion Passenger - https://www.phusionpassenger.com/
-#  Copyright (c) 2010-2014 Phusion
-#
-#  "Phusion Passenger" is a trademark of Hongli Lai & Ninh Bui.
-#
-#  Permission is hereby granted, free of charge, to any person obtaining a copy
-#  of this software and associated documentation files (the "Software"), to deal
-#  in the Software without restriction, including without limitation the rights
-#  to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-#  copies of the Software, and to permit persons to whom the Software is
-#  furnished to do so, subject to the following conditions:
-#
-#  The above copyright notice and this permission notice shall be included in
-#  all copies or substantial portions of the Software.
-#
-#  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-#  IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-#  FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-#  AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-#  LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-#  OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-#  THE SOFTWARE.
-
-module PhusionPassenger
-module Standalone
-
-module Utils
-private
-	def require_platform_info_binary_compatibility
-		if !defined?(PlatformInfo) || !PlatformInfo.respond_to?(:cxx_binary_compatibility_id)
-			PhusionPassenger.require_passenger_lib 'platform_info/binary_compatibility'
-		end
-	end
-
-	def runtime_version_string(nginx_version)
-		if PhusionPassenger.originally_packaged? || nginx_version != PhusionPassenger::PREFERRED_NGINX_VERSION
-			require_platform_info_binary_compatibility
-			return "#{VERSION_STRING}-#{PlatformInfo.passenger_binary_compatibility_id}"
-		else
-			return VERSION_STRING
-		end
-	end
-
-	# Dir.pwd resolves symlinks. So in turn, File.expand_path/File.absolute_path
-	# do that too. We work around that by shelling out to the `pwd` tool.
-	if File.respond_to?(:absolute_path)
-		def absolute_path(path)
-			return File.absolute_path(path, `pwd`.strip)
-		end
-	else
-		def absolute_path(path)
-			return File.expand_path(path, `pwd`.strip)
-		end
-	end
-end
-
-end
-end

data/lib/phusion_passenger/utils/tmpdir.rb

@@ -1,69 +0,0 @@
-#  Phusion Passenger - https://www.phusionpassenger.com/
-#  Copyright (c) 2010 Phusion
-#
-#  "Phusion Passenger" is a trademark of Hongli Lai & Ninh Bui.
-#
-#  Permission is hereby granted, free of charge, to any person obtaining a copy
-#  of this software and associated documentation files (the "Software"), to deal
-#  in the Software without restriction, including without limitation the rights
-#  to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-#  copies of the Software, and to permit persons to whom the Software is
-#  furnished to do so, subject to the following conditions:
-#
-#  The above copyright notice and this permission notice shall be included in
-#  all copies or substantial portions of the Software.
-#
-#  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-#  IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-#  FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-#  AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-#  LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-#  OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-#  THE SOFTWARE.
-
-module PhusionPassenger
-
-module Utils
-protected
-	@@passenger_tmpdir = nil
-	
-	def passenger_tmpdir(create = true)
-		PhusionPassenger::Utils.passenger_tmpdir(create)
-	end
-	
-	# Returns the directory in which to store Phusion Passenger-specific
-	# temporary files. If +create+ is true, then this method creates the
-	# directory if it doesn't exist.
-	def self.passenger_tmpdir(create = true)
-		dir = @@passenger_tmpdir
-		if dir.nil? || dir.empty?
-			tmpdir = "/tmp"
-			["PASSENGER_TEMP_DIR", "PASSENGER_TMPDIR"].each do |name|
-				if ENV.has_key?(name) && !ENV[name].empty?
-					tmpdir = ENV[name]
-					break
-				end
-			end
-			dir = "#{tmpdir}/passenger.1.0.#{Process.pid}"
-			dir.gsub!(%r{//+}, '/')
-			@@passenger_tmpdir = dir
-		end
-		if create && !File.exist?(dir)
-			# This is a very minimal implementation of the subdirectory
-			# creation logic in ServerInstanceDir.h. This implementation
-			# is only meant to make the unit tests pass. For production
-			# systems one should pre-create the temp directory with
-			# ServerInstanceDir.h.
-			system("mkdir", "-p", "-m", "u=rwxs,g=rwx,o=rwx", dir)
-			system("mkdir", "-p", "-m", "u=rwxs,g=rwx,o=rwx", "#{dir}/generation-0")
-			system("mkdir", "-p", "-m", "u=rwxs,g=rwx,o=rwx", "#{dir}/backends")
-		end
-		return dir
-	end
-	
-	def self.passenger_tmpdir=(dir)
-		@@passenger_tmpdir = dir
-	end
-end
-
-end

data/packaging/debian/LICENSE.md

@@ -1,19 +0,0 @@
-Copyright (c) 2013-2015 Phusion
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.

data/packaging/debian/README.md

@@ -1,320 +0,0 @@
-# Phusion Passenger Debian packaging project
-
-This repository contains Debian package definitions for [Phusion Passenger](https://www.phusionpassenger.com/), as well as tools for automatically building Passenger packages for multiple distributions and architectures.
-
-The goal of this project is twofold:
-
- 1. To allow Phusion to release Debian packages for multiple distributions and architectures, immediately after a Passenger source release, in a completely automated manner.
- 2. To allow users to build their own Debian packages for Passenger, without having to wait for Phusion to do so.
-
-> Are you a user who wants to build your own packages for a Passenger version that hasn't been released yet? Read [Tutorial: building your own packages](#tutorial-building-your-own-packages).
-
-**Table of Contents**
-
- * [Overview](#overview)
- * [Development](#development)
- * [Package building process](#package-building-process)
-   - [The build script](#the-build-script)
-   - [The test script](#the-test-script)
-   - [The publish script](#the-publish-script)
- * [Maintenance](#maintenance)
-   - [Adding support for a new distribution](#adding-support-for-a-new-distribution)
-   - [Building Nginx packages only](#building-nginx-packages-only)
-   - [Updating SSL certificates](#updating-ssl-certificates)
- * [Jenkins integration](#jenkins-integration)
-   - [Debugging a packaging test failure](#debugging-a-packaging-test-failure)
- * [Tutorial: building your own packages](#tutorial-building-your-own-packages)
- * [Related projects](#related-projects)
-
-## Overview
-
-This project consists of three major tools:
-
- * **build** -- Given a Passenger source directory, this script builds Debian packages for it.
- * **test** -- Given a directory with built Debian packages (as produced by the `build` script), this script runs tests against them.
- * **publish** -- Given a directory with built Debian packages, this script publishes them to [PackageCloud](https://packagecloud.io/).
-
-Debian package definitions are located in the `debian_specs` directory:
-
- * `debian_specs/passenger` -- Package definitions for Passenger, open source edition.
- * `debian_specs/passenger-enterprise` -- Package definitions for [Passenger Enterprise](https://www.phusionpassenger.com/enterprise).
- * `debian_specs/nginx` -- Package definitions for Nginx, with Passenger compiled in.
-
-Other noteworthy tools:
-
- * `shell` -- Open a shell in the buildbox container for debugging purposes.
- * `jenkins` -- Scripts to be run by our Jenkins continuous integration jobs, either after every commit or during release time.
-
-This project utilizes Docker for isolation. Because of the usage of Docker, these tools can be run on any 64-bit Linux system, including non-Debian-based systems. Though in practice, we've only tested on Ubuntu.
-
-## Development
-
-This repository is included as a git submodule in the Passenger git repository, under the directory `packaging/debian`. Instead of cloning the `passenger_apt_automation` repository directly, you should clone the Passenger git repository, and work in the `packaging/debian` directory instead. This scheme allows each Passenger version to lock down to a specific version of `passenger_apt_automation`.
-
-A Vagrantfile is provided so that you can develop this project in a VM. To get started, run:
-
-    host$ vagrant up
-
-The Passenger source directory (`../..`) will be automatically mounted inside the VM under `/passenger`.
-
-## Package building process
-
-The package build process is as follows. First, the `build` script is used to build Debian packages from a Passenger source code directory. Next, either the `test` script is run to test the built packages, or the `publish` script is run to publish the built packages to PackageCloud.
-
-    build   ------------>   test
-                 \
-                  \----->   publish
-
-### The build script
-
-Everything begins with the `build` script and a copy of the Passenger source code. Here's an example invocation:
-
-    ./build -p /passenger -w work -c cache -o output pkg:all
-
- * `-p` tells it where the Passenger source code is.
- * `-w` tells it where it's work directory is. This is a directory in which in stores temporary files while building packages. WARNING: everything inside this directory will be deleted before the build begins, so only specify a directory that doesn't contain anything important.
- * `-c` tells it where the cache directory is. The build script caches files into this directory so that subsequent runs will be faster.
- * `-o` tells it where to store the final built Debian packages (the output directory). WARNING: everything inside this directory will be deleted when the build finishes, so only specify a directory that doesn't contain anything important.
- * The final argument, `pkg:all`, is the task that the build script must run. The build script provides a number of tasks, such as tasks for building packages for specific distributions or architecture only, or tasks for building source packages only. The `pkg:all` task builds all source and binary packages for all supported distributions and architectures.
-
-More command line options are available. Run `./build -h` to learn more. You can also run `./build -T` to learn which tasks are available.
-
-When the build script is finished, the output directory (`-o`) will contain one subdirectory per distribution that was built for, with each subdirectory containing packages for that distribution (in all architectures that were built for). For example:
-
-    output/
-      |
-      +-- trusty/
-      |      |
-      |      +-- *.deb
-      |      |
-      |      +-- *.dsc
-      |
-      +-- precise/
-      |      |
-      |      +-- *.deb
-      |      |
-      |      +-- *.dsc
-      |
-     ...
-
-#### Vagrant notes
-
-When using Vagrant, the directories referred to by `-w` and `-c` must be native filesystem directories. That is, they may not be located inside /vagrant, because /vagrant is a remote filesystem. I typically use `-w ~/work -c ~/cache` when developing with Vagrant.
-
-#### Troubleshooting
-
-If anything goes wrong during a build, please take a look at the various log files in the work directory. Of interest are:
-
- * state.log -- Overview.
- * pkg.*.log -- Build logs for a specific package, distribution and architecture.
-
-### The test script
-
-Once packages have been built, you can test them with the test script. Here is an example invocation:
-
-    ./test -p /passenger -x trusty -d output/trusty -c cache
-
- * `-p` tells it where the Passenger source code is.
- * `-x` tells it which distribution it should use for running the tests. To learn which distributions are supported, run `./test -h`.
- * `-d` tells it where to find the packages that are to be tested. This must point to a subdirectory in the output directory produced by the build script, and the packages must match the test environment as specified by `-x`. For example, if you specified `-x trusty`, and if the build script stored packages in the directory `output`, then you should pass `-d output/trusty`.
- * `-c` tells it where the cache directory is. The test script caches files into this directory so that subsequent runs will be faster.
-
-#### Vagrant notes
-
-When using Vagrant, the directory referred to by `-c` must be a native filesystem directory. That is, it may not be located inside /vagrant, because /vagrant is a remote filesystem. I typically use `-c ~/cache` when developing with Vagrant.
-
-### The publish script
-
-Once packages have been built, you can publish them to PackageCloud. The `publish` script publishes all packages inside a build script output directory. Example invocation:
-
-    ./publish -d output -c ~/.packagecloud_token -r passenger-testing publish:all
-
- * `-d` tells it where the build script output directory is.
- * `-c` refers to a file that contains the PackageCloud security token.
- * `-r` tells it the name of the PackageCloud repository. For example `passenger-5`, `passenger-testing`.
- * The last argument is the task to run. The `publish:all` publishes all packages inside the build script output directory.
-
-## Maintenance
-
-### Adding support for a new distribution
-
-There are three things you want to add support for a new distribution. In these instructions, we assume that  the new distribution is Ubuntu 15.05 "wily". Update the actual parameters accordingly.
-
- 1. Rebuild the build box so that it has the latest distribution information:
-
-        ./docker-images/setup-buildbox-docker-image
-
- 2. Add a definition for this new distribution to `internal/lib/distro_info.rb`.
-
-     * Add to either the `UBUNTU_DISTRIBUTIONS` or the `DEBIAN_DISTRIBUTIONS` constant.
-     * Add to the `DEFAULT_DISTROS` constant.
-
- 3. Run `./internal/scripts/regen_distro_info_script.sh`.
- 4. Update the package definitions in `debian_specs/`.
- 5. Build publish packages for this distribution only. You can do that by running the build script with the `-d` option.
-
-    For example:
-
-        ./build -p /passenger -w work -c cache -o output -d wily pkg:all
-
- 6. Create a test box for this new distribution.
-
-     1. Create `docker_images/setup-testbox-docker-image-ubuntu-15.10`
-     2. Create `docker_images/testbox-ubuntu-15.10/`
-     3. Edit `docker_images/Makefile` and add entries for this new testbox.
-     4. Run `./docker_images/setup-testbox-docker-image-ubuntu-15.10`
-
-    When done, test Passenger under the new testbox:
-
-        ./test -p /passenger -x wily -d output/wily -c cache
-
- 7. Commit and push all changes, then publish the new packages and the updated Docker images by running:
-
-        git add docker_images
-        git commit -a -m "Add support for Ubuntu 15.10 Wily"
-        git push
-        cd docker_images
-        make upload
-
- 8. On the Phusion CI server, pull the latest buildbox:
-
-        docker pull phusion/passenger_apt_automation_buildbox
-
-### Building Nginx packages only
-
-Sometimes you want to build Nginx packages only, without building the Phusion Passenger packages. You can do this by invoking the build script with the `pkg:nginx:all` task. For example:
-
-    ./build -p /passenger -w work -c cache -o output -d wily pkg:nginx:all
-
-After the build script finishes, you can publish these Nginx packages:
-
-    ./publish -d output -c ~/.packagecloud_token -r passenger-testing publish:all
-
-### Updating SSL certificates
-
-The Jenkins publishing script posts to some HTTPS servers. For security reasons, we pin the certificates, but these certificates expire after a while. You can update them by running:
-
-    ./internal/scripts/pin_certificates
-
-## Jenkins integration
-
-The `jenkins` directory contains scripts which are invoked from jobs in the Phusion Jenkins CI server.
-
-### Debugging a packaging test failure
-
-If a packaging test job fails, here's what you should do.
-
- 1. Checkout the Passenger source code, go to the commit for which the test failed, then cd into the packaging/debian directory.
-
-        git clone https://github.com/phusion/passenger.git
-        git reset --hard <COMMIT FOR WHICH THE TEST FAILED>
-        cd packaging/debian
-
- 2. If you're not on Linux, setup the Vagrant development environment and login to the VM:
-
-        vagrant up
-        vagrant ssh
-
- 3. Build packages for the distribution for which the test failed.
-
-        ./build -w ~/work -c ~/cache -o ~/output -p /passenger -d wily -a amd64 -j 2 -R pkg:all
-
-    Be sure to customize the value passed to `-d` based on the distribution for which the test failed.
- 4. Run the tests with the debugging console enabled:
-
-        ./test -p /passenger -x wily -d ~/output/wily -c ~/cache -D
-
-    Be sure to customize the values passed to `-x` and `-d` based on the distribution for which the test failed.
-
-If the test fails now, a shell will be opened inside the test container, in which you can do anything you want. Please note that this is a root shell, but the tests are run as the `app` user, so be sure to prefix test commands with `setuser app`. You can see in internal/test/test.sh which commands are invoked inside the container in order to run the tests.
-
-Inside the test container, you will be dropped into the directory /tmp/passenger, which is a *copy* of the Passenger source directory. The original Passenger source directory is mounted under /passenger.
-
-## Tutorial: building your own packages
-
-Are you a user who wants to build Debian packages for a Passenger version that hasn't been released yet? Maybe because you want to gain access to a bug fix that isn't part of a release yet? Then this tutorial is for you.
-
-You can follow this tutorial on any OS you want. You do not necessarily have to follow this tutorial on the OS you wish to build packages for. For example, it is possible to build packages for Ubuntu 14.04 while following this tutorial on OS X.
-
-### Prerequisites
-
-If you are following this tutorial on a Linux system, then you must [install Docker](https://www.docker.com/).
-
-If you are following this tutorial on any other OS, then you must install [Vagrant](https://www.vagrantup.com/) and [VirtualBox](https://www.virtualbox.org/).
-
-NOTE: If you are on OS X, installing boot2docker is NOT enough. You MUST use Vagrant+VirtualBox.
-
-### Step 1: Checkout out the desired source code
-
-First, clone the Passenger git repository and its submodules:
-
-    git clone git://github.com/phusion/passenger.git
-    cd passenger
-    git submodule update --init --recursive
-
-Checkout the branch you want. At the time of writing (2015 May 13), you will most likely be interested in the `stable-5.0` branch because that's the branch that is slated to become the next release version.
-
-    git checkout stable-5.0
-
-Then go to the directory `packaging/debian`:
-
-    cd packaging/debian
-
-### Step 2 (non-Linux): spin up Vagrant VM
-
-If you are on a Linux system, then you can skip to step 3.
-
-If you are not on a Linux system, then you must spin up the Vagrant VM. Type:
-
-    vagrant up
-
-Wait until the VM has booted, then run:
-
-    vagrant ssh
-
-You will now be dropped in an SSH session inside the VM. Any futher steps must be followed inside this SSH session.
-
-### Step 3: build packages
-
-Use the `./build` script to build packages. You must tell the build script which distribution and architecture it should build for. Run:
-
-    ./build -p <PATH TO PASSENGER> -w ~/work -c ~/cache -o output -a <ARCHITECTURE> -d <DISTRIBUTION> pkg:all
-
-Replace `<PATH TO PASSENGER>` with one of these:
-
- * If you are on a Linux system, it should be `../..`.
- * If you are on a non-Linux system (and using Vagrant), it should be `/passenger`.
-
-Replace `<ARCHITECTURE>` with either `i386` or `amd64`. Replace `<DISTRIBUTION>` with the codename of the distribution you want to build for. For example:
-
- * `precise` -- Ubuntu 12.04
- * `trusty` -- Ubuntu 14.04
- * `wheezy` -- Debian 7
- * `jessie` -- Debian 8
-
-You can find the codename of your distribution version on Wikipedia: [Ubuntu codenames](http://en.wikipedia.org/wiki/Debian#Release_timeline), [Debian codenames](http://en.wikipedia.org/wiki/Ubuntu_(operating_system)#Releases).
-
-Here is an example invocation for building packages for Ubuntu 14.04, x86_64:
-
-```bash
-# If you are on a Linux system:
-./build -p ../.. -w ~/work -c ~/cache -o output -a amd64 -d trusty pkg:all
-
-# If you are on a non-Linux system (and using Vagrant):
-./build -p /passenger -w ~/work -c ~/cache -o output -a amd64 -d trusty pkg:all
-```
-
-### Step 4: get packages, clean up
-
-When the build is finished, you can find the packages in the `output` directory.
-
-If you are on a non-Linux OS (and thus using Vagrant), you should know that this `output` directory is accessible from your host OS too. It is a subdirectory inside `<PASSENGER REPO>/packaging/debian`.
-
-If you are not on a Linux system, then you should spin down the Vagrant VM. Run this on your host OS, inside the `packaging/debian` subdirectory:
-
-    vagrant halt
-
-## Related projects
-
- * https://github.com/phusion/passenger_autobuilder
- * https://github.com/phusion/passenger_rpm_automation