sonicaj
6da73fe25c
Update catalog information
|
%!s(int64=2) %!d(string=hai) anos | |
|---|---|---|
| .. | ||
| charts | %!s(int64=2) %!d(string=hai) anos | |
| ci | %!s(int64=2) %!d(string=hai) anos | |
| templates | %!s(int64=2) %!d(string=hai) anos | |
| Chart.lock | %!s(int64=2) %!d(string=hai) anos | |
| Chart.yaml | %!s(int64=2) %!d(string=hai) anos | |
| README.md | %!s(int64=2) %!d(string=hai) anos | |
| app-readme.md | %!s(int64=2) %!d(string=hai) anos | |
| ix_values.yaml | %!s(int64=2) %!d(string=hai) anos | |
| questions.yaml | %!s(int64=2) %!d(string=hai) anos | |
README.md
Gitea
Gitea - Git with a cup of tea
When application is installed, a container will be launched with root privileges. This is required in order to apply the correct permissions to the
giteadirectories. Afterward, thegiteacontainer will run as a non-root user (Default:568). Same applies to thepostgrescontainer. This will run afterwards as a non-root user (999). On each upgrade, a container will be launched with root privileges in order to apply the correct permissions to thepostgresbackups directory. Container that performs the backup will run as a non-root user (999) afterwards. Keep in mind the permissions on the backup directory will be changed to999:999on every update. But will only be changed once for thegiteaandpostgresdata directories.
On initial startup a setup wizard will be launched with settings for database, ports and root url prefilled.
Keep them as they are, fill the Administration section and click on Install Gitea.