Skip to content

nextcloud

Upgrading nextcloud

Before Upgrading

Before upgrading read the Guide and Critical Changes if upgrading to the next major version. Make sure no database version upgrade is required, and if so, it is required to perform the MariaDB upgrade procedures with backup beforehand.

Upgrading NGINX

Moreover, update the nginx ConfigMap to the newest nginx.conf.

Change the following sections in nginx.conf to customize to the cluster (without the description comments starting with ##):

## Change app:9000 to 127.0.0.1:9000

upstream php-handler {
    server 127.0.0.1:9000;
}

## Change and add the below values

# set max upload size and increase upload timeout:
proxy_max_temp_file_size 0;
proxy_buffering off;
proxy_request_buffering off;
fastcgi_read_timeout 86400s;
client_max_body_size 0;
client_body_timeout 86400s;
fastcgi_buffers 64 4K;
Deployment upgrade

To upgrade, change the nextcloud image to the latest revision of the minor version unless upgrading to the next major version, and wait for the pod to be restarted and the upgrade logs inside the pod container to conclude.

After the upgrade, you need to run the long running steps manually, and finally run php occ maintenance:repair --include-expensive.

NOTE: In order to run occ: use the bash shell started by su -s /bin/bash www-data or run su -s /bin/sh -c 'php occ [command]' www-data inside the nextcloud container of the nextcloud-fpm pod.

Collabora and LanguageTool should only require a restart to upgrade.