Cutlery/gravity-sync
1
0
Fork 0
mirror of https://github.com/vmstan/gravity-sync.git synced 2025-07-09 02:34:06 -04:00
Code Issues Packages Projects Releases Wiki Activity

Updated 4.0 (markdown)

Michael Stanclift 2022-04-11 16:58:47 -05:00
parent 442a7b7eed
commit 80a3df4ad9
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
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 ### 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. 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.