Mirror of the Rel4tion website/wiki source, view at <http://rel4tion.org>
Clone
HTTPS:
git clone https://vervis.peers.community/repos/yEzqv
SSH:
git clone USERNAME@vervis.peers.community:yEzqv
Branches
Tags
unison.mdwn
looks like unison-gtk is enough, but I’m not sure the same is true for the server - will need to check.
The idea: Have a new user ‘unison’ in the sshuser group and a /bin/false shell (at least it should have - see how I made the git user, for whom ssh shell is not allowed), and whose home directory will be used with unison. It’s important that this user cannot access anything but its homedir - maybe it’s time to make my home folder not work-readable. Or maybe use a chroot…
Another idea, just read on the internet some unison tutorials. I’m sure people found good solutions.
Then I need to put my public key on that “server” so that it trusts me and lets me login. It probably should be under /home/unison/.ssh - just read about it and see. Then I can sync files.
Note that the path may default to the same, e.g. my folder /home/fr33domlover/x/y/z will sync to /home/unison/x/y/z, i.e. the same path. It’s not necessarily the right thing. I need to try and see.
Then, how does collaboration work? I’ll need the unison user to also accept some additional keys. I can e.g. see in /home/git how gitolite stores the keys in a way ssh can see them. Probably somewhere under the .ssh dir.
GENERAL IMPRESSION: It’s cool for the power, but it’s not exactly made for real world personal user like Sparkleshare. I’m not sure I’ll use it if I don’t discover it’s a bit smarter, at least the GUI.