volker.raschek/helm-gitea
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

docs(README): grammar and typos

Browse Source
This commit is contained in:
Markus Pesch
2025-07-19 14:56:42 +02:00
parent 66551d417b
commit c39ab958f1
1 changed files with 7 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
README.md
View File

@@ -819,15 +819,15 @@ gitea:
## TLS certificate rotation ## TLS certificate rotation
If Gitea uses TLS certificates that are mounted as secret in the container file system, Gitea will not automatically If Gitea uses TLS certificates that are mounted as a secret in the container file system, Gitea will not automatically
apply them when the TLS certificates are rotated. Such a rotation can be for example triggered, when the cert-manager apply them when the TLS certificates are rotated. Such a rotation can be for example triggered, when the cert-manager
issues new TLS certificates before expiring. Further information is described as GitHub issues new TLS certificates before expiring. Further information is described as GitHub
[issue](https://github.com/go-gitea/gitea/issues/27962). [issue](https://github.com/go-gitea/gitea/issues/27962).
Until the GitHub issue is not solved, a workaround can be applied. For example stakater's Until the issue is present, a workaround can be applied. For example stakater's
[reloader](https://github.com/stakater/Reloader) controller can be used to trigger a rolling update. The following [reloader](https://github.com/stakater/Reloader) controller can be used to trigger a rolling update. The following
annotation must be added to instruct the reloader controller to trigger a rolling update, when the mounted configMaps annotation must be added to instruct the reloader controller to trigger a rolling update, when the mounted `configMaps`
and secrets has been changed. and `secrets` have been changed.
```yaml ```yaml
deployment: deployment:
@@ -835,8 +835,9 @@ deployment:
reloader.stakater.com/auto: "true" reloader.stakater.com/auto: "true"
``` ```
Instead of triggering a rolling update for all configMap and secret resources, it can also be defined individually. For example, Instead of triggering a rolling update for configMap and secret resources, this action can also be defined for
when the secret named `gitea-tls` is mounted and the reloader controller should only listen on changes of this secret: individual items. For example, when the secret named `gitea-tls` is mounted and the reloader controller should only
listen for changes of this secret:
```yaml ```yaml
deployment: deployment: