Yes, Gemfile and Gemfile.lock files are present at the top level. I can get "cf logs" output for other apps I pushed. So I think the reason that I don't see anything from "cf logs --recent" is that

Here is the output of "cf buildpacks": cf buildpacks Getting buildpacks... buildpack position enabled locked filename staticfile_buildpack 1 true false

Hello, all When pushing an application to CF, we need to define its disk/memory limitation. The memory limitation is just the possible maximum value will be needed in this application, but in most

Are your Gemfile and Gemfile.lock files literally named Gemfile and Gemfile.lock, and both checked present at the top level of the directory you're pushing from, on the machine you're pushing

This has been completed in Stacks 1.42.0 [1] [1] - https://github.com/cloudfoundry/stacks/releases/tag/1.42.0

Ning, What is the output of `cf buildpacks`? JT

Hi everybody, few days ago i've deployed Cloud Foundry locally using BOSH-Lite, and seems that all VMS deployed run without any problem. Here's a screen with the VMS and

Does NATS also need to come up before any of the other components?

Hi, Does anyone know how to debug "BuildpackCompileFailed" issue? When I push a ruby app: ======================== ... Done uploadingOK Starting app happy in org funorg / space development as

Final reminder to all. Please note that we will be implementing new approach to CAN call based on survey results which we will review briefly... Also, if you are a PM, please still update your status

follow the steps in here https://github.com/cloudfoundry/bosh-lite/blob/master/bin/provision_cf for a working bosh-lite. key is to start with a virtualbox image. the fusion/workstation are not up to

Hey Wayne, What command did you run to generate your manifest? Amit

Filip, I am running with the latest CF v231. Initially, I ran it with older stemcell and got: `api_z1/0' is not running after update After running with the latest stemcell, I got a successful

Error performing request: Get https://login.bosh-lite.com/login: stopped after 1 redirect that's the error right there. it's a redirect loop what version of CF is this? upgrade to the latest.

Hi Wayne, I am not seeing any errors in above. To capture UAA errors, It is better to open 2 terminals in one terminal you can do tail -f uaa.log and in another terminal try to do cf login -a

Zach, After using the latest stemcell, I got a successful deployment. But after that, cf login fails: vagrant(a)agent-id-bosh-0:~$ cf login -a api.bosh-lite.com -u admin -p admin API endpoint:

wicked cool! -- Cornelia Davis (805) 452 8941

Hi All, The oauth client with client ID *cf* is meant to be used by the CF CLI for communicating with the UAA using password grant type. There are default values for this client

Upcoming support for TCP routing (not just HTTP routing) will allow you to run a container that serves HTTPS traffic. Currently the wso2 product ships with an untrusted self-signed cert. How do you

You need some static IPs, because some components don't use service discovery, so clients need to be configured up front to know those components' IPs. For example, the route-registrar jobs talk to