Utilize bjw-s's common Helm library. #13

Merged
konrad merged 41 commits from :new-helm-chart into main 2023-11-07 14:47:24 +00:00
1 changed files with 2 additions and 7 deletions
Showing only changes of commit 746555db06 - Show all commits

View File

@ -7,13 +7,6 @@
image:
tag: 0.21.0
perfectra1n marked this conversation as resolved Outdated

Is there a reason we're using env here and not the config directly?

We should still be able to configure Vikunja as it can be done currently: https://kolaente.dev/vikunja/helm-chart/src/branch/main/values.yaml#L142

There are things that can't be configured via env like openid providers.

Is there a reason we're using env here and not the config directly? We should still be able to configure Vikunja as it can be done currently: https://kolaente.dev/vikunja/helm-chart/src/branch/main/values.yaml#L142 There are things that can't be configured via env like openid providers.

Ah, didn't know that. I thought everything was configurable via env variables (which I've always found easier to manage), but I'll go ahead and use the config instead.

Ah, didn't know that. I thought everything was configurable via `env` variables (which I've always found easier to manage), but I'll go ahead and use the `config` instead.
storage:
persistence:
# Automatically creating the library volume is not supported by this chart
# You have to specify an existing PVC to use
existingClaim:
######################
# VIKUNJA COMPONENTS #
######################
@ -24,6 +17,8 @@ api:
repository: vikunja/api
pullPolicy: IfNotPresent
persistence:
# This is your Vikunja data will live, you can either let
konrad marked this conversation as resolved Outdated

Doesn't this need a link to the docs with the default config?

Doesn't this need a link to the docs with the default config?

fixed

d8500214e9

fixed https://kolaente.dev/vikunja/helm-chart/commit/d8500214e98def13755bad78e31e9b2e39404df1
# the chart create a new PVC for you or provide an existing one.
data:
enabled: true
# existingClaim: # your-claim