summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawnZEanlyzay_QlEAL0CWpyZcRTyN7vay8U <Carlo@web>2013-10-22 09:35:05 +0000
committerGravatar admin <admin@branchable.com>2013-10-22 09:35:05 +0000
commitddbd8c75d11490b4e4a1474b3f48854e54352e0e (patch)
treec8fcf37fcb6cd9efa701aa3d848a8e368a8d6e2c /doc
parente8dd97e91d72484f8677f8233ce0103bdbf7e87f (diff)
Diffstat (limited to 'doc')
-rw-r--r--doc/forum/__34__Pairing__34___more_than_two_computers.mdwn11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/forum/__34__Pairing__34___more_than_two_computers.mdwn b/doc/forum/__34__Pairing__34___more_than_two_computers.mdwn
new file mode 100644
index 000000000..099c7a663
--- /dev/null
+++ b/doc/forum/__34__Pairing__34___more_than_two_computers.mdwn
@@ -0,0 +1,11 @@
+I need some help understanding here.
+
+We use AeroFS at work to sync the normal user files across computers. I'll quite likely be replacing that with git annex as soon as Windows port is stable enough.
+
+How it works is that you create a repo, and share it with one or more users. Then AeroFS discovers what other repos are online and if they're on the local network, and syncs from wherever is most convenient.
+
+This sounds a little like pairing, but with pairing you need to arrange more than 2 devices in a "star" or "chain". This is fine for my own devices, but it becomes brittle if you have lots of devices syncing from each other, which may or may not be online at any given time. The only way around it seems to be to pair each device with each other device, with the labor rising exponentially.
+
+Is this correct? Best compromise for my use case seems to be to just do a star setup and pair everything with an always-on machine. Do you agree?
+
+Thanks! Carlo