peterkeen / heroku-buildpack-vendorbinaries Goto Github PK

The readme mentions the legacy heroku-buildpack-multi buildpack, which was previously required in order to use multiple buildpacks.

However Heroku now supports doing this natively, see:
https://devcenter.heroku.com/articles/using-multiple-buildpacks-for-an-app

Pull down vendored binaries and stuff them in the cache, instead of pulling them down every time. This will work best with binaries with a unique hash in their filename.

-----> Fetching custom git buildpack... done
-----> Multipack app detected
=====> Downloading Buildpack: https://github.com/ashu-daffodil/heroku-buildpack-vendorbinaries.git
=====> Detected Framework: VendorBinaries
-----> Found a .vendor_urls file
Vendoring https://github.com/ashu-daffodil/HerokuTest1/blob/master/wkhtmltox.tar.gz

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Exiting with failure status due to previous errors

Hello!

First, thanks for putting this together! It's very helpful to have this and not have to wrangle my own buildpack.

I just wanted to point out that the README lists that the URLs should go in a file named .vendor_binaries, whereas the code is looking at .vendor_urls.

Hi,

You put wrong link in your blog post.

Wrong:

https://github.com/heroku/heroku-buildpack-helo

Correct:

https://github.com/heroku/heroku-buildpack-hello