Serve frontend over ExpressJS
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?
- In a production environment, the HTML file that displays our page must be delivered to the user in order for them to see it.
- Currently we don't have anything serving our page in our Node.js code, so we need to implement this functionality through a serving application. ExpressJS is the industry standard. (I'm not very well versed in this technology, so the terminology may be used incorrectly)
- The goal of this issue is to have the html page that the user interacts with served by Express JS, and the documentation updated accordingly
How are you going to acheive the goal or solve the problem?
- Adjusting the package.json file
- Updating the tech stack in the readme
- Figuring out how to implement, and then implementing ExpressJS
- Getting the above step to work inside of a docker container and with other npm scripts
What will be produced as a result of this effort and where will it live on GitLab?
-
There is a very comprehensible guide that can be followed here: https://www.digitalocean.com/community/tutorials/use-expressjs-to-deliver-html-files
-
You'll need to install ExpressJS through npm in the repository.
Give a justification of weight or due date.
-
This ticket should be worth around 6 points. It can be broken up as follows:
- Adjusting the package.json file - 1 point
- Updating the tech stack in the readme - 1 point
- Figuring out how to implement, and then implementing ExpressJS - 2 - 3 points.
- Getting the above step to work inside of a docker container and with other npm scripts - 1 - 2 points.
Who will do it, and what will they do?
@mm413 will be responsible for this issue For what they will do, see the justification section directly above.
What was the outcome?
- The frontend is now being served over Express, allowing for key cloak integration with Auth
Template Version 1.0.0
Edited by Mark Meade