From 5d6943b893e04542e23a7216e858cbe06760a6d7 Mon Sep 17 00:00:00 2001 From: Lukey Date: Sun, 2 May 2021 08:03:56 +0000 Subject: [PATCH] Added a comment --- ...omment_1_f77818a766f2b41d13ced2bcf4447de0._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/forum/dev_machine_-__62___NAS_-__62___cloud/comment_1_f77818a766f2b41d13ced2bcf4447de0._comment diff --git a/doc/forum/dev_machine_-__62___NAS_-__62___cloud/comment_1_f77818a766f2b41d13ced2bcf4447de0._comment b/doc/forum/dev_machine_-__62___NAS_-__62___cloud/comment_1_f77818a766f2b41d13ced2bcf4447de0._comment new file mode 100644 index 0000000000..b33329dbd1 --- /dev/null +++ b/doc/forum/dev_machine_-__62___NAS_-__62___cloud/comment_1_f77818a766f2b41d13ced2bcf4447de0._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="Lukey" + avatar="http://cdn.libravatar.org/avatar/c7c08e2efd29c692cc017c4a4ca3406b" + subject="comment 1" + date="2021-05-02T08:03:56Z" + content=""" +I guess you could just put something like this in your crontab: +`*/5 * * * * cd /path/to/repo; flock -n .git/periodic-sync.lock git annex sync --content --all` + +As a optimization, you could only sync with `--content --all` if the git-annex branch changed since the last time it ran. +"""]] -- 2.30.2