-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Docker Support to enhance developer experience #38
Comments
@hvini @KarinePistili I would like to work on this issue |
@asr2003 I have a good experience with this issue, can you please assign this to me? |
@KarinePistili @hvini Any insights on it? |
Hello @asr2003, we never considered using docker on the front app cause we already have the environment properly configured, but for those who don't have it could be a good idea. your steps seems good, so, i will assign to you and then you can open a PR when you finish |
Hello @asr2003 will you able to work on this? |
Yes @KarinePistili. I have exams right now and will be submit a PR on this weekend :) |
Great! We will wait for you then ;) |
Title:
Adding Docker Support to web-eye-tracker-front
Description:
Problem:
web-eye-tracker-front currently lacks Docker support, hindering its ease of deployment and scalability. Adding Docker support is essential to streamline the deployment process and make it more accessible to a broader audience.
Solution:
Implementing Docker support for web-eye-tracker-front would involve creating a Dockerfile and configuration to package the application into a Docker container. This containerization would simplify deployment, improve consistency across environments and enhance scalability.
Approach:
To achieve Docker support for web-eye-tracker-front, we can follow these steps:
Additional Context:
Adding Docker support aligns with modern development practices, making it easier for developers to set up and run web-eye-tracker-front in various environments. Docker containers provide isolation, portability, and reproducibility, contributing to a more robust and user-friendly development and deployment experience.
The text was updated successfully, but these errors were encountered: