lunny/helm-chart
1
0
Fork 1
Code Issues 36 Pull Requests 14 Actions Packages Projects Releases 93 Wiki Activity

Use image tag instead of image version in values #91

Merged
lafriks merged 1 commits from refs/pull/91/head into master 2020-12-20 22:53:46 +00:00
Conversation 4 Commits 1 Files Changed 1 +7 -7
1 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
View File

@ -6,7 +6,7 @@
This helm chart has taken some inspiration from <https://github.com/jfelten/gitea-helm-chart>
But takes a completly different approach in providing database and cache with dependencies.
Also this chart provides ldap and admin user configuration with values as well as it is deployed as statefulset to retain stored repositories.
Also this chart provides LDAP and admin user configuration with values as well as it is deployed as statefulset to retain stored repositories.
## Dependencies
@ -21,7 +21,7 @@ Dependencies:
## Installing
```
```sh
helm repo add gitea-charts https://dl.gitea.io/charts/
helm install gitea gitea-charts/gitea
```
@ -60,7 +60,7 @@ INSTALL_LOCK is always set to true, since we want to configure gitea with this h
If a builtIn database is enabled the database configuration is set automatically. For example postgresql builtIn which will appear in the app.ini as:
```
```ini
[database]
DB_TYPE = postgres
HOST = RELEASE-NAME-postgresql.default.svc.cluster.local:5432
@ -73,7 +73,7 @@ USER = gitea
Memcached is handled the exakt same way as database builtIn. Once memcached builtIn is enabled, this chart will generate the following part in the app.ini:
```
```ini
[cache]
ADAPTER = memcache
ENABLED = true
@ -85,7 +85,7 @@ HOST = RELEASE-NAME-memcached.default.svc.cluster.local:11211
The server defaults are a bit more complex.
If ingress is enabled, the ROOT_URL, DOMAIN and SSH_DOMAIN will be set accordingly. HTTP_PORT always defaults to 3000 as well as SSH_PORT to 22.
```
```ini
[server]
APP_DATA_PATH = /data
DOMAIN = git.example.com
@ -235,8 +235,8 @@ It is not possible to delete an admin user after it has been created. This has t
### LDAP Settings
Like the admin user the ldap settings can be updated but also disabled or deleted.
All ldap values from <https://docs.gitea.io/en-us/command-line/#admin> are available.
Like the admin user the LDAP settings can be updated but also disabled or deleted.
All LDAP values from <https://docs.gitea.io/en-us/command-line/#admin> are available.
You can either use them in camel case or kebab case.
camelCase: