ruby+php sequence in .buildpacks works; but php+ruby fails?

[aceare]

If .buildpacks contains:
https://github.com/heroku/heroku-buildpack-ruby.git
https://github.com/heroku/heroku-buildpack-php.git
then, git push heroku master succeeds.

However, .buildpacks contains:
https://github.com/heroku/heroku-buildpack-php.git
https://github.com/heroku/heroku-buildpack-ruby.git
then, "git push heroku master" fails with error "Push rejected, failed to compile Multipack app". Looks like "framework=$($dir/bin/detect $1)" fails for ruby.

Any clues/suggestions?

[leorochael]

Looks like, @michaelmior has the right of it.

Try the patch in pull request #12, and add your opinion to it.

Basically, the set -e instruction to the shell means that any command failures, even if intented to be captured in subshell commands, like $(...), causes the whole script to fail.

[aceare]

Thanks for the suggestion. But #12 patch didn't help to resolve this issue. Here are the details:
First item in .buildpacks, heroku-buildpack-php.git is compiled successfully. But then for heroku-buildpack-ruby.git, "$dir/bin/detect $1" retuns with $exit_code 1. So, "$dir/bin/compile $1 $2" is not executed and thus Ruby/Rails is not getting installed.
Also tried to forcefully execute "compile" for Ruby/Rails, but that also didn't help.

[j15e]

The real issue here is that the default heroku PHP buildpack is moving everything to a new folder www so that is breaking the previous buildpack installation. If you place it before the ruby buildpack, it still move the Gemfile to www so the ruby buildpack detect phase is failling.

There is certainly good reasons to move stuff to www, but I don't like it and it makes other buildpack incompatible.

I made a quick fork to fix this issue, I hope it may resolve your issues as did for me in the same PHP + Ruby (for sass) setup :

https://github.com/hooktstudios/heroku-buildpack-php-multi

P.S. I think this issue should be closed as it is not caused by heroku-buildpack-multi.

[aceare]

Ooh yes, that explains it. Thanks 👍