From ece9429f4441345d6568ba1284054068d1c52ec1 Mon Sep 17 00:00:00 2001 From: "git-annex@17927e6dc041ab425c14217a97a685adf3ecf44f" Date: Wed, 13 Nov 2019 19:39:21 +0000 Subject: [PATCH] --- ...o_and_GDrive_special_remote_in_common.mdwn | 23 +++++++++++++++++++ 1 file changed, 23 insertions(+) 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 index a1177cbf1d..aa58a1df90 100644 --- 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 @@ -18,3 +18,26 @@ Thx Christopher + + + +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 + +