Fix #714: large file upload tuning as configuration

charts/nextcloud/CHANGELOG.md

@@ -0,0 +1,13 @@
+# Changelog
+
+This Helm-Chart increase there major version on every breaking change (or major version of Nextcloud itself) inspired by semantic releases.
+
+Here we list all major versions and their breaking changes for migration.
+
+## v7
+
+- update redis to v20 (see [CHANGELOG](https://github.com/bitnami/charts/blob/main/bitnami/redis/CHANGELOG.md#2000-2024-08-09))
+- update postgresql to v16 (see [CHANGELOG](https://github.com/bitnami/charts/blob/main/bitnami/postgresql/CHANGELOG.md#1600-2024-10-02))
+- update mariadb to v19 (see [CHANGELOG](https://github.com/bitnami/charts/blob/main/bitnami/mariadb/CHANGELOG.md#1900-2024-07-11))
+- update mariadb to v20 (see [CHANGELOG](https://github.com/bitnami/charts/blob/main/bitnami/mariadb/CHANGELOG.md#2000-2024-11-08))
+- update nextcloud to v31 (see [CHANGELOG](https://nextcloud.com/changelog/#31-0-0))

charts/nextcloud/Chart.lock

@@ -1,15 +1,15 @@
 dependencies:
 - name: postgresql
   repository: oci://registry-1.docker.io/bitnamicharts
-  version: 15.5.0
+  version: 16.5.1
 - name: mariadb
   repository: oci://registry-1.docker.io/bitnamicharts
-  version: 18.2.0
+  version: 20.4.1
 - name: redis
   repository: oci://registry-1.docker.io/bitnamicharts
-  version: 19.6.4
+  version: 20.11.3
 - name: collabora-online
   repository: https://collaboraonline.github.io/online
   version: 1.1.20
-digest: sha256:00e8d82d28825fd3f46e7e7d888d1aac93ebdb5135f6a4d7e6ae0c3155881c27
-generated: "2024-12-15T19:47:53.357052+01:00"
+digest: sha256:527dbb38da0523da66605923a74ca2f5666d3548f1618114e85b08d4759ec2d3
+generated: "2025-03-17T20:39:18.201813568+01:00"

charts/nextcloud/Chart.yaml

@@ -1,8 +1,8 @@
 apiVersion: v2
 name: nextcloud
-version: 6.6.9
+version: 7.0.1
 # renovate: image=docker.io/library/nextcloud
-appVersion: 30.0.6
+appVersion: 31.0.2
 description: A file sharing server that puts the control and security of your own data back into your hands.
 keywords:
   - nextcloud
@@ -28,15 +28,15 @@ maintainers:
     url: https://jessebot.work
 dependencies:
   - name: postgresql
-    version: 15.5.0
+    version: 16.5.1
     repository: oci://registry-1.docker.io/bitnamicharts
     condition: postgresql.enabled
   - name: mariadb
-    version: 18.2.0
+    version: 20.4.1
     repository: oci://registry-1.docker.io/bitnamicharts
     condition: mariadb.enabled
   - name: redis
-    version: 19.6.4
+    version: 20.11.3
     repository: oci://registry-1.docker.io/bitnamicharts
     condition: redis.enabled
   - name: collabora-online

charts/nextcloud/README.md

@@ -15,6 +15,7 @@ helm install my-release nextcloud/nextcloud
 * [Prerequisites](#prerequisites)
 * [Installing the Chart](#installing-the-chart)
 * [Uninstalling the Chart](#uninstalling-the-chart)
+* [Upgrade / Breaking Changes](#upgrade--breaking-changes)
 * [Configuration](#configuration)
     * [Ingress](#ingress)
         * [Ingress Sticky-Sessions](#ingress-sticky-sessions)
@@ -97,6 +98,11 @@ helm delete my-release
 
 The command removes all the Kubernetes components associated with the chart and deletes the release.
 
+## Upgrade / Breaking Changes
+
+There is a Changelog of breaking changes here: [CHANGELOG.md](./CHANGELOG.md).
+You should read it bevore updating.
+
 ## Configuration
 
 The following table lists the configurable parameters of the nextcloud chart and their default values.

charts/nextcloud/files/nginx.config.tpl

@@ -26,9 +26,7 @@ server {
     {{- end }}
     {{- end }}
 
-    # set max upload size
-    client_max_body_size 10G;
-    fastcgi_buffers 64 4K;
+    {{- .Values.nginx.config.serverBlockCustom | nindent 4 }}
 
     # Enable gzip but do not remove ETag headers
     gzip on;

charts/nextcloud/values.yaml

@@ -353,6 +353,13 @@ nginx:
       "X-Robots-Tag": "noindex, nofollow"
       "X-XSS-Protection": "1; mode=block"
 
+    # Added in server block of default config.
+    serverBlockCustom: |
+      # set max upload size
+      client_max_body_size 10G;
+      fastcgi_buffers 64 4K;
+      fastcgi_read_timeout 3600s;
+
     custom:
     # custom: |-
     #     worker_processes  1;..