diff options
author | 2015-02-22 14:25:35 +0000 | |
---|---|---|
committer | 2015-02-22 14:25:35 +0000 | |
commit | 926f669ebcbbad5020b0ebb6007799017f6cc64f (patch) | |
tree | 1cb14698d55364dce2c2c8460e33dba85fc98fb1 /doc | |
parent | 8d1471506c2bdd89767f138de26355adaa491cbc (diff) |
Diffstat (limited to 'doc')
-rw-r--r-- | doc/forum/Repository_backup.mdwn | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/forum/Repository_backup.mdwn b/doc/forum/Repository_backup.mdwn new file mode 100644 index 000000000..39501f700 --- /dev/null +++ b/doc/forum/Repository_backup.mdwn @@ -0,0 +1,5 @@ +What's the best way of backing up the git repository itself? I feel fairly comfortable using a special remote to create an offsite backup in S3 or Glacier or whatnot, but restoring from those still requires I have a working repository somewhere that can map chunks back to files, no? + +I can probably just create a repo that has no content, tar it up, and store it on my backup medium (or on bitbucket or wherever), but that seems kinda hackish--it'd be nice to handle this within git-annex. In fact, it'd be really neat if I could handle this with any existing special remote--for example, if there were a way to commit and restore the git repo state (and symlink tree) to the remote. But that doesn't seem to exist. Is there a recommended approach for this? Am I just missing something obvious? + +Thanks. |