summaryrefslogtreecommitdiff
path: root/git_backup
diff options
context:
space:
mode:
authorMiguel <m.i@gmx.at>2021-11-07 00:38:17 +0100
committerMiguel <m.i@gmx.at>2021-11-07 00:38:17 +0100
commit7d82a05300aff62c16c612904c9a6e9311ccb71f (patch)
tree41c789020e8cadf8c3f27f76321f3cb349259cd3 /git_backup
parent55ceb41956343d59cb156dadf6d7491bd7ee9279 (diff)
minor change in backup scripts
Diffstat (limited to 'git_backup')
-rw-r--r--git_backup/git_backup.sh2
1 files changed, 1 insertions, 1 deletions
diff --git a/git_backup/git_backup.sh b/git_backup/git_backup.sh
index fef095a..348d559 100644
--- a/git_backup/git_backup.sh
+++ b/git_backup/git_backup.sh
@@ -3,7 +3,7 @@
#But even if you do not have the capability to do snapshots, you can still make consistent backups, as long as you back up objects after refs. You might end up with some dangling objects, but your repository will be consistent and all refs will point to existing objects. With rsync, that could look like:
TIMESTAMP=$(date +%Y%m%d%H%M%S)
-INPUT=comet:/var/lib/gitolite/repositories
+INPUT=root@comet:/var/lib/gitolite/repositories
OUTPUT=~/BACKUPS/comet_git_backup/$TIMESTAMP
OUTPUT_TAR=~/BACKUPS/comet_git_backup/$TIMESTAMP.tar