From 6ec47d79cc93fcc58385cb357ff3f1c8a09ce6c1 Mon Sep 17 00:00:00 2001 From: Michael Stanclift Date: Mon, 11 Apr 2022 17:04:45 -0500 Subject: [PATCH] Updated Updating (markdown) --- Updating.md | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/Updating.md b/Updating.md index a30f53f..5b6732f 100644 --- a/Updating.md +++ b/Updating.md @@ -1,19 +1,18 @@ -If you'd like to know what version of the script you have running, run the built in version checker. It will notify you if there are updates available. +If you'd like to know what version of Gravity Sync you have running, run the built in version checker. It will notify you if there are updates available. ```bash -./gravity-sync.sh version +gravity-sync version ``` You can then run the built-in updater to get the latest version of all the files. Both the `version` and `update` commands reach out to GitHub, so outbound access to GitHub.com is required. ```bash -./gravity-sync.sh update +gravity-sync update ``` -Your copy of the `gravity-sync.conf` file, logs and backups should not be be impacted by this update, as they are specifically ignored. The main goal of Gravity Sync is to be simple to execute and maintain, so any additional requirements should also be called out when it's executed. +If the built in updater doesn't function as expected, you can reinstall Gravity Sync using the single line installer. This will make sure you have the latest copy. Your existing configuration file will not be impacted. -After updating, be sure to manually run a `./gravity-sync.sh compare` to validate things are still working as expected. +- Make sure to run the update command on both Gravity Sync instances. +- After updating, please run `gravity-sync compare` from each Pi-hole to validate things are still working as expected. -You can run a `./gravity-sync.sh config` at any time to generate a new configuration file if you're concerned that you're missing something, especially after a major version upgrade. - -- If the update script fails, make sure you did your original deployment via the online installation script or with `git clone` -- and not a manual install. Refer to [Updater Issues](https://github.com/vmstan/gravity-sync/wiki/Troubleshooting#updater-issues) or [Manual Updates](https://github.com/vmstan/gravity-sync/wiki/Under-The-Covers#manual-updates) for more details. \ No newline at end of file +You can run a `gravity-sync config` at any time to generate a new configuration file if there are issues or you're concerned that you're missing something, especially after a major version upgrade.