Mirrored_Repos/pihole-cloudsync
1
0
Fork 0
mirror of https://github.com/stevejenkins/pihole-cloudsync.git synced 2024-08-30 18:22:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updating README

Browse Source
This commit is contained in:
Steve Jenkins 2019-07-10 14:04:05 -07:00
parent 71f920624f
commit a8c7633b0a
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -64,13 +64,13 @@ to enter and save your credentials. Now you can run `pihole-cloudsync` unattende
Again, **the above steps must be performed on each Pi-hole you wish to use with `pihole-cloudsync`.** Again, **the above steps must be performed on each Pi-hole you wish to use with `pihole-cloudsync`.**
## Automating with cron ## Automating with cron
Once each Pi-hole's local Git repo has been configured to save your login credentials, you can automate your Primary Pi-hole's "push" and your Secondary Pi-holes' "pull" in any number of ways. The simplest way is to run a simple cron job a couple times a day. Once each Pi-hole's local Git repo has been configured to save your login credentials, you can automate your Primary Pi-hole's "push" and your Secondary Pi-holes' "pull" in any number of ways. The simplest way is to run a simple cron job a couple times a day. Remember to set the cron job for the root user (with `sudo crontab -e`).
Once you can successfully run `pihole-cloudsync --push` from the command line on your Primary Pi-hole, create a cron entry such as: Once you can successfully run `pihole-cloudsync --push` from the command line on your Primary Pi-hole, do `sudo crontab -e` and create a cron entry such as:
`00 01,13 * * * /usr/local/bin/pihole-cloudsync/pihole-cloudsync --push > /dev/null 2>&1 #Push Master Pi-hole Lists to remote Git repo` `00 01,13 * * * /usr/local/bin/pihole-cloudsync/pihole-cloudsync --push > /dev/null 2>&1 #Push Master Pi-hole Lists to remote Git repo`
And once you can successfully run `pihole-cloudsync --pull` from the command line on each of your Secondary Pi-holes, create a cron entry that runs 5 minutes after your Primary pushes any changes, such as: And once you can successfully run `pihole-cloudsync --pull` from the command line on each of your Secondary Pi-holes, do `sudo crontab -e` and create a cron entry that runs 5 minutes after your Primary pushes any changes, such as:
`05 01,13 * * * /usr/local/bin/pihole-cloudsync/pihole-cloudsync --push > /dev/null 2>&1 #Pull Master Pi-hole Lists from remote Git repo` `05 01,13 * * * /usr/local/bin/pihole-cloudsync/pihole-cloudsync --push > /dev/null 2>&1 #Pull Master Pi-hole Lists from remote Git repo`