Skip to content

Commit 9f8f52c

Browse files
author
keeper
committed
docs: quote the hosts instead of inventing an authority
1 parent a0a803f commit 9f8f52c

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

README.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,9 @@ Everyone lives in git. Almost nobody backs it up. gitdr copies your entire GitHu
1919
2020
## Why
2121

22-
Your repos are the control plane now. Infra, deploys, runbooks, all of it lives in git. But your host runs on shared responsibility. They keep the lights on. If your data goes because someone deleted it, took over an account, or dropped ransomware, that part is on you.
22+
Your repos are the control plane now. Infra, deploys, runbooks, all of it lives in git. Your host keeps the lights on, and says in its own documentation where that stops.
23+
24+
GitHub: ["After you delete an organization, GitHub cannot restore your content."](https://docs.github.com/en/organizations/managing-organization-settings/deleting-an-organization-account) GitLab: ["While data security is ensured for GitLab.com, you can't use these methods to export or back up your data from GitLab.com."](https://docs.gitlab.com/administration/backup_restore/) Neither sells a first-party backup product. If your data goes because someone deleted it, took over an account, or dropped ransomware, that part is on you.
2325

2426
gitdr writes backups to a bucket you own and checks it's WORM (write-once-read-many) before writing, so you never get a false sense of safety. WORM is strongly recommended. Turning it on is your call, and `--require-worm` makes gitdr refuse anything softer if you want the hard guarantee.
2527

0 commit comments

Comments
 (0)