mirror of
https://github.com/stevejenkins/pihole-cloudsync.git
synced 2025-07-25 19:12:12 +00:00
Updating README
This commit is contained in:
@ -68,13 +68,13 @@ Again, **the above steps must be performed on each Pi-hole you wish to use with
|
||||
## 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 few 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, do `sudo crontab -e` and create a cron entry such as:
|
||||
Once you can successfully run `pihole-cloudsync --push` from the command line on your Primary Pi-hole, do `crontab -e` (or `sudo crontab -e`) and create a cron entry such as:
|
||||
|
||||
`00 01,07,13,19 * * * /usr/local/bin/pihole-cloudsync/pihole-cloudsync --push > /dev/null 2>&1 #Push Master Pi-hole Lists to remote Git repo`
|
||||
`00 01,07,13,19 * * * sudo /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, do `sudo crontab -e` and create a cron entry that runs 5 minutes after your Primary pushes any changes, such as:
|
||||
|
||||
`05 01,07,13,19 * * * /usr/local/bin/pihole-cloudsync/pihole-cloudsync --pull > /dev/null 2>&1 #Pull Master Pi-hole Lists from remote Git repo`
|
||||
`05 01,07,13,19 * * * sudo /usr/local/bin/pihole-cloudsync/pihole-cloudsync --pull > /dev/null 2>&1 #Pull Master Pi-hole Lists from remote Git repo`
|
||||
|
||||
# Disclaimer
|
||||
You are totally responsible for anything this script does to your system. Whether it launches a nice game of Tic Tac Toe or global thermonuclear war, you're on your own. :)
|
||||
|
Reference in New Issue
Block a user