1. Cf-Dev
  2. Topics

private vs public visibility of apps

Matthias Ender <Matthias.Ender@...>
 

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 convenient.

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?

thanks,
Matthias

?
attachment.html

Josh Ghiloni
 

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)ECSTeam.com<mailto:rgarrett(a)ECSTeam.com>

ECS Team
Technology Solutions Delivered
ECSTeam.com<http://www.ecsteam.com/> <http://www.ecsteam.com/>


________________________________
From: cf-dev-bounces(a)lists.cloudfoundry.org <cf-dev-bounces(a)lists.cloudfoundry.org> on behalf of Matthias Ender <Matthias.Ender(a)sas.com>
Sent: Monday, June 29, 2015 2:46 PM
To: cf-dev(a)lists.cloudfoundry.org
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 convenient.



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?



thanks,

Matthias

?
attachment.html

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

[1]
https://blog.starkandwayne.com/2014/10/31/public-and-private-microservices-on-the-same-cloud-foundry/
[2]
https://docs.google.com/document/d/1bGOQxiKkmaw6uaRWGd-sXpxL0Y28d3QihcluI15FiIA/edit

On Mon, Jun 29, 2015 at 2:23 PM, Josh Ghiloni <jghiloni(a)ecsteam.com> 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)ECSTeam.com <rgarrett(a)ECSTeam.com>



*ECS Team *

*Technology Solutions Delivered*

ECSTeam.com <http://www.ecsteam.com/> <http://www.ecsteam.com/>


------------------------------
*From:* cf-dev-bounces(a)lists.cloudfoundry.org <
cf-dev-bounces(a)lists.cloudfoundry.org> on behalf of Matthias Ender <
Matthias.Ender(a)sas.com>
*Sent:* Monday, June 29, 2015 2:46 PM
*To:* cf-dev(a)lists.cloudfoundry.org
*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
convenient.



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?



thanks,

Matthias



_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

--
Thank you,

James Bayer

?
attachment.html

Matthias Ender <Matthias.Ender@...>
 

excellent.

I can create domain to the private proxy that's included



cf create-shared-domain apps.<ip of private_haproxy>.xip.io

and then push my app to it

cf push -d apps.<ip of private_haproxy>.xip.io myapp

?
attachment.html

1 - 4 of 4