Configure Guest Info System Network
License and Copyright Notice
By submitting this issue or commenting on this issue, or contributing any content to this issue, you certify under the Developer Certificate of Origin that the content you post may be licensed under GPLv3 (for code) or CC-BY-SA 4.0 International (for non-code content).
What is the goal or the problem, and why is it important?
How are you going to achieve the goal or solve the problem?
What will be produced as a result of this effort and where will it live on GitLab?
Ideally a functional Docker network will be created, if applicable any config files will be uploaded to our repository.
Give a justification of weight or due date.
This is the totality of creating the network; it is conceivable that this could be subdivided further but given the several previous approaches that have failed before I am unable to envision a successful approach. That is I do not know what I do not know and the smallest unit of work on this seems to be the establishment and connections of containers and then testing Keycloak once the network has been configured.
Who will do it, and what will they do?
Cameron Boyle has been assigned to this. This consists of three larger initiatives:
1. Create/Acquire Images
- Keycloak
- Nginx + [APPLICABLE_JAVASCRIPT_FRONTEND]
- Express + [APPLICABLE_BACKEND]
- [APPLICABLE_DATABASE]
These variable names are given as placeholders as the initial proof concept may involve using the mock examples given to us. Moreover we may not finish some of the smaller components/services and thus will not be able to compose images of them.
**2. Spin Up and Connect Container Network(s)**
Based on the most recent architecture provided, it appears as though there will be container subnets that will be bridged by the "Express + [APPLICABLE_BACKEND]" container. Based on it's connection to other subnets (and containers?) it seems this connection should be formed first. Following that connection it stands to reason the front end should be configured to the backend and lastly keycloak should be configured in front the front end.
3. Configure Keycloak to this container network
It still is not entirely clear how I will bridge the "Nginx + [APPLICABLE_JAVASCRIPT_FRONTEND]" container to Keycloak itself, as all prior experience pointed to Nginx and Keycloak residing 'locally' (on the same image). This is the most dubious parts and I am truly back to square one with this initiative.