Using Docker to Containerize Toy NodeJS Application
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 become familiar with setting up a basic docker problem to gain an understanding of how to run a docker container with an active server.
How are you going to achieve the goal or solve the problem?
Setting up a basic hello world nodeJS service and containerizing it. Possibly following a video or written guide.
What will be produced as a result of this effort and where will it live on GitLab?
A list of URLs and a basic docker file that demonstrates the code needed to spin up a basic Docker container with an application.
Give a justification of weight or due date.
This should take roughly 1-3 days because of the need to gain an understanding of how the technology works.
Who will do it, and what will they do?
@ajantara Will be assigned to the task and he will create a Toy nodeJs application and attempt to get that application running in a Docker Container.
What was the outcome?
A toy project has been created here. This is probably the most basic setup that can be achieved using Docker to run a project where the frontend and backend are in separate containers. Additional work is being done by @nathanlach60 to add a reverse proxy to the setup using nginx. This will be important further down the road when all the microservices need to communicate with each other.
Template Version 1.0.0
/label type::spike