DevFW-CICD/forgejo-helm
16
0
Fork 1
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: small readme updates

Browse source
This commit is contained in:
xeruf 2025-01-23 13:02:40 +01:00
parent c386e289f5
commit 72c45de1d1
1 changed files with 4 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
README.md
View file

@ -531,7 +531,7 @@ postgresql:
This chart enables you to create a default admin user. This chart enables you to create a default admin user.
It is also possible to update the password for this user by upgrading or redeploying the chart. It is also possible to update the password for this user by upgrading or redeploying the chart.
Deleting the admin user can only be done from the UI. To delete it, you need to remove this block and delete the user in the UI.
You cannot use `admin` as username. You cannot use `admin` as username.
```yaml ```yaml
@ -693,12 +693,7 @@ route:
When using the rootless image, the GPG key folder is not persistent by default. When using the rootless image, the GPG key folder is not persistent by default.
If you want commits by Forgejo (e.g. initial commit) to be signed, If you want commits by Forgejo (e.g. initial commit) to be signed,
you need to provide a signing key. you need to provide a signing key:
Prior to [PR186](https://gitea.com/gitea/helm-chart/pulls/186),
imported keys had to be re-imported once the container got replaced by another.
The mentioned PR introduced a new configuration object `signing` so you can configure prerequisites for commit signing.
By default this section is disabled to maintain backwards compatibility.
```yaml ```yaml
signing: signing:
@ -706,6 +701,8 @@ signing:
gpgHome: /data/git/.gnupg gpgHome: /data/git/.gnupg
``` ```
By default this section is disabled to maintain backwards compatibility.
Regardless of the used container image the `signing` object allows to specify a private GPG key. Regardless of the used container image the `signing` object allows to specify a private GPG key.
Either using the `signing.privateKey` to define the key inline, or referring to an existing secret containing the key data with `signing.existingSecret`. Either using the `signing.privateKey` to define the key inline, or referring to an existing secret containing the key data with `signing.existingSecret`.