290 docker compose

[michael-barbour]

closes #290

If you're using the developer setup postgres db you will probably have to docker rm -f postgresql and rebuild. If you want to use the pgadmin you may have to do the same.

Most of this ticket was ensuring I understood how the docker-compose file will allow for interactions on a developer set-up as well as for a production set-up. There will be changes to the wiki that accompany this. Please use those as a guide for how to set up the docker environment.

The docker-compose file now first pulls in .env file in the root of the repo and then replaces it with container specific overrides using the env_file and environment. This means even if a variable is not defined in the environment section, it will still get passed into the django instance if it is defined on the .env file.

Wiki Changes

• The developer setup postgres container from the wiki is now built on the chemcurator_default network. This will allow pgbouncer to talk to it using the container name "postgresql"
• There is a new section on the Deploying with Docker explaining how to find the resolver web container's url using a docker deployment.

[mwfrost]

The wiki article: https://github.com/Chemical-Curation/chemcurator_django/wiki/Deploying-with-Docker

[tbnorth]

This gets the docker-compose.yml out of the wiki back into the filesystem, with some variable cleanup.