SCS: Integrate Front-End and Back-End via API
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?
The goal of this issue is to, after refactoring, link the newly created UI to use our API. Without this linking step, "real" data cannot be used by the front end.
Epic: &2 (closed)
Issues: #18 (closed)
How are you going to achieve the goal or solve the problem?
We will work with CCLK'D to implement our resulting Docker container as a dependency with their .docker-compose.yml
. From there, the front end should have communication to the API's endpoints and our data set will be available for use in the front end as needed.
What will be produced as a result of this effort and where will it live on GitLab?
The .docker-compose.yml
file in the frontend project will be modified to use our API as a dependency.
Give a justification of weight or due date.
- Weight: 4
- Due Date: 04/01/2023
- Justification: This task requires a significant amount of communication between CCLK'D and SCS to ensure proper functionality between the two systems. It will take time to develop & verify.
Who will do it, and what will they do?
@egartley will lead this project with @njsharpe as support & review. We will work together with members from CCLK'D for this implementation. In the process, we will need to research Docker dependencies and GitLab's CI/CD with a Docker image as an artifact.