Re: private vs public visibility of apps

James Bayer

here is a write-up about that from stark and wayne [1]

the upcoming "route service" capability [2] will also support the ability
to have pluggable authorization


On Mon, Jun 29, 2015 at 2:23 PM, Josh Ghiloni <jghiloni(a)> wrote:

I'm sure there's an easier way to do it, but you could always map a DNS
domain to your space that does not have public visibility, then deploy your
apps to that domain.

*Josh *Ghiloni

Senior Consultant

303.932.2202 o | 303.590.5427 m | 303.565.2794 f

jghiloni(a) <rgarrett(a)>

*ECS Team *

*Technology Solutions Delivered* <> <>

*From:* cf-dev-bounces(a) <
cf-dev-bounces(a)> on behalf of Matthias Ender <
*Sent:* Monday, June 29, 2015 2:46 PM
*To:* cf-dev(a)
*Subject:* [cf-dev] private vs public visibility of apps

We have a cf app that need not have public visibility.

It’s like a service, but it’s a stateless app, so making it a droplet is

It only needs to be visible to the other apps.

How can I hide the endpoint from the outside world?

I can remove the route, but then the other apps can’t see it either.

How does one handle that in cf?



cf-dev mailing list

Thank you,

James Bayer

Join to automatically receive all group messages.