Hi there! We wanted to let you know of a significant feature addition to the PHP buildpack. Thanks to Daniel Mikusa and the Buildpacks team the PHP Buildpack now has support for persistent sessions

hello, I tried with latest cf/diego release. I still can reproduce the issue. I am using all things provided by CF without any customization. I just push my servlet APP and access it from command

Hi, Mod_security [1] is a flexible opensource web application firewall, which runs configureable rules to detect and possible filter malicious incoming HTTP requests received (XSS, SQL injection

If possible add more logging or increase logging levels. Not sure what language / runtime you're using, but you might be able to add an exit hook or some code that is guaranteed to run before your

No, I didn't see error or related messages in the logs prior to the application existing. I also executed the command "bosh logs cell_z1 0" to get the log of cell_z1 0, but didn't find any useful

This isn't really a problem with the build pack. It's a problem with compiling one of the native modules that you are using ` dtrace-provider(a)0.2.8`. Not sure why that's failing. There's some

It is the exit status of your application. In other words, your app exited and returned this number. http://tldp.org/LDP/abs/html/exit-status.html It may be an application specific number or it

Sorry, the version of CF and Diego in previous mail is incorrect, CF release version is v233, Diego version is V 0.1460.0

Hello, I deployed an application to Diego, found this application often got restarted, there is no error message in the log, just found the following message, what does the status code 255

This issue has been resolved in https://github.com/cloudfoundry-incubator/cf-routing-release/issues/28, the root cause of this issue is that cf cli caches RoutingEndpoint in ~/cf/config.json so do a

Hello, I have a nodejs application, it can be deployed and started in CF if the version nodejs buildpack <v 1.5.9, the version of node and npm in package.json of my nodejs application is as

Hi Am 28.04.2016 um 23:08 schrieb Mike Youngstrom: +1 for that proposal. A 404 also causes issues when crawler remove pages from their index. A 503 has less side effects. I would also prefer a 503

Hi all, Giving everyone heads up about changes in manifest property for 'haproxy' job. We are merging what are now two separate properties for configuration of the router static ips into a single

Hi Eric, forget my preceding messages. I had to add and bind the security groups. Now it seems to work. What if I have a username/password protected registry? (https, self signed certs) Where do I

Hi Stanley, We attempted to reproduce this behavior on bosh-lite and were unable to, which leads me to believe the issue might be in some middleware. Are you using the provided java buildpack or a

Yes, I haven't deployed cf-routing-release, I just deployed cf-routing-release, but meet a new issue, when I run command "cf router-groups", the following error is shown: FAILED This command requires

Hi Eric, thank you for your kind and comprehensive answer! Regarding point 1) I still have problems. Our internal Docker registry is configured with HTTP, a self signed certificate, no user and no

Hi Eric, thank you for the kind and comprehensive answer! Regarding point 1, I still have some difficulties. Our internal Docker repository is configured in HTTPS, self signed certificate, no

they fixed in the community haproxy release see https://github.com/cloudfoundry-community/cf-haproxy-boshrelease/pull/21 it would be nice to implement this as well in the haproxy in cf-release

hey all, v256 bosh version fixed a long present bug with mutation of properties between colocated releases. it was not easily noticeable since most of the time properties are not mutated as part of