i just created a new cloudfoundry deployment for testing purposes and i can push a application but the the following error Warning: error tailing logs Error dialing loggregator server: unexpected

I deployed a java application app1 to diego, then I ssh to the application container using command " cf ssh app1", when I execute command "ruby -v" in this application container, the value is shown as

We came across a certain situation when deploy abacus where we initially deployed it with a SLACK window of 45D so we could resubmit previous data to it again. We want to change the SLACK to a smaller

Hi All, Its 2016 and we have finally decided to make token persistence & revocation a reality in UAA !! Over the past year, I have had multiple conversations with foundation members and customers

Hi All, Good news: stemcell 3192 fixes this issue as well as including patches for the aforementioned CVEs. I'd recommend everyone update their deployments to use this

Search the archives. This has come up on this list at least once before. Try searching for "download buildpack". Dan wrote:

Hi, I am following up on my previous email (mentioned below) Please let me know the best time for you to get on a call and accordingly we can take the discussion further. Look forward to your

HI, All buildpacks are opensource, https://github.com/cloudfoundry/python-buildpack xxx is the github tag. Thanks wrote:

Hi. I would like to get buildpack code for a buildpack which is currently in "cf buildpacks" list. I tried: - list of buildpacks -> cf curl /v2/buildpacks - details about my buildpack -> cf curl

OpsMetrics is a pivotal product for PCF. I don't think It's intend to be use outside of PCF. Of course you can use new relic but it depends on which runtime, seems you are using Java Buildpack the

My admin ui is running as bosh vm and have opened a route in haproxy. I am trying to access https://myappexample.com/adminui from browser. I am getting** page not found error** in browser. I tried

If you are trying to get the actual JWT token of your current UAA instance targeted by UAAC, you can try: $uaac context corentin.dupont(a)create-net.org> wrote: --

Hi, all, Based on recent low attendance and engagement, it's time we perhaps tweak the call. After briefly discussing with Colin, Chip, Sam, Chris, Stormy, and a few others, here is a short

You can obtain the "Authorization: bearer" token using the cf cli. cf login cf oauth-token

Still struggling... I have already an account with CF, so I tried: $ uaac token client get Client ID: admin Client secret: ************ Successfully fetched token via client credentials

Hi Darren, We had put it on hold when we thought someone was going to open source a solution that matched our proposal in functionality. Apologies to everyone who responded at the time and have been

Hi, Nanduni, The diego-release README does recommend deploying the runtime-passed branch of cf-release alongside the master branch of diego-release. Although the two are typically compatible,

Hi all, Sorry for troubling again. I generated the CF manifests successfully. But I am getting errors while generating the Diego manifests. I gives me the following

Hi Daniel, I got this issue solved. The cause had been setting the path incorrectly. Thank you very much. Looking forward for more help in upcoming issues. Best Regards, Nanduni

Since the code in those executables is meant to be ruby, you'll need the appropriate shebang line, like