Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using Domains with ADOP #6

Open
luismsousa opened this issue Dec 7, 2017 · 0 comments
Open

Using Domains with ADOP #6

luismsousa opened this issue Dec 7, 2017 · 0 comments

Comments

@luismsousa
Copy link

Hi,

I've recently come across an issue whereby I spin up the stack but then have to manually update the compose instance if I want to use a custom Domain with valid SSL certs.

Example:

  • Spin up the 2 tiered Stack
  • Define Domain in Route53
  • Add record set to point the domain name adop.customdomain.com to the outer Proxy
  • Add the SSL termination rules on the outer proxy
  • Update the Stack: Need to update the tools Manually
    • doesn't get persisted and will revert on compose restart
  • log in to the stack, change the PROXY_IP variables, re-run compose
    • might create inconsistent behaviour with some of the tools (need to test)

A way to get around this would be to change the setup order and spin up all of the infrastructure components before spinning up the stack. This will allow inputting a CUSTOM_URL to the compose start which will then be used at up time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants