Thanks for the quick feedback on this, we appreciate your responsiveness. We'll continue to follow the issue in the pivotal tracker.

We currently have two routing APIs in CF. 1. HTTP Routing API in cf-release: https://github.com/cloudfoundry-incubator/routing-api 2. TCP Routing API in

Hi Shawn, Great question, thanks for asking it. The Buildpacks team has a Tracker story in its backlog to work on Node 4: https://www.pivotaltracker.com/story/show/102941608 Generally our

I was playing around this morning using the Heroku Node.js binaries for v4 with the existing CF Node.js

Hi, Would you be interested acquiring business databases for your sales and marketing initiatives? I hope you are the right person to discuss about this in your company? If not please refer me to

Nice news! In my side, I am working on a Node Client for Cloud foundry: https://github.com/jabrena/cf-nodejs-client and a webApp to deploy in a easy way

NodeJS version 4 was released yesterday to the community. Generally speaking, what is the typical release schedule for buildpack binaries after new runtime releases are announced? More specifically,

Okay, great! Thanks, Amit

Hi expert,my env:cf 213 vsphere 5.5 After redeploy CF in a new environment,  testing spring-music as the first app. When run cf push, get below issue:------------------------------------ $ cf

Hello CF Community, Apologies for the lapse in sending timely Utilities PMC notes (see comments below). These notes are permanently available

After the fix, having override: true should not revoke the tokens. If it still does, then it's a bug and we would like to know. thanks

Awesome. option 2 is definitely the cause of the problem. Thank you very much.

Hello CF community, Apologies for the lapse in sending timely Buildpacks PMC notes (see comments below). These notes are permanently available

We introduced a feature called 'revokable tokens'. A token would automatically be revoked if a client changed it's secret. All tokens issued previously would be automatically revoked. In earlier

Hi, What could cause a valid token to become invalid on UAA restart? I've noticed this overtime, that a token (of client_credentials grant type) which has a validity of 315360000 and has been used

Hi Amit, Sorry, you right. In fact, I'm an user of the CF' Ramon installation ;) Daniel has solve my problems with the last link (JAVA_OPTS

Thanks Matthew. Very detail reply. :) It seems the all-in-one release won't come out soon.

Hi James, Yes, you have reason, I returned to test: https://nodejsssl.MY_IP.xip.io/ and I see the sreeen where Chrome advise the user about a NET::ERR_CERT_AUTHORITY_INVALID so, the node

Yes, there are some differences in the approach from that document. -Dieu

Hi Guillaume, Just to ensure that it will be addressed, could you add it as github issues on the repo? Hoping to do another pass at the remaining open issues later this week. -Dieu