Components
The following table provides information about the components of the Discover application.
- The component names match the arguments used in the deployment script. For example, the "auth" component actually consists of two containers - the Keycloak server and a PostgreSQL database.
- The components designated as "public" listen on all interfaces, which means that they can be accessed remotely. The components that are not public listen only on the loopback interface, so cannot be accessed remotely.
Component | Port | Public | Description |
---|---|---|---|
auth | 8000 | No | A PostgreSQL database that stores the authentication server configuration. |
auth | 8010 | Yes | Keycloak authentication server (API and admin UI). |
entity | 8021 | No | The ACI port of the IDOL Content component. |
entity | 8022 | No | The Index port of the IDOL Content component. |
entity | 8023 | No | The port of the Cassandra database backend for the Gremlin database. |
filestore | 8030 | No | S3-compatible object storage. If you wish you can replace this component with your own S3-compatible object store (see Use a Custom Object Store). |
analysis | 8040 | No | An Apache NiFi instance for performing media analysis (API and admin UI). |
audit | 8050 | No | A PostgreSQL database that stores audit logs. |
dataset-locations | 8100 | No | The ACI port of an IDOL Content component, which is used for the locations database. |
api | 8060 | Yes | The Discover HTTP API. |
ui | 8090 | Yes | The Discover UI (front-end application). |