datahub/docker/datahub-frontend/README.md

# DataHub Frontend Docker Image

[![datahub-frontend docker](https://github.com/datahub-project/datahub/workflows/datahub-frontend%20docker/badge.svg)](https://github.com/datahub-project/datahub/actions?query=workflow%3A%22datahub-frontend+docker%22)

Refer to [DataHub Frontend Service](../../datahub-frontend) to have a quick understanding of the architecture and
responsibility of this service for the DataHub.

## Checking out DataHub UI

After starting your Docker container, you can connect to it by typing below into your favorite web browser:

If using React app:

```
http://localhost:9002
```

You can sign in with `datahub` as username and password.

## Build instructions

If you want to build the `datahub-frontend` Docker image yourself, you can run this command from the root directory of the DataHub repository you have locally (using Buildkit):

`DOCKER_BUILDKIT=1 docker build -t your_datahub_frontend -f ./docker/datahub-frontend/Dockerfile .`

Please note the final `.` and that the tag `your_datahub_frontend` is determined by you.
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 Frontend Docker Image`

fix: Replace old repository link with new link (#4446) 2022-03-18 22:12:19 +01:00			`[![datahub-frontend docker](https://github.com/datahub-project/datahub/workflows/datahub-frontend%20docker/badge.svg)](https://github.com/datahub-project/datahub/actions?query=workflow%3A%22datahub-frontend+docker%22)`
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
ci(graphql,workflows): Format .md, .graphql, and workflow .yml files via prettier (#13220) 2025-04-16 16:55:51 -07:00			`Refer to [DataHub Frontend Service](../../datahub-frontend) to have a quick understanding of the architecture and`
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			`responsibility of this service for the DataHub.`

			`## Checking out DataHub UI`

			`After starting your Docker container, you can connect to it by typing below into your favorite web browser:`

refactor(react): React as the default UI (#2252) Co-authored-by: John Joyce <john@acryl.io> 2021-03-18 09:55:05 -07:00			`If using React app:`
ci(graphql,workflows): Format .md, .graphql, and workflow .yml files via prettier (#13220) 2025-04-16 16:55:51 -07:00
refactor(react): React as the default UI (#2252) Co-authored-by: John Joyce <john@acryl.io> 2021-03-18 09:55:05 -07:00			```
			`http://localhost:9002`
			```

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			You can sign in with `datahub` as username and password.
docs(datahub-frontend): add build instructions for the datahub-frontend docker image (#3314) 2021-10-01 00:49:22 -05:00
			`## Build instructions`

fix(ingest) Azure AD: support nested groups (#4367) (#4368) LGTM - Thanks! 2022-03-14 11:59:04 -04:00			If you want to build the `datahub-frontend` Docker image yourself, you can run this command from the root directory of the DataHub repository you have locally (using Buildkit):
docs(datahub-frontend): add build instructions for the datahub-frontend docker image (#3314) 2021-10-01 00:49:22 -05:00
fix(ingest) Azure AD: support nested groups (#4367) (#4368) LGTM - Thanks! 2022-03-14 11:59:04 -04:00			`DOCKER_BUILDKIT=1 docker build -t your_datahub_frontend -f ./docker/datahub-frontend/Dockerfile .`
docs(datahub-frontend): add build instructions for the datahub-frontend docker image (#3314) 2021-10-01 00:49:22 -05:00
chore: cleanup references to the old ember app (#5797) Co-authored-by: Shirshanka Das <shirshanka@apache.org> 2022-09-04 22:42:09 -07:00			Please note the final `.` and that the tag `your_datahub_frontend` is determined by you.