From 90612e91c8532bea9fa30d57c8a80eaaa6b3a9e4 Mon Sep 17 00:00:00 2001 From: justusbunsi Date: Fri, 5 Jul 2024 21:07:32 +0200 Subject: [PATCH] Drop ineffective production single-pod settings As discovered in https://gitea.com/gitea/helm-chart/pulls/585#issuecomment-760170 (bottom part), as long as an Chart internal redis is enabled (no matter which), users are not able to overrule its settings. Signed-off-by: justusbunsi --- README.md | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index a110ebf..56d902e 100644 --- a/README.md +++ b/README.md @@ -247,7 +247,7 @@ External tools such as `redis-cluster` or `memcached` handle these workloads muc If HA is not needed/desired, the following configurations can be used to deploy a single-pod Gitea instance. -1. For a production-ready single-pod Gitea instance without external dependencies (using the chart dependency `postgresql`): +1. For a production-ready single-pod Gitea instance without external dependencies (using the chart dependency `postgresql` and `redis`):
@@ -270,12 +270,6 @@ If HA is not needed/desired, the following configurations can be used to deploy config: database: DB_TYPE: postgres - session: - PROVIDER: db - cache: - ADAPTER: memory - queue: - TYPE: level indexer: ISSUE_INDEXER_TYPE: bleve REPO_INDEXER_ENABLED: true @@ -295,6 +289,8 @@ If HA is not needed/desired, the following configurations can be used to deploy ```yaml redis-cluster: enabled: false + redis: + enabled: false postgresql: enabled: false postgresql-ha: