1.8.3 (1)

This commit is contained in:
Michael Stanclift 2020-06-22 11:21:40 -05:00
parent 2842eea71e
commit ef635627ba
2 changed files with 6 additions and 6 deletions

View File

@ -13,10 +13,10 @@ There is nothing really sexy here, but a lot of changes under the covers to impr
- Generally better error handling of configuration options.
#### 1.8.3
- Simplified method for input of automation frequency via crontab.
- Removes existing automation task from crontab, if it exists.
- Automation can be disabled by setting frequency to 0 when prompted.
- Adds dev tag to version output.
- Simplified method for input of automation frequency when running `./gravity-sync.sh automate` function.
- Now removes existing automation task from crontab, if it exists, when re-running `automate` function.
- Automation can be disabled by setting frequency to `0` when prompted.
- Adds `dev` tag to `./gravity-sync.sh version` output for users running off the development branch.
#### 1.8.2
- Corrects issue where `custom.list` file would not replicate if the file didn't exist locally, and there were no other changes to replicate. [#39](https://github.com/vmstan/gravity-sync/issues/39)

View File

@ -122,7 +122,7 @@ Automation of sync is accomplished by adding an execution of the script to the u
./gravity-sync.sh automate
```
Select the frequency per hour that you'd like to sync (once, twice, quadrice, etc) and that's it.
Select the frequency per hour (in minutes) that you'd like to sync and that's it.
Now, make another small adjustment to your primary settings and wait until annointed time to see if your changes have been synchronized. If so, profit! If not, start from the beginning. From this point forward any blocklist changes you make to the primary will reflect on the secondary within the frequency you select.
@ -135,7 +135,7 @@ If you'd like to see the log of what was run the last crontab, you can view that
Keep in mind if your cron task has never run, you will not see any valid output from this command.
### Adjusting Automation
You can verify your cron entry by running `crontab -l` and see it listed at the bottom of the file. If you decide to remove or change your frequency, you'll need to run `crontab -e` and adjust this by hand. If you're unsure of how to adjust the timers by hand, just delete the entire line in the crontab file and then re-run the `./gravity-sync automate` function.
You can verify your existing automation entry by running `crontab -l` and see it listed at the bottom of the crontab file. If you decide to remove or change your frequency (as of version 1.8.3) you can run `./gravity-sync.sh automate` again and pick a new timing, including setting it to 0 to disable automation.
## Advanced Installation
Please review the [Advanced Installation](https://github.com/vmstan/gravity-sync/blob/master/ADVANCED.md) guide for assistance.