dbrepo/discovery-service repository overview

⁠Quick Reference

• Maintained by:

  the DBRepo Maintainers⁠

• Where to get help:

  the official documentation⁠, ICoDSE'22 paper⁠, IJDC'22 paper⁠, iPRES'21 paper⁠

⁠Supported tags and respective Dockerfile links

• 1.2⁠
• 1.1⁠
• latest⁠

⁠Quick reference (cont.)

• Where to file issues:

  Send us an email⁠

• Supported architectures:

  amd64

• Source of this description:

  docs repo's dockerhub/ directory⁠ (history⁠)

⁠What is DBRepo?

We present a database repository system that allows researchers to ingest data into a central, versioned repository through common interfaces, provides efficient access to arbitrary subsets of data even when the underlying data store is evolving, allows reproducing of query results and supports findable-, accessible-, interoperable- and reusable (FAIR) data.

⁠How to use this image

$ docker run -p 9090:9090 -e SPRING_PROFILES_ACTIVE=docker

⁠Customization

Change the default behavior by setting the following environment variables to different values:

• METADATA_DB, default: fda

  The Metadata Database⁠ database name.

• METADATA_USERNAME, default: root

  The Metadata Database⁠ database username.

• METADATA_PASSWORD, default: dbrepo

  The Metadata Database⁠ database password.

• LOG_LEVEL, default: debug

  The minimum logging level for the service.

⁠License

View license information⁠ for the software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.