From 98bf07a6c0e9476611f714e0477c422132f1dd7a Mon Sep 17 00:00:00 2001 From: Michael Stanclift Date: Wed, 21 Oct 2020 20:10:36 -0500 Subject: [PATCH] Updated Other Functions (markdown) --- Other-Functions.md => Pull-vs-Push.md | 14 +------------- 1 file changed, 1 insertion(+), 13 deletions(-) rename Other-Functions.md => Pull-vs-Push.md (66%) diff --git a/Other-Functions.md b/Pull-vs-Push.md similarity index 66% rename from Other-Functions.md rename to Pull-vs-Push.md index 3237e3e..c5750bc 100644 --- a/Other-Functions.md +++ b/Pull-vs-Push.md @@ -20,16 +20,4 @@ Before executing, this will make a copy of the remote database under `backup/gra This function purposefully asks for user interaction to avoid being accidentally automated. -- If your script prompts for a password on the remote system, make sure that your remote user account is setup not to require passwords in the sudoers file. - -### The Restore Function - -Gravity Sync can also `restore` the database on the secondary Pi-hole in the event you've overwritten it accidentally. This might happen in the above scenario where you've had your primary Pi-hole down for an extended period, made changes to the secondary, but perhaps didn't get a chance to perform a `push` of the changes back to the primary, before your automated sync ran. - -```bash -./gravity-sync.sh restore -``` - -This will copy your last `gravity.db.backup` and `custom.list.backup` to the running copy on the secondary Pi-hole. - -This function purposefully asks for user interaction to avoid being accidentally automated. \ No newline at end of file +- If your script prompts for a password on the remote system, make sure that your remote user account is setup not to require passwords in the sudoers file. \ No newline at end of file