|
persistence for apps?
yes, that one would hit the spot! Sent: Thursday, December 10, 2015 2:29 PM To: Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org> Subject: [cf-dev] Re:
yes, that one would hit the spot! Sent: Thursday, December 10, 2015 2:29 PM To: Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org> Subject: [cf-dev] Re:
|
By
...
· #3067
·
|
|
persistence for apps?
Danke, Johannes. We actually have an implementation that uses S3, but want to also be able to also support openstack, on-premise. Rather than re-implementing in swift, nfs would be an easier path from
Danke, Johannes. We actually have an implementation that uses S3, but want to also be able to also support openstack, on-premise. Rather than re-implementing in swift, nfs would be an easier path from
|
By
...
· #3056
·
|
|
persistence for apps?
We are looking at solutions to persist and share directory-type information among a couple of apps within our application stack. NFS comes to mind. How would one go about that? A manifest modification
We are looking at solutions to persist and share directory-type information among a couple of apps within our application stack. NFS comes to mind. How would one go about that? A manifest modification
|
By
...
· #3054
·
|
|
postgres out of disk space
thank you all! I’m indeed running v212. Deleting /var/vcap/store/shared/run.10.10.2.37.xip.io-cc-droplets/buildpack_cache did the trick. Sent: Friday, September 25, 2015 6:47 PM To: Discussions about
thank you all! I’m indeed running v212. Deleting /var/vcap/store/shared/run.10.10.2.37.xip.io-cc-droplets/buildpack_cache did the trick. Sent: Friday, September 25, 2015 6:47 PM To: Discussions about
|
By
...
· #1993
·
|
|
postgres out of disk space
ah, it’s not postgres: 90M postgres it’s actually: 94G shared/run.10.10.2.37.xip.io-cc-droplets Does it keep a copy of each artifact ever pushed? Or is this part of the event storage, controlled by th
ah, it’s not postgres: 90M postgres it’s actually: 94G shared/run.10.10.2.37.xip.io-cc-droplets Does it keep a copy of each artifact ever pushed? Or is this part of the event storage, controlled by th
|
By
...
· #1985
·
|
|
postgres out of disk space
I have a cf-aws-tiny cf-boshrelease deployment, and it's been running well for over 4 months. We have about 40 apps, with a couple of dozen of cf pushes each day. Yesterday pushing apps became spotty
I have a cf-aws-tiny cf-boshrelease deployment, and it's been running well for over 4 months. We have about 40 apps, with a couple of dozen of cf pushes each day. Yesterday pushing apps became spotty
|
By
...
· #1977
·
|
|
public proxy and access control
I recently used this terraform project to create a AWS cf install: https://github.com/cloudfoundry-community/terraform-aws-cf-install I uses the floating ipaddress of the public proxy as its default d
I recently used this terraform project to create a AWS cf install: https://github.com/cloudfoundry-community/terraform-aws-cf-install I uses the floating ipaddress of the public proxy as its default d
|
By
...
· #695
·
|
|
private vs public visibility of apps
excellent. I can create domain to the private proxy that's included cf create-shared-domain apps.<ip of private_haproxy>.xip.io and then push my app to it cf push -d apps.<ip of private_haproxy>.xip.i
excellent. I can create domain to the private proxy that's included cf create-shared-domain apps.<ip of private_haproxy>.xip.io and then push my app to it cf push -d apps.<ip of private_haproxy>.xip.i
|
By
...
· #640
·
|
|
private vs public visibility of apps
We have a cf app that need not have public visibility. It's like a service, but it's a stateless app, so making it a droplet is convenient. It only needs to be visible to the other apps. How can I hid
We have a cf app that need not have public visibility. It's like a service, but it's a stateless app, so making it a droplet is convenient. It only needs to be visible to the other apps. How can I hid
|
By
...
· #609
·
|