Have resolved this issue, the solution is change the npm version of package.json from ~2.11.3 to ~2.15.0 . Change ``` , "engines" : { "node" : "~0.12.7", "npm" : "~2.11.3"

Correct. There's a couple ways you can create the target app. Push a dummy app or use the API directly (i.e. `cf curl` [1]). Once you create the target app, copy source will override whatever is in

yes, I looked at "copy-source". copy-source - Make a copy of app source code from one application to another. Unless overridden, the copy-source command will restart the application. cf copy-source

Have you looked at `cf copy-source`? You can use that to copy one app to another. You could then change service bindings, environment variables and scale the copy of the app separately. I believe

Hello, all As we know, right now if we want to create an APP, we need push it to CF, which will cause us some time. It needs to download buildpack, upload APP bits etc, it may takes several

LGTM, but i'm using private docker registry, same docker image download from docker hub +-----------------+-----------+-------------+ | Name | Versions | Commit Hash

Hello, all I am trying on to push APP using docker image. From an existed thead, As Eric said we can use "cf push diego-docker-app -o cloudfoundry/diego-docker-app" But I got errors when running it,

Hi, all, Quick reminder of the CAB call next Wednesday, May 11th @ 8a PDT. All info in

Hi Dies, IMO the healthcheck of the app should be determined independently of whether a developer wants their app routable. My understanding of the implications for you proposal are that a

Hi Dies, I considered this a bit more after we chatted yesterday and I don't think we should try to create parity between DEAs and Diego in this case. My personal opinion is that behavior should be

The CF CLI team just cut 6.17.1. Binaries and link to release notes are available at: https://github.com/cloudfoundry/cli#downloads Note that we've been working with the Docs team to publish

The Java Buildpack creates a very complex command to start applications (since it needs to manage the JVM’s memory space within the container’s memory space). Therefore, it detects standard

Can you have a try with the attached jettty.zip.txt in previous reply to see if you reproduce it? It's used to simulate my APP, you can just download it and change to jetty.zip and unzip it. There is

Ok thanks for clarifying. It sounds like your java app is a WAR, not a JAR, correct? Or, perhaps it's a jar, but it's a non-executable jar - it cannot be run with `java -jar my-web-app.jar` If you

Hello cf-dev, Loggregator has been working on some improvements to the NOAA library. The recommended way to create a NOAA consumer is now consumer.New(...) under the consumer package instead of the

Hi all, We'd like to let you know that in the next week we'll be scheduling work to update the default version of Ruby in the Ruby Buildpack from 2.2.x to 2.3.x. This change only affects application

wrote: The time stamp on the request and response are exactly 60 seconds apart. Do you have any timeouts that are set to 60 seconds? Perhaps on your load balancer? Dan

Hello, Hope you are doing well. I wanted to bring to your attention the latest SNS Research report in which you might be interested, " The Wearable Technology Ecosystem: 2016 - 2030 - Opportunities,

So to be precise, my APP is a jetty based application, it includes jetty jars and related jetty configuration files. When this application is deployed on ubuntu (Non-CF) environment, we can get expect

Hi, We are trying to push an buildpack using cf creat-buildpack command and below are the CF_TRACE logs REQUEST: [2016-05-03T06:20:46Z] PUT /v2/buildpacks/9899f3d5-8eab-454e-accb-fcb6d139d69f/bits