Cutlery/gravity-sync
1
0
Fork 0
mirror of https://github.com/vmstan/gravity-sync.git synced 2025-07-31 14:33:47 -04:00
Code Issues Packages Projects Releases Wiki Activity

Created Updating (markdown)

Michael Stanclift 2020-10-21 16:04:44 -05:00
parent a125739edc
commit e4d2712a98
1 changed files with 19 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
Updating.md Normal file

@ -0,0 +1,19 @@
If you'd like to know what version of the script you have running, run the built in version checker. It will notify you if there are updates available.
```bash
./gravity-sync.sh version
```
You can then run the built-in updater to get the latest version of all the files. Both the `version` and `update` commands reach out to GitHub, so outbound access to GitHub.com is required.
```bash
./gravity-sync.sh update
```
Your copy of the `gravity-sync.conf` file, logs and backups should not be be impacted by this update, as they are specifically ignored. The main goal of Gravity Sync is to be simple to execute and maintain, so any additional requirements should also be called out when it's executed.
After updating, be sure to manually run a `./gravity-sync.sh compare` to validate things are still working as expected.
You can run a `./gravity-sync.sh config` at any time to generate a new configuration file if you're concerned that you're missing something, especially after a major version upgrade.
- If the update script fails, make sure you did your original deployment via the online installation script or with `git clone` -- and not a manual install. Refer to [Updater Issues](https://github.com/vmstan/gravity-sync/wiki/Troubleshooting#updater-issues) or [Manual Updates](https://github.com/vmstan/gravity-sync/wiki/Under-The-Covers#manual-updates) for more details.