Re: CF v205 / Pushing an app
Dieu Cao <dcao@...>
I'll look into getting that page updated.
One known issue is that CC doesn't have a concept of a default shared
domain when pushing apps.
The CLI assumes it's the first shared domain that comes back in the list.
Depending how you're splitting your domain, you may need to create a new
shared domain, delete any other shared domains until your desired shared
domain for apps is first in the `cf domains` list and create/map routes
with your new shared app domain to existing apps.
-Dieu
toggle quoted message
Show quoted text
One known issue is that CC doesn't have a concept of a default shared
domain when pushing apps.
The CLI assumes it's the first shared domain that comes back in the list.
Depending how you're splitting your domain, you may need to create a new
shared domain, delete any other shared domains until your desired shared
domain for apps is first in the `cf domains` list and create/map routes
with your new shared app domain to existing apps.
-Dieu
On Tue, Oct 13, 2015 at 8:03 AM, Sylvain Gibier <sylvain(a)munichconsulting.de
wrote:
Hi,
Thanks for the clarification - it should be worth to update the
documentation (
http://docs.cloudfoundry.org/deploying/ec2/bootstrap-aws-vpc.html) - as I
followed this one, and this setting is not even mentioned anywhere.
Any known issues should I be aware before trying to split an existing CF
deployment ? Does it mean that both application and system domain go
through the same ELB (cfrouter) ? Quid of existing application deployed ?
Sylvain