summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar http://a-or-b.myopenid.com/ <http://a-or-b.myopenid.com/@web>2013-05-17 00:54:51 +0000
committerGravatar admin <admin@branchable.com>2013-05-17 00:54:51 +0000
commit91eb772830bc7a4eb57c2f17cee9db0384a975a7 (patch)
tree7abd8c6689b4f92ed6f7bc3ee78810cd8f9cbd0b /doc
parentda9040cb1c415d2f8a5bec2baf5ea49596cb3419 (diff)
Diffstat (limited to 'doc')
-rw-r--r--doc/forum/Running_assistant_steps_manually.mdwn20
1 files changed, 20 insertions, 0 deletions
diff --git a/doc/forum/Running_assistant_steps_manually.mdwn b/doc/forum/Running_assistant_steps_manually.mdwn
new file mode 100644
index 000000000..b3b683433
--- /dev/null
+++ b/doc/forum/Running_assistant_steps_manually.mdwn
@@ -0,0 +1,20 @@
+Unfortunately one of the machines that I am running git-annex on is too old to handle the watcher thread.
+
+The error message is:
+
+ Watcher crashed: Need at least OSX 10.7.0 for file-level FSEvents
+
+
+I am however interested in duplicating the assistant steps manually. I'm happy to accept that I won't have the great, auto-magic, coverage, but, how I run the steps that the assistant runs?
+
+I'm guessing there is a:
+
+ git annex add .
+ git commit -m "[blah]"
+ git annex sync
+
+but how do I get the pushing to backup/transfer/whatever remotes to work? And what order should I do these?
+
+What I would *like* to do is get a script that runs all of the needed annex steps and then kick it off in a cron job 2-5 times a day.
+
+Any thoughts?