I had two repositories, on different machines, created with the assistant, so they were both direct mode.
After pairing each with the other, so that files were merrily flowing back and forth, I happened to do the following: * on machine A, in the dashboard * click on the 'actions' emnu for the repository on machine B * select 'disable'
Result: all references to the repo on machine B have disappeared from the assistant in machine A.
On machine B, I still have the pairing with machine A, and selecting the 'sync now' action seems to be working.
The thing I am curious about is the behaviour on machine A - why is it that I cannot find any reference to it any more in the assistant, so that I can re-enable it?
Syncing seems to work only in one direction.
If I go to machine B and: * change a file * select 'sync now' from the 'actions' menu for machine A the webapp says it worked.
But if I login to machine A and inspect the file I expect to have changed, it is 'not available'.
If I run 'git annex get 'baz.txt' on machine A it complains and asks me to make available the reposiotry on machine B.
Disabling a remote is a weak form of deleting it; the remote repository is left as-is, but the git remote is removed so git-annex won't sync with it, and the webapp won't show it.
I don't know if it makes sense for the webapp to expose this possibility. It seems that it certianly doesn't makes sense to do it without getting confirmation, since to re-enable the repository, the user has to do some probably unknown to them process to set it back up.
In your case, I think that re-doing the pairing process would get them back to how they were.
On consideration, I am going to remove this feature from the webapp UI.