Missing PHP extensions while running composer

[croemmich]

I have the following config in a Laravel application:

.bp-config/options.json

{
  "WEB_SERVER": "nginx",
  "WEBDIR": "public",
  "LIBDIR": "",
  "PHP_EXTENSIONS": ["amqp", "bz2", "curl", "dba", "exif", "fileinfo", "ftp", "gd", "gettext", "gmp", "igbinary", "imagick", "imap", "intl", "ldap", "mailparse", "mbstring", "mcrypt", "memcache", "memcached", "mongo", "msgpack", "mysql", "mysqli", "openssl", "pdo", "pdo_sqlite", "pdo_mysql", "pdo_pgsql", "pgsql", "phalcon", "phpiredis", "pspell", "redis", "snmp", "soap", "sockets", "sundown", "twig", "zip", "zlib"],
  "ZEND_EXTENSIONS": ["xdebug"]
}

Obviously I don't actually need all of the extensions, but it appears they are all being loaded as I configured:
https://laravel.mybluemix.net/phpinfo.php#module_mcrypt

However, when composer attempts to run Laravel's post install scripts, the script is throwing the following error:

Mcrypt PHP extension required.
Script php artisan clear-compiled handling the post-install-cmd event returned with an error

From what I can tell, the built ini file is being copied to tmp, and should have the same configuration as php-fpm, but the error above makes me wonder if that is the case. Thoughts?

[dmikusa]

At the moment, if you're going to run a command that uses PHP and requires extensions you'll need to point PHP at the php.ini file (because everything has to be install in non-standard locations). See here which shows how the build pack runs a stand-alone PHP app.

As a note, part of adding PHP to the path will be fixing this as well.

[croemmich]

Doh. This is why I shouldn't work on things late at night.

I was able to get it working by setting the PHPRC environment variable. I have updated my pull request for issue #26.

Thanks!

[dmikusa]

No worries. For what it's worth, I think that's the path the build pack will take. It seems to make the most sense.