php-protobuf | PHP Protobuf - Google 's Protocol Buffers for PHP | Serialization library

To build a custom PHP buildpack, typically done to include proprietary dependencies like Oracle or SQL Server drivers you can do the following.

1. Build PHP. This is done with binary-builder. Follow the instructions here. Build as many versions of PHP as you require. This will produce tgz files that contain the binaries.

2. Host your custom binaries on a web server. This could be local or public, it depends on your needs (see step #5) below.

3. Clone the PHP Buildpack and checkout one of the stable release tags. Do not build from master as that makes it really hard to know what you're getting or recreate your build. When in doubt, pick the latest tagged release.

4. Edit the manifest.yml file. If it already has entries for the versions of PHP that you built, you can just modify the uri, sha256 hash and modules. You need to add in the additional extensions you compiled to the modules list. For example, append oci8 or pdo_oci to that list. If you're compiling a version of PHP that doesn't existing in the manifest, copy an existing entry and edit all the properties. You can also adjust the manifest to change default versions of PHP or to remove versions you don't want and slim down the buildpack.

5. At this point, you can either commit your changes, push to a fork of the PHP buildpack and set cf push -b to point to your fork, or alternatively, you can run the build pack packager and create a buildpack file. You can then take that and cf create-buildpack or cf update-buildpack in your foundation (requires admin permissions).

   If you use cf push -b then the binaries you are hosting in step #2 must be accessible from the CF foundation where you are running your application. If you create and upload a buildpack, then the binaries only need to be accessible from the VM where you run build pack packager.

Hope that helps!