FAQ
Does anyone know how contained the concept of NG build packs is? For
example, would it be possible for someone to publish a build pack for a
completely new language and framework with their application to an NG cloud
that had never hosted that framework before?

I am just trying to understand if there needs to be any inherent knowledge
about given frameworks or languages inherent in the DEAs or controllers
themselves or if everything can be completely contained within the
build-pack itself.

Michael

Search Discussions

  • Dr Nic Williams at May 23, 2013 at 11:01 pm
    Brian McClain made a buildpack for Haskell
    https://github.com/BrianMMcClain/heroku-buildpack-haskell without really
    knowing what he was doing (his words, not mine). So I think we're good to
    host new languages/frameworks :)


    On Thu, May 23, 2013 at 3:55 PM, Michael Surkan wrote:

    Does anyone know how contained the concept of NG build packs is? For
    example, would it be possible for someone to publish a build pack for a
    completely new language and framework with their application to an NG cloud
    that had never hosted that framework before?

    I am just trying to understand if there needs to be any inherent knowledge
    about given frameworks or languages inherent in the DEAs or controllers
    themselves or if everything can be completely contained within the
    build-pack itself.

    Michael


    --
    Dr Nic Williams
    Stark & Wayne LLC - consultancy for Cloud Foundry users
    http://drnicwilliams.com
    http://starkandwayne.com
    cell +1 (415) 860-2185
    twitter @drnic
  • Scott Frederick at May 24, 2013 at 12:04 am
    The built-in CF buildpacks are submodules in the dea
    repository: https://github.com/cloudfoundry/dea_ng/tree/master/buildpacks/vendor.
    If you are deploying your own CF, you can fork this repo and add whatever
    buildpack subdirectories you would like to make them "native" to your CF
    deployment. When an app is being staged, dea calls the "detect" script in
    each known buildpack until one of them indicates that they know how to
    handle the app (usually by detecting the existence of certain files that
    are specific to the language/runtime/framework supported by the buildpack).

    Custom buildpacks (unknown to the CF deployment) can be specified when an
    app is pushed by providing a git URL to the buildpack as shown
    here: http://docs.cloudfoundry.com/docs/using/deploying-apps/custom/index.html#deploying-with-custom-buildpacks.
    In this case, dea clones the git repo on-demand and then uses it to stage
    the app.

    So, to answer your question, there is nothing inherent in dea itself -
    everything is completely contained in either a set of known buildpacks or
    the one buildpack specified with the push.

    Scott
    On Thursday, May 23, 2013 5:55:46 PM UTC-5, Michael Surkan wrote:

    Does anyone know how contained the concept of NG build packs is? For
    example, would it be possible for someone to publish a build pack for a
    completely new language and framework with their application to an NG cloud
    that had never hosted that framework before?

    I am just trying to understand if there needs to be any inherent knowledge
    about given frameworks or languages inherent in the DEAs or controllers
    themselves or if everything can be completely contained within the
    build-pack itself.

    Michael

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupvcap-dev @
postedMay 23, '13 at 10:55p
activeMay 24, '13 at 12:04a
posts3
users3

People

Translate

site design / logo © 2017 Grokbase