Closed MikeTheCanuck closed 6 years ago
The A (alias) record for civicpdx.org
has been directed to 2017.civicpdx.org
.
And that of course led to an unexpected destination - now the civicpdx.org request leads to the page entitled "The Civic Lab Front End Placeholder", whose page content is
Civic Lab Front End
This where the "landing page" will be. Go out and get your service deployed
That text is only found in this one piece of content in all of HackO: https://github.com/hackoregon/hackoregon-aws-infrastructure/blob/master/services/civic-lab-service/src/index.html
...which responds also at http://service.civicpdx.org
Thus, sending all requests for civicpdx.org to 2017.civicpdx.org, is instead landing the traffic at the "civic lab service" container.
So the question is: is this a problem of the Load Balancer or Target Groups configuration in EC2?
I've implemented changes via PR 44 to try to direct requests for civicpdx.org (a) away from the container listening at service.civicpdx.org (b) to the container listening at 2017.civicpdx.org.
With the first commit to that PR I have achieved (a). With the second commit to that PR I have achieved (b).
I can't claim to know if the second commit is the right way or the only way to achieve what I have pulled off, but it is sufficiently successful for now to move on to other work.
Also, cross-reference to #186 for posterity.
Currently the http://civicpdx.org site is last year's collection of front end projects.
We are also now publishing that set of projects under http://2017.civicpdx.org.
Let's direct all traffic to the new 2017.civicpdx.org site, and eliminate the S3 bucket with that (now deprecated and no-longer-maintained) copy of the website.