It would be more useful if the multi-buildpack can reference an admin buildpack in addition to a remote git-hosted buildpack. :-) Jack wrote:

+1 Jack

Yes that should work too, but it's still nice to be able to install the gems during staging. Jack

Can someone merge this PR: [1]? It provides useful features to allow operators to set a global gem repo mirror (via environment variable group) where the default repo is slow to reach. Thanks!! Jack [

Thanks for all the replies. I think I've got what need. Jack

Hi Ronak, Thanks for answering it. The public API needs a CF user credential. It's much easier for the app/buildpack to get such info from an env variable. My scenario is that during our transition to

Hi, Is there a way for the application to know whether it's running in DEA or DIEGO? Looking at [1], there is no environment variable that can tell this. Jack [1] https://docs.cloudfoundry.org/devguid

Mike, thanks for sharing your thoughts. I agree that it's also valuable to provide the runtime information for a pushed application. For the use case of providing supported runtime by a buildpack, let

Now that most buildpacks only support a small set of runtime versions (as defined in their manifest), it makes good sense to make this information easily accessible by users. They can of course go to

What cloud are you referring to? Better ask the question in the cloud provider's forum. Jack

The "cached" packages of the buildpacks contain lots of runtime binaries, like OpenJDK, Node.js, PHP etc, built by Cloud Foundry. Has anybody gone through a review of their export control classificati

Thanks JT. Except the Java buildpack though :-) Jack

Thanks Mike. Is it true that even for the online version (aka when doing "cf push -b https://github.com/cloudfoundry/nodejs-buildpack.git"), users are now limited to use the runtime versions defined i

For the cached package of the buildpacks, I thought it would refuse to provide a runtime version that's not cached. Yesterday I was playing with the node.js buildpack and found it actually will downlo

This is a great list of languages to support. May I ask to add ar (Arabic) and iw (Hebrew) to the list? These two are considered "Group 2" languages in the company I work for. With them added, all Gro

I notice the below changes in the environment variables of DIEGO: 1. VCAP_APP_HOST & VCAP_APP_PORT are removed. 2. These fields are removed from VCAP_APPLICATION value: application_uris, started_at, s

One thing I'm wondering is how to provide enough public "ports" for users to map to. It seems the cloud provider need to provide multiple public IP to map the ports, otherwise they will soon run out o

After ssh into the vagrant VM and digging into the processes/ports, I found out that in my previous attempt I was trying to map one additional port that was already occupied by garden (7777). Because

Thanks Atul and Marco for your advice. Below is the command I used to push the docker image: * ltc create hello <docker-image> --ports 8888,8788 --http-routes hello:8888 --tcp-routes 8788:8788 --memor

I'm playing around with the tcp-routing feature in the latest Lattice release. I started two node.js applications in the pushed image (listening on two ports), one mapped to an http route and the othe