Add example for Kubernetes secret as additional source (#294)
As discussed in #286, an example for using Kubernetes secrets as additional configuration source was missing. This adds it. Co-authored-by: techknowlogick <techknowlogick@gitea.io> Reviewed-on: https://gitea.com/gitea/helm-chart/pulls/294 Reviewed-by: techknowlogick <techknowlogick@gitea.io> Reviewed-by: luhahn <luhahn@noreply.gitea.io> Co-authored-by: justusbunsi <justusbunsi@noreply.gitea.io> Co-committed-by: justusbunsi <justusbunsi@noreply.gitea.io>
This commit is contained in:
parent
f2948646ba
commit
7bdf742e81
15
README.md
15
README.md
@ -341,6 +341,21 @@ data:
|
||||
ENABLED=true
|
||||
```
|
||||
|
||||
Or when using a Kubernetes secret, having the same data structure:
|
||||
|
||||
```yaml
|
||||
apiVersion: v1
|
||||
kind: Secret
|
||||
metadata:
|
||||
name: gitea-security-related-configuration
|
||||
type: Opaque
|
||||
stringData:
|
||||
security: |
|
||||
PASSWORD_COMPLEXITY=off
|
||||
session: |
|
||||
SAME_SITE=strict
|
||||
```
|
||||
|
||||
### External Database
|
||||
|
||||
An external Database can be used instead of builtIn PostgreSQL or MySQL.
|
||||
|
Loading…
Reference in New Issue
Block a user