David Zülke

How did you install Composer, @jonahgeorge? Is there a local `composer.phar`? Please run this and report what it returns: ``` file $(which composer) ``` Also, what does `composer config vendor-dir`...

Also, do you have a "php" executable, or is it "php5" or "php5-cli"?

What happens if you run `composer config vendor-dir 2> /dev/null | tail -n 1`, and what happens if you run `echo $(composer config vendor-dir 2> /dev/null | tail -n 1)`?...

Ah, this has to do with the alias we make that uses a local composer.phar Please help me by running the following and reporting: ``` $ which ./composer.phar composer $...

Wow, even phar is compiled as shared on Ubuntu? :(

The reason we do `php -n` (which prevents loading of INIs, so it also won't load `conf.d/` configs that enable extensions) is that we don't want new relic to start...

Oh yeah sure, that'll work, otherwise dynos would not boot on Heroku ;) I can't think of a quick and clean workaround from my side right now...

That works for you @theobat, but if there is no `phar.so` because it's built into core then that'd produce an error... :/

Very interesting. I wonder how feasible it would be for the buildpack to do that out of the box. My biggest worry is changes to the Debian or Ubuntu config...

Yeah, that's the recommended way for the moment. [Heroku Exec](https://devcenter.heroku.com/articles/exec) currently only has the ability to forward local ports to a dyno, not the inverse, which would be needed for...