Improvement to docker-compose to support dev work
We would like to have a docker-compose file that spins up needed docker containers and mounts our Nomad dev folder from the host machine into these containers. This means we run the local version of our Nomad source code rather than the one compiled into the container image.
This allows us to have almost the same dev environment as a production Nomad Oasis install.
Here are some recommendations or ideas we have already discussed in Area B:
- Make use of the docker-compose from ops/docker-compose/nomad-oasis
- Mount the dev folder into all containers that are not just infrastructure i.e. the app, hub, gui, etc.
- Run yarn in hot reload on the gui folder instead of using the production build for the gui container
- Maybe it is a good idea to check if we need to change/add some helper scripts to reload things like generate_gui_artifacts.sh. We would guess for scripts that just create new files on disk this wouldn't be an issue.