There've been some issues relating to how stack-docker starts up stuff using the docker-compose image.
  * changing project names
  * volume mounts not working
  * some other issues regaring containers not starting.

I've moved everything around and more use of docker volumes:
  * created certs volume, for storing the certs. Now all containers can mount that volume and have access to the certs.
  * created a config volume for each service
    * this mounts the config.yml for each service and also stores the keystore.

These changes help process a lot of the permissions issues that were happening.
This makes it a lot easer to clean up using a 'docker-compose down -v' and restart.

known issues:
  * the setup script doesn't work as cleanly as I'd like and when trying execute it via a
    'docker-compose -f setup/setup.yml run setup' the script exits early.

and update the setup command to be correct.

… into nick/docker-volumes