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 07:25:28 -07:00
parent e7993b0542
commit 04d6eae94c
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -17,7 +17,7 @@ All other Pi-holes that you wish to keep syncronized use `pihole-cloudsync` in *
The script is designed to work with any Git repo that your Pi-holes have access to, but I have only personally tested it with GitHub. The script is designed to work with any Git repo that your Pi-holes have access to, but I have only personally tested it with GitHub.
# Setup # Setup
Prior to running `pihole-cloudsync`, you must first create a new dedicated Git respository to store your lists, then clone that new repository to the Master/Primary Pi-hole and all secondary Pi-holes that you wish to keep in sync. The easiest way to do that is to fork the blank `my-pihole-lists` example GitHub repository made for that purpose. Prior to running `pihole-cloudsync`, you must first create a new dedicated Git respository to store your lists, then clone that new repository to all Pi-holes (both Primary and Secondary) that you wish to keep in sync. The easiest way to do that is to fork my `my-pihole-lists` example GitHub repository made for that purpose. Don't worry if my personal lists in that repo are different than yours. You'll overwrite your forked version of the repo with your own Pi-hole lists the first time you run `pihole-cloudsync` in **Push** mode.
**On GitHub** **On GitHub**
1. Sign into GitHub 1. Sign into GitHub