cphalcon | High performance , full-stack PHP framework | Model View Controller library

Since version 4.0.0 Phalcon requires the PSR extension. The extension can be downloaded and compiled from this GitHub repository. Installation instructions are available on the README file of the repository. Once the extension has been compiled and is available in your system, you will need to load it to your php.ini. You will need to add this line:

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!

You need to just use the ADD command to add files from your local to the container:

Looks like you are exposing port 5001 from local machine to port 80 on the docker instance, but then you are defining your virtual host on port 5001. So your site-default.conf it probably should read:

Notice that the error is about /var/www/html/ (some Apache default directory) and not your own /usr/src/fileserver/public

The latest docs at time of writing recommend Phalcon-3.3 and state:

PHP >= 5.5

https://docs.phalconphp.com/en/3.3/installation

You can use the incubator to load twig or mustache