anchor.diff:  
   The buildpack automatically configures HTTPD, Nginx. and PHP for your application.  This section explains how to modify the configuration.
   
  -The `.bp-config` directory in your application can contain configuration overrides for these components. Name the directories `httpd`, `nginx`, and `php`.
  +The `.bp-config` directory in your application can contain configuration overrides for these components. Name the directories `httpd`, `nginx`, and `php` (although we suggest you use [php.ini.d](#php_ini_d) or [fpm.d](#fpm_d)).
  +
  +<p class='note'><strong>NOTE</strong>: If you override the php.ini or php-fpm.ini files many other forms of configuration will not work.</p>
   
   For example:
   ```
  
positive.code: php-fpm | NOTICE: PHP message: PHP Fatal error:  Unable to start example Loader module in Unknown on line 0
  ```
  
  Try moving the `example` extension from `PHP_EXTENSIONS` to `ZEND_EXTENSIONS`, then re-pushing your application.
  
  If you see this error:
  
  
negative.code: Include conf/extra/httpd-my-special-config.conf # This line includes your additional file.
  ```
  
  
  #### <a id="php_ini_d"></a> .bp-config/php/php.ini.d/
  
  The buildpack will add any `.bp-config/php/php.ini.d/<file>.ini` files it finds in the application to the PHP configuration. This can be used to change any value which is acceptable to php.ini [(list of directives)](http://php.net/manual/en/ini.list.php).
  
  For example adding a file `.bp-config/php/php.ini.d/something.ini` to your app, with contents
  
  ```
  default_charset="UTF-8"
  default_mimetype="text/xhtml"
  ```
  
  would override both the default charset and mimetype.
  
  ##### Precedence
  
  In order of highest precedence, php config values come from.
  
  * php scripts using ini_set() to manually override config files
  * user.ini files (for local values)
  * .bp-config/php/php.ini.d overrides master value but, local value is still the one from user.ini
  
  #### <a id="fpm_d"></a> .bp-config/php/fpm.d/
  
  The buildpack will add any `.bp-config/php/fpm.d` files it finds in the application to the PHP-FPM configuration. This can bes used to change any value which is acceptable to `php-fpm.ini` [(list of directives)](http://php.net/manual/en/install.fpm.configuration.php)
  
  ### <a id="php-extensions"></a> PHP Extensions
  
  The buildpack will add any `.bp-config/php/php.ini.d/<file>.ini` files it finds in the application to the PHP configuration. This can be used to enable PHP or ZEND extensions. For example,
  
  
  ```
  extension=redis.so
  extension=gd.so
  zend_extension=opcache.so
  ``` 
  
  If an extension is already present and enabled in the compiled php, for example `intl`, you do not need to explicitly enable it to use that extension.
  
  #### PHP\_EXTENSIONS vs. ZEND\_EXTENSIONS
  
  PHP has two kinds of extensions, "PHP extensions" and "Zend extensions". These [hook into the PHP executable in different ways](https://wiki.php.net/internals/extensions).
  
  For this reason, they are specified differently in ini files. Your app will fail if a Zend Extension is specified as a PHP Extension, or vice versa.
  
  If you see this error:
  
  