From 80a3df4ad9f2adf888ce0e90b38e368c3a12467e Mon Sep 17 00:00:00 2001 From: Michael Stanclift Date: Mon, 11 Apr 2022 16:58:47 -0500 Subject: [PATCH] Updated 4.0 (markdown) --- 4.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/4.0.md b/4.0.md index 651297c..6a7cade 100644 --- a/4.0.md +++ b/4.0.md @@ -76,7 +76,7 @@ Gravity Sync now uses a dedicated SSH key for connection to remote Pi-hold insta ### Migrate Existing Configuration -From your existing Gravity Sync folder, running any version 3.1 to 3.7, run `./gravity-sync.sh update` and the the version 4.0 code will temporarily come into the legacy folder. At this point `./gravity-sync.sh` is the migration tool to move you to the version 4.0 format. +From your existing Gravity Sync folder, running any version 3.1 to 3.7, run `./gravity-sync.sh update` and the version 4.0 code will temporarily come into the legacy folder. At this point `./gravity-sync.sh` is the migration tool to move you to the version 4.0 format. Run `./gravity-sync.sh` **again** and a new Gravity Sync 4 installation will be laid down for you and your existing configuration, logs, SSH key, and hashes will be migrated to the fresh install. Legacy backup files are not retained. At the end of a successful script execution the legacy Gravity Sync folder will be deleted, so you may need to run a `cd ~` to get yourself out of the now deleted folder.