Files
lasuite-docs/src/helm/env.d/feature/values.dev-backend.yaml.gotmpl
T
Anthony LC 5a804d8588 🐛(helm) bump the dev-backend chart to run silo
The dev-backend chart 0.0.10 started the media storage with a hardcoded
`minio server` shell command and pulled quay.io/minio/mc to create the
bucket. Since the switch to pgsty/silo, the first one failed with
"minio: command not found" and the second one with a 401 from quay.io, so
the feature deployments (ArgoCD) did not come up.

Chart 0.0.15 defaults to pgsty/silo and pgsty/mc, and starts the container
with `args` instead of a shell command, so the name of the executable no
longer matters.
2026-10-13 14:39:31 +02:00

59 lines
1.2 KiB
Go Template

postgres:
enabled: true
name: postgres
#serviceNameOverride: postgres
image: postgres:16-alpine
username: dinum
password: pass
database: docs
size: 5Gi
redis:
enabled: false
minio:
enabled: true
image: pgsty/silo
mc:
image: pgsty/mc
name: minio
ingress:
enabled: true
hostname: {{ .Values.feature }}-minio.{{ .Values.domain }}
tls:
enabled: true
secretName: docs-tls
consoleIngress:
enabled: true
hostname: {{ .Values.feature }}-minio-console.{{ .Values.domain }}
tls:
enabled: true
secretName: docs-tls
username: dinum
password: password
bucket: docs-media-storage
versioning: true
size: 5Gi
keycloak:
enabled: true
image: quay.io/keycloak/keycloak:20.0.1
name: keycloak
annotations:
cert-manager.io/cluster-issuer: letsencrypt
#serviceNameOverride: keycloak
hostname: {{ .Values.feature }}-docs-keycloak.{{ .Values.domain }}
username: admin
password: pass
tls:
enabled: true
secretName: docs-tls
db:
username: dinum
password: pass
database: keycloak
size: 5Gi
image: postgres:16-alpine
realm:
name: docs
username: docs
password: docs
email: docs@example.com