anchor.diff:  
     This log is more detailed than the stdout output, however it is still terse.
   
  -  0. Set the `BP_DEBUG` environment variable to `true` for more verbose logging. This instructs the build pack to set it's log level to DEBUG and it'll write to stdout. Follow [Environment Variables documentation] to set `BP_DEBUG`.
  +  0. Set the `BP_DEBUG` environment variable to `true` for more verbose logging. This instructs the buildpack to set its log level to DEBUG and it writes to stdout. Follow [Environment Variables documentation] to set `BP_DEBUG`.
   
   [Environment Variables documentation]:../../devguide/deploy-apps/manifest.html#env-block
   [application configuration files]:./gsg-php-config.html
   [include_path]:http://us1.php.net/manual/en/ini.core.php#ini.include-path
   [extensions]:https://github.com/cloudfoundry/php-buildpack/blob/master/docs/development.md#extensions
  -[provide your own Apache or Nginx
  -configurations]:./gsg-php-config.html#engine-conigurations
  +[provide your own Apache or Nginx configurations]:./gsg-php-config.html#engine-configurations
   [configuration option]:./gsg-php-config.html
  
positive.code: cf push my-php-app -m 128M
  ```
  
  Change *my-php-app* to some unique name, otherwise you'll get an error and the push will fail.
  
  The example above will create and push a test application, "my-php-app", to Cloud Foundry.
  
  Here's a breakdown of what happens when you run the example above.
  
    - On your workstation...
      - It'll create a new directory and one PHP file, which calls `phpinfo()`
      - Run `cf` to push your application. This will create a new application with a memory limit of 128M (more than enough here) and upload our test file.
    - On Cloud Foundry...
      - The buildpack detects that your app is a php app
      - The buildpack is executed.
        - Application files are copied to the `htdocs` folder.
      - Apache HTTPD & PHP 5.4 are downloaded, configured with the buildpack defaults and run.
      - Your application is accessible at the default route. Use ```cf app
      my-php-app``` to view the url of your new app.
  
  ## <a id="caveats"></a>Caveats ##
  
  The PHP buildpack doesn't work with custom commands (the `-c` argument to `cf push` or a `command:` key in an application manifest).
  
  As an alternative, the `ADDITIONAL_PREPROCESS_CMDS` [configuration option] specifies commands that run prior to your app. Use this option to specify migration scripts etc.
  Use the `APP_START_CMD` configuration option to specify an alternate PHP script to run to start your app.
  
  ## <a id="folder-structure"></a>Folder Structure ##
  
  The easiest way to use the buildpack is to put your assets and PHP files into a directory and push it to <%=vars.product_short%>. This way, the build pack will take your files and automatically move them into the `WEBDIR` (defaults to `htdocs`) folder, which is the directory where your chosen web server looks for the files.
  
  ### URL Rewriting
  
  If you select Apache as your webserver, you can include `.htaccess` files with your application.
  
  Alternatively, you can [provide your own Apache or Nginx configurations].
  
  ### Preventing Access To PHP Files
  
  The buildpack will put all of your files into a publicly accessible directory.  In some cases, you might want to have PHP files that are not publicly accessible but are on the [include_path].  To do that, you simply create a `lib` directory in your project folder and place your protected files there.
  
  Example:
  
  ```bash
  $ ls -lRh
  
negative.code: -rw-r--r--  1 daniel  staff     0B Feb 27 21:48 controller.php
  ```
  
  Given this setup, it is possible to have both a public `lib` directory and a protected `lib` directory. The following example demonstrates this setup:
  
  Example:
  
  