Generic way for configuring Gitea #243
Labels
No Label
has
backport
in progress
invalid
kind
breaking
kind
bug
kind
build
kind
dependency
kind
deployment
kind
docs
kind
enhancement
kind
feature
kind
lint
kind
proposal
kind
question
kind
refactor
kind
security
kind
testing
kind
translation
kind
ui
need
backport
priority
critical
priority
low
priority
maybe
priority
medium
reviewed
duplicate
reviewed
invalid
reviewed
wontfix
skip-changelog
status
blocked
status
needs-feedback
status
needs-reviews
status
wip
upstream
gitea
upstream
other
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/helm-chart#243
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The Helm Chart supports configuring Gitea via inline values.yaml. In larger or fine-grained configured environments this results in a cluttered configuration that may contain sensitive data as well.
To allow sensitive data being retrieved from other sources and maybe split the configuration into several sections (as the app.ini itself is split in such way), it would be great to have a generic way for configure Gitea in its whole glory.
Sensitive app.ini settings via Kubernetes secretsto Generic way for configuring Gitea