The project folder structure is illustrated below: backend/ up -build command from within the devops directory. The devops folder contains the docker-compose.yaml file which is used by Docker compose to set up the project using the docker-compose -f. Within the backend and frontend folders are contained the source code folders and the node_modules folders (more on this later). This example project is set up in such a way that the backend, devops and frontend folders all exist within the same project folder. If you have access to Docker for Windows then it would be easier to set up Docker compose on Ubuntu Bash as described in this article, but if you don't have access to Windows Premium (and thus no Hyper-V), this is a good alternative.

Note that if you would like to simply see the code, skip to the end of this article. On a recent project, many issues came up when trying to set up a common JavaScript stack (Node + Angular) using Docker Compose in a Vagrant Ubuntu Virtual Machine (VM) with VirtualBox as a provider. Be that as it may, some challenges still arise in using these tools due to varying operating systems and the way in which they operate, especially when it comes to Windows. Thankfully, tools such as Kubernetes and Docker allow for the easy automation of these setups which can be shared between all members of a team. It is common knowledge among developers that setting up your development environment for a new project can be a time consuming task that no one really enjoys doing.

Vagrant up provider virtualbox