forum/Local and remote in direct modegit-annexhttp://git-annex.branchable.com/forum/Local_and_remote_in_direct_mode/git-annexikiwiki2014-09-18T17:55:21Zcomment 1http://git-annex.branchable.com/forum/Local_and_remote_in_direct_mode/comment_1_45f89ebcb6092d1b2582feebc8a5e9d7/joey2013-11-27T22:47:37Z2013-03-19T18:05:58Z
<p>The "Remote server using ssh" option in the webapp is intended to set up a bare git repository on a server, not a non-bare git repository on a client.</p>
<p>For what you want, both your computers need to be running the git-annex assistant.</p>
<ul>
<li>If the computers are on the same network, pick the "Local computer" option on one to start a pairing process with the other.</li>
<li>If the computers are not on the same network, but can (apparently) access one-another by ssh, then you're a lucky guy. <img src="http://git-annex.branchable.com/smileys/smile.png" alt=":)" /> But the webapp doesn't cater to this unusual configuration (unless the local pairing option above works). All you need to do though, it manually add a git remote on each that points to the already existing, git-annex assistant managed repository on the other. Eg: <code>git remote add B ssh://machineB:/~/annex</code></li>
<li>If the computers are not on the same network, and cannot access each other directly using ssh, you will need
to use the XMPP option, and a transfer remote that both can access.</li>
</ul>
comment 2http://git-annex.branchable.com/forum/Local_and_remote_in_direct_mode/comment_2_90eeb2bffdb2db8032f9a0eac630ed56/Petter_petterson2014-09-16T08:15:05Z2014-09-16T08:15:05Z
Doing git remote add B ssh://machineB:/~/annex still makes the repository on machineB a bare one, just try it and check git config -l | grep core.bare...
comment 3http://git-annex.branchable.com/forum/Local_and_remote_in_direct_mode/comment_3_859ec2b3a8e938073b2099fdc5781109/joeyh.name2014-09-18T17:55:21Z2014-09-18T17:55:21Z
Petter_petterson, I think you're mistaken about that. If you were right, that would be a massive bug in git -- nothing git-annex specific about that command after all.