From 377058cef1ae8113b868ac472d686756843664fb Mon Sep 17 00:00:00 2001 From: Simon L Date: Fri, 23 Dec 2022 22:03:00 +0100 Subject: [PATCH] make description of the mv command a bit clearer Signed-off-by: Simon L --- manual-install/readme.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/manual-install/readme.md b/manual-install/readme.md index 617eee60..8e52e932 100644 --- a/manual-install/readme.md +++ b/manual-install/readme.md @@ -29,7 +29,7 @@ Now you should be ready to go with `sudo docker-compose up`. ## How to update? Since the AIO containers may change in the future, it is highly recommended to strictly follow the following procedure whenever you want to upgrade your containers. -1. If your previous copy of `sample.conf` is named `my.conf`, run `mv my.conf .env` +1. If your previous copy of `sample.conf` is named `my.conf`, run `mv my.conf .env` in order to rename the file to `.env`. 1. Run `sudo docker-compose down` to stop all running containers 1. Back up all important files and folders 1. Run `git pull` in order to get the updated yaml files from the repository. Now bring your `docker-compose.yml` file up-to-date with the updated one from the repository. You can use `diff docker-compose.yml latest.yml` on x64 and `diff docker-compose.yml latest-arm64.yml` on arm64 for comparing.