From adcdfedaed9217c410ff495a1c853a7d1ce6f87c Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnb2yfWzJ2lYQw1UTm6XVZ4y8qashNagZA" Date: Thu, 26 Feb 2015 12:48:56 +0000 Subject: [PATCH] Added a comment: Re: comment1 --- ...ent_2_e362221ef3d13bd417b2b6b0c51738a8._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/forum/Repository_backup/comment_2_e362221ef3d13bd417b2b6b0c51738a8._comment diff --git a/doc/forum/Repository_backup/comment_2_e362221ef3d13bd417b2b6b0c51738a8._comment b/doc/forum/Repository_backup/comment_2_e362221ef3d13bd417b2b6b0c51738a8._comment new file mode 100644 index 0000000000..e84be7f22a --- /dev/null +++ b/doc/forum/Repository_backup/comment_2_e362221ef3d13bd417b2b6b0c51738a8._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawnb2yfWzJ2lYQw1UTm6XVZ4y8qashNagZA" + nickname="Daniel" + subject="Re: comment1" + date="2015-02-26T12:48:56Z" + content=""" +Thanks for the tip! + +Yeah, I get that special remotes aren't meant for this, and backing up a bare (i.e. contentless) git repo somewhere else is pretty trivial. My only point was that it'd be nice to have a single unified offsite backup--if you backup the content to S3, say, and the git repo itself to Github, you now have two points of failure and, in some sense, twice the management hassle. (I now need both my Amazon and Github credentials to restore, for example.) + +This seems somewhat undesirable in a backup system. + +An easy way around this may be for me to just have a wrapper script that first backs up content to the special remote and then copies the .git repo (minus the objects) to the same place. So it's something I can easily enough work around. +"""]]