Another common use case for me is that an application is polyglot in some
toggle quoted message
Show quoted text
way. For example, you have a blog you'd like to deploy that uses a static
site generator written in (say) Go. You would have the Go buildpack run to
bootstrap and generate the resulting files in some output directory, and
then the staticfile buildpack runs and serves the files from the output
On Tue, Apr 12, 2016 at 12:45 PM John Feminella <jxf(a)pivotal.io> wrote:
Multibuildpack is absolutely useful and I'm excited for this proposal.
I encounter a lot of use cases for this. The most common is that an
application wants to pull in private dependencies during a future
dependency-resolution step of a later buildpack, but the dependency
resolver needs to be primed in some specific way. If you wait until
buildpack time it's too late.
On Heroku, for example, this is accomplished by having something like the
netrc buildpack (
https://github.com/timshadel/heroku-buildpack-github-netrc), adding a
GITHUB_TOKEN environment variable, and then running your "real" buildpack.
The netrc BP runs first, allowing Bundler to see the private dependencies.
On Tue, Apr 12, 2016 at 12:36 PM Jack Cai <greensight(a)gmail.com> wrote:
It would be more useful if the multi-buildpack can reference an admin
buildpack in addition to a remote git-hosted buildpack. :-)
On Tue, Apr 12, 2016 at 6:38 AM, David Illsley <davidillsley(a)gmail.com>
In the past we've used the multi-buildpack to be able to use ruby sass
to compile SCSS for non-ruby projects (node and Java). In that case we used
the multi-buildpack and a .buildpacks file which worked reasonably well
(and was very clear).
On Mon, Apr 11, 2016 at 1:15 AM, Danny Rosen <drosen(a)pivotal.io> wrote:
The CF Buildpacks team is considering taking on a line of work to
provide more formal support for multibuildpacks. Before we start, we would
be interested in learning if any community users have compelling use cases
they could share with us.
For more information on multibuildpacks, see Heroku's documentation