datahub/docker/neo4j/README.md
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

448 B

Neo4j

DataHub uses Neo4j as graph db in the backend to serve graph queries. Official Neo4j image found in Docker Hub is used without any modification.

Neo4j Browser

To be able to debug and run Cypher queries against your Neo4j image, you can open up Neo4j Browser which is running at http://localhost:7474/browser/. Default username is neo4j and password is datahub.