A Direct Consortial Borrowing Service for OpenRS Libraries
翻訳待ち
Loading the full README. The saved excerpt is shown below.
A Direct Consortial Borrowing Service for the OpenRS resource sharing project.
This module is distributed in source and pre-compiled docker container form:
• https://github.com/openlibraryenvironment/dcb-service
• https://nexus.libsdev.k-int.com/#browse/browse:libsdev-docker:v2%2Fknowledgeintegration%2Fdcb
Upgrading from 8.x to v9.0.0? Read
docs/v9-migration-guide.md before you deploy. v9.0.0
carries migrations that are not free, an automatic re-clustering sweep, the removal of
the PATRON role, and it is not cleanly reversible.Read the full README ↗A Direct Consortial Borrowing Service for the OpenRS resource sharing project.
This module is distributed in source and pre-compiled docker container form:
Upgrading from 8.x to v9.0.0? Read docs/v9-migration-guide.md before you deploy.
By creating a bootstrap.yml file and mounting it at /bootstrap.yml, then referencing this file in an environment variable: MICRONAUT_CONFIG_FILES=/bootstrap.yml devops teams can point DCB at a local secret manager. Info for different environments can be found here: https://guides.micronaut.io/latest/tag-distributed_configuration.html and the bootstrap.yml under dcb/src/main/resources contains commented out sections for AWS Secrets Manager and Hashicorp Vault.
It is important to note that Micronaut declarative configuration reads environment variables last, so if switching to secrets manager, you should remember to remove any environment variables as they will override distributed config.
The module is deployed as a docker container which supports the following runtime ENV settings
Note: Today flyway does not support r2dbc datasources, so we need to configure both JDBC and R2DBC datasources - same DB connection effectively, 2 different connections - with JDBC only being used for database migrations.
This is the beginning of the README. Read the rest at the original. Read the full README ↗