Great question, Dan. I'm curious to this as well - I just assumed it took some time to report back the status. -- Ed Mikuszewski *| * <http://www.pivotal.io> *|* Mobile: 646-628-2872 *| * Email:

Quick question, when I push an app to CF I get this output at the bottom after the app starts. ``` requested state: started instances: 1/1 usage: 256M x 1 instances urls:

I have further information the to 403 error. internal_error.log states: "2016/03/16 12:05:00 [error] 20579#0: *105 directory index of "/var/vcap/store/shared/" is forbidden, client: 10.10.0.104,

Hello, I am facing some problems with the cloud_connector on cf-release 231. I suspect the problem has something to do with the blobstore configuration, but I can't figure out what's wrong. I want

Hi, Fillip, here's decoded token { doesn't contain scim scope -- Regards, Yitao

Hello Rob, sure...i will post to the other thread. Thank you for your answer.

Hi Raymond, It is possible to use FUSE-based clients to connect to remote filesystems, but only if your Cloud Foundry deployment has enabled privileged containers. We are currently working on adding

Hi Austin, We are not sure which docs you are referring to - can you clarify this? Cloud Foundry is available as a bosh release at https://github.com/cloudfoundry/cf-release - this includes the

Hi Austin, We are not sure which docs you are referring to - can you clarify this? Cloud Foundry is available as a bosh release at https://github.com/cloudfoundry/cf-release - this includes the

Can a cloud foundry application make us of Network Filesystem share? If so, would this scale? Thanks, Raymond

Giovanni, A github issue was opened by others with similar issues at https://github.com/cloudfoundry/cf-release/issues/923. Could you take a look at our suggestions there and, in the interest of

Take a look at the value of $TOKEN (many online decoders out there. https://jwt.io is one) and see what scopes your token actually has. Filip

As of cf-release v232 there will be some required changes to the blobstore configuration in the cf-release manifest. The linked doc should explain what you will need to do depending on the type of

Thanks for letting us know

That's fantastic! Great to hear DNS hostname worked well for you, as supporting it is a new feature in consul-release, so it's good to hear it's working "in the wild". Best, Amit TECH MAHINDRA LIM

This turned out to be a browser cache issue. Clearing out the browser cache and it worked as before. Figured I post in case anyone else sees a similar issue after upgrading. -Rich

Hi Amit Thank you very much for your support, as I am able to successfully deploy with cf-231. We use DNS hostname for all the jobs, with dynamic IP networks. So I used cf-231 release today.. All the

Hi, guys, I wanna get the users email , so per the docs of UAA at https://github.com/cloudfoundry/uaa/blob/master/docs/UAA-APIs.rst#query-for-information-get-users, i create a client with following

Hey Stanley, Yup, that /state endpoint is for the Cell's bookkeeping (it's essentially implementing the overcommit factor of 1, aka no overcommit), but it doesn't mean physical memory has been

it looks like one of the vms is unresponsive. you can try uding bosh cck to recover. Sent from my iPhone