* bug: Fix docker actions.
We renamed directories in docker/ which broke the actions.
Also try to refactor the action files a little so that we can run (but not publish) these images on pull requests that change the docker/ dir as an extra check. Note this only seems to be supported by the dockerhub plugin; the github plugin doesn't support this (so that will be an issue when we move to it only).
* Drop extra pipes
* 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.
* build(docker): build & publish docker images to GitHub Packages
Will kepp publishing to Docker Hub meanwhile until all Dockerfiles have been updated to point to GitHub.
Fixes https://github.com/linkedin/datahub/issues/1548
* Rebase & fix dockerfile locations
PRs are setup to skip docs.
Also, only run docker actions on linkedin/datahub (i.e. disable on forks; makes forks nicer since you don't have failing actions).
* add a sequence diagram and a description
* update descrpition based on feedback
* Update README.md
* Update README.md
Co-authored-by: Mars Lan <mars.th.lan@gmail.com>
Other repos have similar RFC processes (though they seem to have a separate repo for their RFC docs).
This provides a more structured way for contributors to make siginficant design contributions.
https://github.com/linkedin/datahub/issues/1692
