This is a set of scripts that can be used to build the binary files required by the CF PHP Build Pack:

• Apache httpd 2.4.x
• Nginx 1.5.x, Nginx 1.6.x, Nginx 1.7.x,
• PHP 5.4.x, PHP 5.5.x, PHP 5.6.x
• HHVM 3.2.x (lucid only)
• a full set of extensions for both version of PHP.

The scripts are configured with variables at the top and can be used to build different versions of each project and modules for the projects. The scripts were originally designed to be run on Ubuntu 10.04, which is the current stack used by CF. It has been expanded to support Ubuntu 12.04 and Ubuntu 14.04 as well. Different OS & Version combinations are supported through different branches of the repository.

The builds are performed inside virtual machines managed by Vagrant. You can run the builds on your local machine using VirtualBox or VMware Fusion, or remotely on DigitalOcean.

1. Install Vagrant on your local machine.
2. Install VirtualBox or VMware Fusion on your local machine.
3. If using VMware Fusion, also install the Vagrant provider for it.
4. Clone this repository.
5. Change directories to your newly-cloned repository (cd cf-php-buildpack-binary-build-scripts) and run ./build/run_vagrant.sh all. This will cycle through three Ubuntu virtual machines: 10.04 Lucid, 12.04 Precise, and 14.04 Trusty. On each machine, it will build the binaries and copy them to a sub-folder of the output directory.
6. When the build is complete, the packages will all reside in the output directory on the local machine.

To see what happens on each vm, refer to the run_local.sh script below.

1. Install Vagrant on your local machine.
2. Install the Digital Ocean provider for Vagrant: vagrant plugin install vagrant-digitalocean
3. Clone this repository.
4. Change directories to your newly-cloned repository (cd cf-php-buildpack-binary-build-scripts).
5. Run VAGRANT_DEFAULT_PROVIDER=digital_ocean DO_API_TOKEN=<your-api-token> ./build/run_vagrant.sh all. This assumes the default settings will be used. For different options, see the configuration section below.
6. When the build is complete, files will be scp'd down to the local machine and placed in an OS/Version specific sub-folder of the output directory.
7. Please note that the script will halt your DO instance when it is finished. This allows you to run subsequent builds on the same instance without having to completely rebuild and re-initialize the system. When you are finished, run ./vagrant/<platform>/vm_ctl destroy to delete the instance or delete it through the DO console.

To see what happens on each vm, refer to the run_local.sh script below.

The Vagrant scripts that start your DO instances attempts to use good default options, however there are a few settings that you can change to alter the behavior. The following list documents the environment variables that you can set to change the script's behaviour.

1. Install the base OS. Currently Ubuntu 10.04, 12.04 or 14.04.
2. In a terminal in the OS, run bash <( curl -s https://raw.githubusercontent.com/dmikusa-pivotal/cf-php-buildpack-binary-build-scripts/master/build/run_local.sh ).

This will download and run the local install script, which handles everything else. See the run_local.sh script below for more details.

1. Install the base OS. Currently Ubuntu 10.04, 12.04 or 14.04.
2. Setup an SSH Server on the base OS. Add your ssh key to the .ssh/authorized_keys file on the base OS.
3. Run bash <( curl -s https://raw.githubusercontent.com/dmikusa-pivotal/cf-php-buildpack-binary-build-scripts/master/build/run_remote.sh ) [user]@<baseos-ip>.

Here's a listing of the scripts and what they do.

This is the main directory for the scripts, and contains the following scripts.

Each supported OS & Version combination has it's own branch. These are largely similar, but each combination has it's own differences. When you run the run_local.sh script, your OS and Version are determined by looking at /etc/issue and the correct branch is checked out.

The OS & Version specific branches contain the individual scripts which compile the various components. These are stored in project subdirectories with a name and major version number and contain the build script. The build script is responsible for building that individual component. Most of the time this boils down to running ./configure && make && make install, but some components are more complicated than that. Regardless, this script is responsible for building and packaging the component.

Generally you should run the run_local.sh script to build the full suite of components, but you can run the individual <component-version>/build.sh script if you want to build just a single component.

If hosting files on DropBox, this script can be used to walk the output directory (i.e. where built files are downloaded) and automatically upload files to DropBox.

This script relies on the Dropbox-Uploader to handle the work of actually uploading files to DropBox. To use the upload script, you must first run the ./dropbox/dropbox_uploader.sh script. The first time it's run, it will walk you through setting up your DropBox account to allow it to connect and upload files. This creates a config file with your DropBox API credentials and OAuth token info. It's stored in ~/.dropbox_uploader.