Closed RussellMcOrmond closed 5 years ago
Adding @SaschaAdler for help, as I don't know how to test this.
I'm also not sure how it currently works in production, given the Apache config is using a servername "u.figaro.tor.c7a.ca" which uses a private network address and is not available externally. On Figaro it is using name-based HTTP, so it has to match that name otherwise it will be sent to CAP (the CDP version) which is the first listed Apache config. This will change with containers as each webserver will be allocated its own IP address to bind to.
How do we want to connect in cookie-authorizer? I gave the reference to our private registry, but that might not be how others will use it. In production I will use a different compose file based on the one here, so the compose should work for developers and not be tied to now it will run in production.
New year, new brain.
Somehow I was confusing Upholstery which we will be using as part of the admin tools, and Gorilla which is intended to provide a public API. Upholstery was only in testing, which is why it wasn't given a public interface.
I've disabled the running of Upholstery on Figaro for now, and we can decide where we wish to deploy when we are ready.
The running Upholstery app has 3 parts:
The current compose file doesn't build those connections.