You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 23, 2022. It is now read-only.
Why?
Suppose as a user if I am only interested in running the application and not making changes
then I can run this as is without installing anything apart from docker
The text was updated successfully, but these errors were encountered:
I think the usual way is to create separate Dockerfile for each backend and frontend and run through docker-compose, but here our project structure is slightly different.
First, we have to restructure the whole project into two directory, frontend and backend, only then we can go ahead with containerization. Please check @Any28Flo forked version of project here, she is currently working on restructuring, after that you can go ahead with this. Feel free to assist her in it.
Let me know you thoughts on this.
Sure I agree with you and moreover I think we can connect it to Github actions later on to continuosly push the image to the dockerhub on every commit what do you think ?
Idea:
I am thinking of containerizing the project
Why?
Suppose as a user if I am only interested in running the application and not making changes
then I can run this as is without installing anything apart from docker
The text was updated successfully, but these errors were encountered: