Skip to content

Commit 63464e7

Browse files
release-controller[bot]release-controller[bot]
authored and
release-controller[bot]
committed
3.14.3 release
1 parent 7a64e2d commit 63464e7

File tree

3 files changed

+2
-149
lines changed

3 files changed

+2
-149
lines changed

docs/backup.config-example

-147
This file was deleted.

docs/getting-started.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -37,5 +37,5 @@
3737
3838
[1]: https://github.com/github/backup-utils/releases
3939
[2]: https://github.com/github/backup-utils/releases/tag/v2.11.4
40-
[3]: https://github.com/github/enterprise-backup-site/blob/master/docs/backup.config-example
40+
[3]: https://github.com/github/enterprise-backup-site/blob/master/backup.config-example
4141
[4]: https://docs.github.com/enterprise-server/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh

docs/usage.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ These commands are run on the host you [installed][1] Backup Utilities on.
1313

1414
You can supply your own configuration file or use the example configuration file as a template where you can set up your environment for backing up and restoring.
1515

16-
An example configuration file with documentation on possible settings can found in [backup.config-example](backup.config-example).
16+
An example configuration file with documentation on possible settings can found in [backup.config-example](../backup.config-example).
1717

1818
There are a number of command-line options that can also be passed to the `ghe-restore` command. Of particular note, if you use an external MySQL service but are restoring from a snapshot prior to enabling this, or vice versa, you must migrate the MySQL data outside of the context of backup-utils first, then pass the `--skip-mysql` flag to `ghe-restore`.
1919

0 commit comments

Comments
 (0)