Is your feature request related to a problem? If so, please describe.
We currently have to navigate to the frontend directory to start the frontend container and then navigate to the backend directory to the backend container. We also need an extra two commands.
Describe the solution you'd like
It would be a better developer experience if we kept two separate Dockerfiles (one for the frontend and one backend) with one docker-compose.yml in the root of the project.
This would reduce the number of steps it takes to start the project:
Only one docker-compose build, not two
One command to start the frontend, backend and db containers
Only one docker-compose down command to stop and remove the running containers, not two
No need to navigate to the frontend directory and then into the backend directory
Total savings: 5 fewer commands to run everything
Additional context
Be sure to read the contributing guidelines first!
Discuss your implementation approach with us before we assign you to it
Provide us with an estimate on how long you think it will take you to complete
Branch from main and set main as the destination branch in your pull request
Is your feature request related to a problem? If so, please describe. We currently have to navigate to the frontend directory to start the frontend container and then navigate to the backend directory to the backend container. We also need an extra two commands.
Describe the solution you'd like It would be a better developer experience if we kept two separate Dockerfiles (one for the frontend and one backend) with one docker-compose.yml in the root of the project.
This would reduce the number of steps it takes to start the project:
docker-compose build, not twodocker-compose downcommand to stop and remove the running containers, not twoTotal savings: 5 fewer commands to run everything
Additional context
mainand setmainas the destination branch in your pull requestIf you need help with anything, we'll be happy to help you over a GitHub Q&A discussion or our Slack workspace