Hello, According to code https://github.com/cloudfoundry-incubator/nsync/blob/01a624d23cb683f35c88c4160205c4ad880faaf0/recipebuilder/recipe_builder.go#L72-L84 , diego apps scale the number of

All buildpacks except the binary buildpack perform build at push time. Both "buildpacks" and "12-factor" came out of Heroku. That said, whether to use the Go buildpack vs binary buildpack is

Hi there, The CF Buildpacks team is considering taking on a line of work to provide more formal support for multibuildpacks. Before we start, we would be interested in learning if any community users

Buildbacks are still environmentally aware of the target build environment. They mean you don't need to worry about cross platform support. wrote:

On a lazy sunday evening experimenting with the Go and Binary buildpacks, a thought came to my head regarding cloud native patterns, and in particular 12 factors' Build, Release, Run. To me, the Go

Thank you, Eric. The query into auth_username and password, prompted me to review the manifest. Those were not correct and a typo in the cc_uploader, cc, base_url. I've made the corrections. I likely

Thanks, Tom. The errors about the 401 response code make me suspect that the nsync-bulker doesn't have the correct basic-auth credentials for the internal app-enumeration endpoint it queries on CC.

Yes, the logs are there. I grepped the logs for error. I see a lot

Hi Kara & Peter, Thanks a lot for your help. That fixed the issue. ranga.rajagopalan(a)gmail.com> wrote: -- Thanks, Ranga

This feature allows developers more control of the staging and deployment of their application code, without them having to fork existing buildpacks or create their own.

This feature allows developers more control of the staging and deployment of their application code, without them having to fork existing buildpacks or create their own.

Thak you for yuor answer. I gave a look at it but the project is much bigger than what i need for. As i said to Daniel, it should be a very simple application for a minimal study case for PaaS Cloud

@Daniel Mikusa Thank you for your support. I have few more questions and hope that you can help me. If i'll use the library you linked, i'd like to have some suggestions about the task i have to

Unsubscribe

Hi Tom, App developers can currently push an app using api.domain, but that is the problem we are trying to solve. As this is currently allowed, the Gorouter will balance traffic between the Cloud

Thanks, Tom, glad you were able to use veritas to find and remove the stray apps. I'd like to know how they remained present in the first place. Do you have logs from the nsync-bulker jobs on the

It would be nice to figure out the root cause here. Does having two crashed and two apps have some significance as to why the delete failed, though appeared successful?

Thank you. Veritas is quite informative. I found 2 apps running and 2 crashed. I deleted them and all appears well.

Hi Amit, thanks for your answer. I deployed cloud foundry without using static IP’s. It is working well. As far as I understood the uaa config the entire 10.x.x.x network is allowed to access the

I have the same issue. It has to do with every release since bosh 248. However, dynamic networks with older bosh releases + cf-231/cf-231 work. This must be a bug. Ben R