From a0627fdeca22387f80a99e8b5e57f388e6aae492 Mon Sep 17 00:00:00 2001 From: Joseph Date: Wed, 14 Jun 2023 11:58:14 -0600 Subject: [PATCH 1/2] Update containers.twig tiny change to reflect exact button texts Signed-off-by: Joseph --- php/templates/containers.twig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/php/templates/containers.twig b/php/templates/containers.twig index a5af8fc7..4f23b861 100644 --- a/php/templates/containers.twig +++ b/php/templates/containers.twig @@ -265,7 +265,7 @@ {% if has_update_available == true %} {% if is_mastercontainer_update_available == false %} - ⚠️ Container updates are available. Click on Stop Containers and Start Containers to update them. You should consider creating a backup first.

+ ⚠️ Container updates are available. Click on Stop containers and Start and update containers to update them. You should consider creating a backup first.

{% endif %} {% else %} {% if is_mastercontainer_update_available == false %} From bcf0f92d8781fa2cb8c1e2bbf9f2f99ca0fa16fb Mon Sep 17 00:00:00 2001 From: Simon L Date: Thu, 15 Jun 2023 15:06:40 +0200 Subject: [PATCH 2/2] also adjust it in the doc Signed-off-by: Simon L --- readme.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/readme.md b/readme.md index cf4b0c93..89038fec 100644 --- a/readme.md +++ b/readme.md @@ -290,7 +290,7 @@ This project values stability over new features. That means that when a new majo You can switch to a different channel like e.g. the beta channel or from the beta channel back to the latest channel by stopping the mastercontainer, removing it (no data will be lost) and recreating the container using the same command that you used initially to create the mastercontainer. You simply need to change the last line `nextcloud/all-in-one:latest` to `nextcloud/all-in-one:beta` and vice versa. ### How to update the containers? -If we push new containers to `latest`, you will see in the AIO interface below the `containers` section that new container updates were found. In this case, just press `Stop containers` and `Start containers` in order to update the containers. The mastercontainer has its own update procedure though. See below. And don't forget to back up the current state of your instance using the built-in backup solution before starting the containers again! Otherwise you won't be able to restore your instance easily if something should break during the update. +If we push new containers to `latest`, you will see in the AIO interface below the `containers` section that new container updates were found. In this case, just press `Stop containers` and `Start and update containers` in order to update the containers. The mastercontainer has its own update procedure though. See below. And don't forget to back up the current state of your instance using the built-in backup solution before starting the containers again! Otherwise you won't be able to restore your instance easily if something should break during the update. If a new `Mastercontainer` update was found, you'll see an additional section below the `containers` section which shows that a mastercontainer update is available. If so, you can simply press on the button to update the container.