Update README.md

This commit is contained in:
Michael Stanclift 2020-05-28 13:30:34 -05:00 committed by GitHub
parent b7f35ffaed
commit e73b29a129
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -44,7 +44,7 @@ Download the latest release from [GitHub](https://github.com/vmstan/gravity-sync
```bash ```bash
cd ~ cd ~
wget https://github.com/vmstan/gravity-sync/archive/v1.5.0zip wget https://github.com/vmstan/gravity-sync/archive/v1.5.0.zip
unzip v1.5.0.zip unzip v1.5.0.zip
mv ~/gravity-sync-1.5.0 ~/gravity-sync mv ~/gravity-sync-1.5.0 ~/gravity-sync
cd gravity-sync cd gravity-sync
@ -224,4 +224,4 @@ chmod +x gravity-sync.sh
- If you use a non-standard SSH port to connect to your primary Pi-hole, you can add `SSH_PORT='123'` to the bottom of your `gravity-sync.conf` file. (Subsitute 123 for your non-standard port.) This will overwrite the `SSH_PORT=22` at the top of the script as it is imported later in the execution. - If you use a non-standard SSH port to connect to your primary Pi-hole, you can add `SSH_PORT='123'` to the bottom of your `gravity-sync.conf` file. (Subsitute 123 for your non-standard port.) This will overwrite the `SSH_PORT=22` at the top of the script as it is imported later in the execution.
- If you'd like to know what version of the script you have running by running `./gravity-sync.sh version` - If you'd like to know what version of the script you have running by running `./gravity-sync.sh version`
- If the update script fails, make sure you did your original deployment via `git clone` and not a manual install. - If the update script fails, make sure you did your original deployment via `git clone` and not a manual install.
- If it doesn't kick off, you can manually execute a `git pull` while in the `gravity-sync` directory. - If it doesn't kick off, you can manually execute a `git pull` while in the `gravity-sync` directory.