[droningparrot]

I'm really not a fan of absolute paths in the compose file:

  services:
    volumes:
      - /path/to/my/code/on/my/dev/machine:/path/to/the/code/in/the/container

If you're sharing your docker-compose.yml file with other developers, this will get annoying really quickly. Normally, I'd place the docker-compose.yml file in the root of my project, and then replace "/path/to/my/code/on/my/dev/machine" with ".". That way, it doesn't matter where other devs keep code on their machines.

In the case where you have a compose file that builds multiple projects (See: double time!), keep the compose file in one git repo, and then include the code for the other two projects (webappone and webapptwo) as submodules.