From ae473695a61a1fa89087284d2a1279a4ad0d2649 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnZEanlyzay_QlEAL0CWpyZcRTyN7vay8U" Date: Tue, 22 Oct 2013 09:35:05 +0000 Subject: [PATCH] --- .../__34__Pairing__34___more_than_two_computers.mdwn | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/forum/__34__Pairing__34___more_than_two_computers.mdwn 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 0000000000..099c7a6631 --- /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