Join forces?

[davidkarlsen]

We already have a helm chart for dependency-track at https://github.com/evryfs/helm-charts/tree/master/charts/dependency-track - would you rather want to join forces on that one?
It's linked from https://github.com/DependencyTrack/dependency-track/blob/master/README.md

[luhahn]

Hi @davidkarlsen, i was rather busy the last few days. Sure, we'd like to join forces :)

Since your chart is already linked from the readme i guess we should move to the already existing one?

[davidkarlsen]

I think that make sense - you can do PRs against it if something is missing? Then we get one chart with two efforts around it.

[luhahn]

What do you think about the config part.
It creates a application.properties automatically, this is used instead of the environment variables. The advantage here is, that
we don't need to add anything else, because it is completly generated. Even though new values are added.
Also the users don't need to create the file themselves with a huge string.

config:
    alpine:
      worker:
        threads: 0
        thread:
          multiplier: 4

      data:
        directory: /data

      watchdog:
        logging:
          interval: 0

      database:
        pool:
          enabled: true
          max:
            size: 10
            lifetime: 600000
          idle:
            timeout: 600000

      enforce:
        authentification: true
        authorization: true

      bcrypt:
        rounds: 14

[davidkarlsen]

Hi - sorry for the silence, yes this is pretty much how I have it as well: https://github.com/evryfs/helm-charts/blob/master/charts/dependency-track/values.yaml#L96 - but combined with some vars set OOTB for ease of use: https://github.com/evryfs/helm-charts/blob/master/charts/dependency-track/templates/deployment.yaml#L40