John Plaisted b8e18b0b5d
refactor(docker): make docker files easier to use during development. (#1777)
* Make docker files easier to use during development.

During development it quite nice to have docker work with locally built code. This allows you to launch all services very quickly, with your changes, and optionally with debugging support.

Changes made to docker files:
- Removed all redundant docker-compose files. We now have 1 giant file, and smaller files to use as overrides.
- Remove redundant README files that provided little information.
- Rename docker/<dir> to match the service name in the docker-compose file for clarity.
- Move environment variables to .env files. We only provide dev / the default environment for quickstart.
- Add debug options to docker files using multistage build to build minimal images with the idea that built files will be mounted instead.
- Add a docker/dev.sh script + compose file to easily use the dev override images (separate tag; images never published; uses debug docker files; mounts binaries to image).
- Added docs/docker documentation for this.
2020-08-06 16:38:53 -07:00
..

DataHub Generalized Metadata Store (GMS) Docker Image

datahub-gms docker

Refer to DataHub GMS Service to have a quick understanding of the architecture and responsibility of this service for the DataHub.

Other Database Platforms

While GMS defaults to using MySQL as its storage backend, it is possible to switch to any of the database platforms supported by Ebean.

For example, you can run the following command to start a GMS that connects to a PostgreSQL backend.

(cd docker/ && docker-compose -f docker-compose.yml -f docker-compose.postgre.yml -p datahub up)

or a MariaDB backend

(cd docker/ && docker-compose -f docker-compose.yml -f docker-compose.mariadb.yml -p datahub up)