Nice work everyone!

Since we started the CAB calls in late 2013 the size of Cloud Foundry community, the number of engineering teams, and the number of code bases (both core & community) has grown. There was a time when

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

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 comma

I'm trying out the new "cf ssh"/Diego with a new Rails app. I'm unsure how to make the rails app's install scripts run; and the container seems to have an old/wrong Ruby in its environment. For exampl

Ok, discovered that private brokers automatically show up in marketplace and "just work"; no need for "cf enable-service-access" /closed :) wrote:

I was experimenting with private service brokers today using v225 (via PivotalWS) and was successfully able to register a service broker via the API/cf curl, but cannot figure out how to enable access

I am glad for future simpler networking for bosh-lite manifests; I just know we have lots of infrastructure-warden.yml spiff templates in lots of bosh releases. Also, will bosh-lite stemcells keep *wa

I know versioning is somewhat a lost cause for bosh-lite. I guess my actual question is: will old manifests still work for new bosh-lite? I assume so as you said "you will not notice any difference" w

Perhaps worthy of a major version bump? wrote: