summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorgit-annex@17927e6dc041ab425c14217a97a685adf3ecf44f <git-annex@web>2019-11-13 19:38:56 +0000
committeradmin <admin@branchable.com>2019-11-13 19:38:56 +0000
commit8ebcc32745cf96ffa70f738ce166b620dbee41f5 (patch)
treea19fb74531d6ddd06bbcb758814632a1ffd433fb
parent58be3af084771f3296c799ef7f6aa4f6650861cb (diff)
-rw-r--r--doc/forum/git-annex_clients_with_only_a_gitLab_repo_and_GDrive_special_remote_in_common.mdwn20
1 files changed, 20 insertions, 0 deletions
diff --git a/doc/forum/git-annex_clients_with_only_a_gitLab_repo_and_GDrive_special_remote_in_common.mdwn b/doc/forum/git-annex_clients_with_only_a_gitLab_repo_and_GDrive_special_remote_in_common.mdwn
new file mode 100644
index 0000000000..a1177cbf1d
--- /dev/null
+++ b/doc/forum/git-annex_clients_with_only_a_gitLab_repo_and_GDrive_special_remote_in_common.mdwn
@@ -0,0 +1,20 @@
+Greetings,
+
+I'm setting up git-annex as the store for a darktable environment. I have to assume that all of the backup and client machines can not necessarily see each-other. Let's call them:
+client1
+client2
+backup
+usb (incr. backup - in case a client can't reach the gdrive)
+gitlab (upstream - do I need to group this as well - if so, what)
+gdrive (again, labeled as a backup so it will take everything)
+
+They all can reach both a gitlab repo (I know they don't support annex anymore) and a special remote for the large files (gdrive via the rclone remote to allow me to use a team drive)
+
+So either client1 or client2 will create or update content. git-annex assistant on the client will sync that to gitlab and gdrive (I assume).
+
+The question is, will git-annex assistant on backup and the other client check to see if there have been updates to the gitlab upstream? If so, how often? If not, should I git-annex schedule a git-annex-sync on each client and backup to force it?
+
+Thx
+Christopher
+
+