Hi All, This proposal[1] suggests a UX for user-specified and buildpack-specified application sidecar processes in CFAR. Each instance of a standalone application process could have any number of asso

The buildpack cache in CF is always per-app and foundation-wide. It can only be erased by deleting the app or dropping all cache artifacts on the platform. The system buildpacks are cached on the cell

The system buildpacks are cached on the cell and bind mounted read-only into each staging container. Buildpack URLs (to a git repo or a zip file) are downloaded every time staging occurs.

Hi Stephan, The buildpack cache (aka "app cache," or "build artifacts cache") is a per-app cache that is stored as a tarball in the blob store and recovered when an existing app is restaged (regardles

Hi All, If you use the PHP buildpack in Cloud Foundry, please see below. NOTICE: Multiple upstream vulnerabilities have been discovered in all supported PHP versions in the PHP buildpack. MS-ISAC repo

Hi Guillaume, Apologies for the google doc permissions issue -- should be fixed now :) We don't have a public tracker or design docs yet, but we plan to have both soon. -Stephen

PCF Dev is already often (mistakenly) referred to as CF Dev, as `cf dev [command]` is the CLI invocation. We figured that calling this product CF Dev would give both products consistent names that mak

Hi All, Pivotal is proposing CF Dev for inclusion in the Extensions PMC as a new incubating project. CF Dev is a deployment of BOSH and cf-deployment that runs locally in Garden containers. It uses na

Answered here: https://github.com/pivotal-cf/pcfdev/issues/277#issuecomment-355694374

Hey Mike, I've chatted with other CF PMs about the possibility of opening up the namespaces functionality that we're adding for Envoy to allow the app or buildpacks to specify sidecars via Procfile, /

Hi All, The consensus (81.3%) seems to be that we should move to 18.04 for cflinuxfs3. We received some excellent questions and suggestions via email and via the form submit. Here are our thoughts: 1.

Having trouble viewing or submitting this form?FILL OUT IN GOOGLE FORMS I've invited you to fill out a form:Ubuntu version for next app rootfs Hi All, Ubuntu Trusty, which is used as the base OS-layer

The first release of the Ruby buildpack after December 6, 2017 will not include any versions of (MRI) Ruby starting with 2.1.x version numbers. Upstream support for Ruby 2.1 ended on 2017-04-01[1]. Th

The first release of the Node.js buildpack after December 6, 2017 will not include any versions of Nodejs with 7.x.x version numbers. These versions of Node.js are not covered by LTS, and as such they

Hi Peter, Could you apply the relaxed rules to each space (redundant with the platform-wide rule), and then remove the permissive platform-wide rule after? I think that would prevent your users from e

Hi Peter, Apologies for the delay. I was at CF Summit EU last week. First, thanks for following up with me here! While I believe that most of your concerns are addressed by the platform, I truly appre

Hi Peter, Many of your criticisms about buildpack dependencies stem from using online (uncached) buildpacks with apps that aren't vendored. Most enterprise CF users use offline (cached) buildpacks, an

Hi All, I am proposing CF Local for inclusion in the Extensions PMC as a new incubating project. CF Local is a CF CLI plugin that acts as a translation layer between CF apps and a local (or remote) Do

Hi Raghuvamsi, It may be worth opening an issue about this on the Java buildpack Github issue tracker[1]. [1] https://github.com/cloudfoundry/java-buildpack/issues Thanks, Stephen Raghuvamsi.Uthpala(a

Hi Joel, The stack, not the stemcell, provides the underlying base OS for an application container. The list of packages available in the default stack (cflinuxfs2) is available here: https://github.c