I created the docker image, and you can find it "meteorping2/hello". You can push the image as an APP like "cf push stanley -o meteorping2/hello" When the APP is ready, you can access the servlet

And the crowd goes wild. Great news. Looking forward to UDP support in the future for more IoT protocols. *Sam* Ramji | sramji(a)cloudfoundry.org | +1-510-913-6495

Hi Danny, We (Japan Cloud Foundry Group) tried to deploy six applications with ddollar's heroku-buildpack-multi ( https://github.com/ddollar/heroku-buildpack-multi (deprecated now)). Here are our

Well done y'all! Huge milestone for CF and the routing team! Onsi

Great work, everyone!

Great work finishing the end to end integration with the CLI etc!!

Wow, this is great news! Congratulations, team! Chris Sterling chris.sterling(a)gmail.com twitter: @csterwa linkedin: http://www.linkedin.com/in/chrissterling

On behalf of the CF Routing team I invite you to bring your non-http workloads to Cloud Foundry. By deploying the Routing Release [1] alongside Cloud Foundry and the Diego runtime backend, operators

The CF CLI team just cut 6.18.0. Binaries and link to release notes are available at: https://github.com/cloudfoundry/cli#downloads This is likely our last CLI release this month as our velocity

Thanks for the heads up Jim, I use wire (https://github.com/square/wire) for a number of my projects. Unfortunately, it appears the map<string, string> syntax is too new for wire. Looks like I have

Hi cf-dev, In support of the epic to add tagging to CF metrics <https://www.pivotaltracker.com/epic/show/2362529>, we recently added a map to the

In order to debug this, could you provide a sample Dockerfile for an app that demonstrates this behavior, and can you push that sample app to dockerhub? Also, if you're overriding anything like the

I may not have anything that qualifies as compelling. But, here are some of the reasons I've got: * If skipping Xenial that give at the most 1 year to transition from trusty to a 2018.04 based

Thanks for doing that research Eric. So, it appears to be some requirement for Heroku compatibility. So, I guess I have 2 issues I'd like to dig further on that might help other from repeating the

cap(a)hqcquhb1smb:~$ /home/vcap/app/.java-buildpack/open_jdk_jre/bin/jcmd 37 VM.native_memory summary 37: Native Memory Tracking: Total: reserved=2128154KB, committed=836614KB - Java

Try running `jcmd <pid> VM.native_memory summary` to get a full summary of the memory being used by the JVM. Looks like this. ``` $ jcmd 72082 VM.native_memory summary 72082: Native Memory

Hi, We had found that it was due to a mistake in rabbitmq deployment manifest. The administrator user names are not consistent between server and broker. Thank everyone who helped to take a look at

Final reminder. CAB call this Wednesday @ 8a PDT. Best, dr.max ibm cloud labs sillicon valley, ca Sent from my iPhone

I have written up a feature narrative about making admin buildpacks available to meta-buildpacks like the heroku-buildpack-multi, which delegates staging to other buildpacks. The narrative also

Hello, I am running a Java application in Cloud Foundry V3. The manifest indicates 2000Mb of memory. The Java memory parameters (obtained via jcmd) are as follow: -XX:CICompilerCount=3