It will totally depend on the app/buildpack. For example, the static file buildpack and PHP buildpack just launch Nginx and then host the application inside it. As soon as the web server is up it

My understanding is that because the app droplet itself typically includes the webserver (as opposed to Windows where the server is run by the host), it would be rare for the web server to be

Thank you. In that case, I am running the 60 days trial version of Pivotal.io. So I have no administrator as I suppose. Can I set my account to get admin privileges or can I set me as an admin?

I understand what you're trying to avoid, I just think that is actually the normal case for the port healthchecks. Nothing on the Linux or Docker side ever touches the app so it's entirely possible

Thanks! The documentation seems to imply that this can only be done if you have a spring application. Is this true? "Cloud Foundry provides extensive support for connecting a Spring application to

Thanks! The documentation seems to imply that this can only be done if you have a spring application. Is this true? "Cloud Foundry provides extensive support for connecting a Spring application to

Hi Kinjal, Sorry for the delayed response. Are you still hitting compilation timeouts? I cannot access the gist you linked to with the debug output of your failed BOSH task. Amit

Hi Kinjal, You are mixing the minimal deployment instructions with the "standard" deployment instructions. When using the "standard" instructions (where you create a stub), both cf1 and cf2 networks

Hi Aaron, You can track the progress of the story for DiegoWindows here on the public tracker [1]. As it stands, we don't yet have a solution that we could do within the DiegoWindows codebase that

Based on this discussion, where are we on the priority of switching the current "port" check for the Windows lifecycle back to actually be a port check? I get the impression that the changes to

Quick reminder of the CAB call this Wednesday, February 10th @ 8a PDT. All info in

wrote: The administrator for the CF installation you're targeting has disabled docker support. Since you're not an administrator, you cannot turn on this feature. Talk to your administrator and

I want to deploy a Docker image in cloud Foundry. So I proceeded as below. I am using cf version 6.14.1+dc6adf6-2015-12-22. $ cf push myimage -o cloudfoundry/lattice-app --no-start Creating app

Somehow I didn't get Eric's reply so my reply above probably seems odd. Sorry Eric! wrote:

Hi, Dr Nic, This issue also came up in the #buildpacks channel in the CF Slack the other day. Until we solve this permanently, a cleaner and more complete workaround seems to be to run

Eventually I figured out a (nasty) workaround to manually load the environment: https://blog.starkandwayne.com/2016/02/07/run-one-off-tasks-and-database-migrations/ You need to run the following

+ cf-bosh Looking for community feedback on bumping consul to 0.6.0 in the consul-release maintained by the core CF team: https://github.com/cloudfoundry-incubator/consul-release. Please see

Hello, all I am running into this issue again. With change cell VM to c3.xlarge(7.5G memory), I have successfully pushed 2 applications to my cf/diego environment. app1 asked 2g memory and app2

Just as a reference you could look at some of the connection tests that Monit allows: https://mmonit.com/monit/documentation/monit.html#CONNECTION-TESTING Obviously there are quite a few there so it

Dear CF Community, CF has long had a notion of health-checking app instances as they start up to determine whether they're in a functional state, on top of the process simply having started. On the