Skip to content

Latest commit

 

History

History
71 lines (51 loc) · 2.05 KB

CUSTOMISING.md

File metadata and controls

71 lines (51 loc) · 2.05 KB

Customisation

Customizing DAMAP backend

To migrate with the base, you need to fetch updates with upstream, following Semantic Versioning guidelines:

  • Major: Big changes (first value).
  • Minor: Additional changes (second value). For more details on Semantic Versioning, see semver.org.

Dependency Management

Maven Central Approach: You can specify the DAMAP version as a dependency, and Maven will automatically pull it from Maven Central.

Overriding Configuration Values

To connect required components, provide values to custom config variables in application.yaml. To use YAML, add the following to your pom.xml:

<dependency>
  <groupId>io.quarkus</groupId>
  <artifactId>quarkus-config-yaml</artifactId>
</dependency>

Copy the custom config settings from the backend's application.yaml to your project’s application.yaml, and edit them as needed.

You can override these variables at runtime using environment variables (see quarkus config guide).

damap:
  origins: https://your.frontend.com, https://*.yourdomain.com

Configuring Authentication Service

Add the following values for authentication service integration:

damap:
  auth:
    url: https://your.authentication.server
    client:
      backend: your-backend-authentication-client-id
      frontend: your-frontend-authentication-client-id
    scope: your-authentication-scope
    user: your-authentication-claim-holding-the-user-id

Configuring the Database

Provide database config values:

damap:
  datasource:
    url: jdbc:your-datasource-url
    username: your-database-username
    password: your-database-password
    db-kind: postgresql

If you want to customize Liquibase, you can create your own changelogs. For example:

liquibase:
  migrate-at-start: true
  change-log: at/ac/tugraz/damap/db/newChangeLog-root.yaml

Include the damap changelogs and create custom ones as needed.