Documenting PING_AVOID var

ADVANCED.md

@@ -89,24 +89,24 @@ Gravity Sync is configured by default to use the `.ssh/id_rsa` keyfile that is g
 
 At this time Gravity Sync does not support passphrases in RSA keyfiles. If you have a passphrase applied to your standard `.ssh/id_rsa` either remove it, or generate a new file and specify that key for use only by Gravity Sync.
 
-Default setting for Gravity Sync is `.ssh/id_rsa`
+Default setting in Gravity Sync is `.ssh/id_rsa`
 
 #### `LOG_PATH=''`
 Gravity Sync will place logs in the same folder as the script (identified as .cron and .log) but if you'd like to place these in a another location, you can do that by identifying the full path to the directory. (ex: `/full/path/to/logs`)
 
-Default setting for Gravity Sync is `$HOME/${LOCAL_FOLDR}`
+Default setting in Gravity Sync is `$HOME/${LOCAL_FOLDR}`
 
 #### `SYNCING_LOG=''`
 Gravity Sync will write a timestamp for any completed pull, push or restore job to this file. If you want to change the name of this file, you will also need to adjust the LOG_PATH variable above, otherwise your file will be remove during `update` operations.
 
-Default setting for Gravity Sync is `gravity-sync.log`
+Default setting in Gravity Sync is `gravity-sync.log`
 
 #### `CRONJOB_LOG=''`
 Gravity Sync will log the execution history of the previous automation task via Cron to this file. If you want to change the name of this file, you will also need to adjust the LOG_PATH variable above, otherwise your file will be remove during `update` operations.
 
 This will have an impact to both the `./gravity-sync.sh automate` function and the `./gravity-sync.sh cron` functions. If you need to change this after running the automate function, either modify your crontab manually or delete the entry and re-run the automate function.
 
-Default setting for Gravity Sync is `gravity-sync.cron`
+Default setting in Gravity Sync is `gravity-sync.cron`
 
 #### `VERIFY_PASS=''`
 Gravity Sync will prompt to verify user interactivity during push, restore, or config operations (that overwrite an existing configuration) with the intention that it prevents someone from accidentally automating in the wrong direction or overwriting data intentionally. If you'd like to automate a push function, or just don't like to be asked twice to do something distructive, then you can opt-out.
@@ -126,6 +126,11 @@ Default setting in Gravity Sync is 0, change to 1 to print timestamped output.
 #### `BASH_PATH=''`
 If you need to adjust the path to bash that is identified for automated execution via Crontab, you can do that here. This will only have an impact if changed before generating the crontab via the `./gravity-sync.sh automate` function. If you need to change this after the fact, either modify your crontab manually or delete the entry and re-run the automate function.
 
+#### `PING_AVOID=''`
+The `./gravity-sync.sh config` function will attempt to ping the remote host to validate it has a valid network connection. If there is a firewall between your hosts preventing ping replies, or you otherwise wish to skip this step, it can by bypassed here.
+
+Default setting in Gravity Sync is 0, change to 1 to skip this network test.
+
 ## Execution
 If you are just straight up unable to run the `gravity-sync.sh` file, make sure it's marked as an executable by Linux.
 

CHANGELOG.md

@@ -11,6 +11,9 @@
 **Known Issues**
 - No new Star Trek references.
 
+#### 1.7.7
+- `config` function will attempt to ping remote host to validate network connection, can by bypassed by adding `PING_AVOID='1'` to your `gravity-sync.conf` file.
+
 #### 1.7.6
 - Detects `dbclient` install as alternative to OpenSSH Client.
 - Attempts to install OpenSSH Client if not found, and Dropbear is not alternative.