From 10326e19117fd20de8bc3fa30ac898e8ec76971a Mon Sep 17 00:00:00 2001 From: Simon L Date: Wed, 27 Sep 2023 20:58:12 +0200 Subject: [PATCH] add additional disadvantage to manual-install and helm-chart Signed-off-by: Simon L --- manual-install/readme.md | 1 + nextcloud-aio-helm-chart/readme.md | 1 + 2 files changed, 2 insertions(+) diff --git a/manual-install/readme.md b/manual-install/readme.md index 602488e6a94..def74197e1b 100644 --- a/manual-install/readme.md +++ b/manual-install/readme.md @@ -11,6 +11,7 @@ You can run the containers that are build for AIO with docker-compose. This come - You lose the AIO interface - You lose update notifications and automatic updates - You lose all AIO backup and restore features +- You lose all community containers: https://github.com/nextcloud/all-in-one/tree/main/community-containers - **You need to know what you are doing, especially when modifying the compose.yaml file** - For updating, you need to strictly follow the at the bottom described update routine - Probably more diff --git a/nextcloud-aio-helm-chart/readme.md b/nextcloud-aio-helm-chart/readme.md index d3959df651e..3305052535e 100755 --- a/nextcloud-aio-helm-chart/readme.md +++ b/nextcloud-aio-helm-chart/readme.md @@ -10,6 +10,7 @@ You can run the containers that are build for AIO with Kubernetes using this Hel - You lose the AIO interface - You lose update notifications and automatic updates - You lose all AIO backup and restore features +- You lose all community containers: https://github.com/nextcloud/all-in-one/tree/main/community-containers - **You need to know what you are doing** - For updating, you need to strictly follow the at the bottom described update routine - You need to monitor yourself if the volumes have enough free space and increase them if they don't by adjusting their size in values.yaml