Merge branch 'master' of ssh://git-annex.branchable.com

3 files changed, 50 insertions, 0 deletions

diff --git a/doc/forum/Restricting_SSH_+_supply_key.mdwn b/doc/forum/Restricting_SSH_+_supply_key.mdwn
new file mode 100644
index 000000000..59dd72fdc
--- /dev/null
+++ b/doc/forum/Restricting_SSH_+_supply_key.mdwn
@@ -0,0 +1,7 @@
+Just two very simple questions:
+
+1.) Is there a way to restrict the SSH key for git annex by supplying a command= ? Even better, is it also possible to supply a directory in which the repository is? (I do not want chroot - too complicated but a soft check would be sufficient for me).
+
+2.) Can I tell git and git-ssh which pubkey to use WITHOUT changing system-/user wide config (e.g.., .ssh/*)? If it is indeed not possible, what's the best way to do it in Windows?
+
+Thanks!
diff --git a/doc/forum/USB_drive_in_transfer_group_keeps_growing_-_assistant/comment_2_f9eef3019fe690e90c1228d62a16f70a._comment b/doc/forum/USB_drive_in_transfer_group_keeps_growing_-_assistant/comment_2_f9eef3019fe690e90c1228d62a16f70a._comment
new file mode 100644
index 000000000..7f761419c
--- /dev/null
+++ b/doc/forum/USB_drive_in_transfer_group_keeps_growing_-_assistant/comment_2_f9eef3019fe690e90c1228d62a16f70a._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawnNqLKszWk9EoD4CDCqNXJRIklKFBCN1Ao"
+ nickname="maurizio"
+ subject="even a client repository you had once but have now deleted"
+ date="2014-07-09T22:08:44Z"
+ content="""
+if this client repository has been deleted, why does it still have an impact? What is the user supposed to do to use a transfer repository if some day another client which was deleted has existed? 
+
+Old repositories seem to remain for ever in the webapp. You can try to delete them with the webapp, they will stay there. You can disable them, they will stay there. If you want to try to delete them again in the webapp, you first have to enable them again and nothing ever happens. There seems to be basically no way to delete repositories which have some day existed...
+"""]]
diff --git a/doc/forum/help_needed_with_setup:_2_local_computers_and_box.com.mdwn b/doc/forum/help_needed_with_setup:_2_local_computers_and_box.com.mdwn
new file mode 100644
index 000000000..e484c4f0e
--- /dev/null
+++ b/doc/forum/help_needed_with_setup:_2_local_computers_and_box.com.mdwn
@@ -0,0 +1,33 @@
+**EDIT: partially solved**
+*by looking around I might have come upon the solution to my own question: the webapp uses a shared cipher for encryption, and since the cipher is stored in the git repository, only the contents will be synced in the encrypted repository (in the cloud in this case). So both computers need to be online to sync, because the cloud only has the content of the files and not the whole annex repository.*
+
+---
+
+Hello everyone,
+
+I need some help with this use-case: two local computers, paired with git annex, also sync in the cloud (box.com) to pull and push changes even when the other local computer is offline.
+
+I've tried the following steps with the webapp, but the result isn't working so far:
+
+1. Create repo in *Computer A* through the webapp.
+2. Create repo in *Computer B* through the webapp.
+3. In *Computer A*, add box.com encrypted repository and put it in the 'backup' group (Just to make sure that it gets everything but I've also tried re-doing the whole procedure with box.com set to 'transfer' (as suggested by the webapp), and still will not work).
+4. Pair computer *A* and *B* over the local network. 
+5. Now also enable box.com in *B* (the cloud repo has appeared thanks to pairing)
+
+So far, when everyone is online, everything syncs correctly. Creating "file1" in *A*, will sync it to all repositories as shown by "git annex whereis file1".
+
+The problem is that this won't work for the following use-case, which I'm currently trying to solve:
+
+(continued from the previous steps)
+
+6. *B* goes offline.
+7. *A* creates a file (or makes a change), which is correctly synced to box.com (*whereis* shows that it's there too). As expected, syncing with B fails because B is offline.
+8. *A* goes offline.
+9. *B* come back online.
+
+The expected behavior here is that B gets the new file (or change) from box.com, since it's been pushed there by *A*, but this doesn't happen. Strangely, the new file doesn't get in *B* until *A* comes back online.
+
+**What am I missing? Should I do something differently to get this behavior?**
+
+Thanks everyone for your help.