For the workshop I'll host on Saturday I'm still wondering how to make a quick'n'dirty publicly accessible git-annex repo where all participants can just push and pull and do git annex stuff with.
Options:
- Use one of my servers, make a new user, add all of the participants' ssh keys (works)
- Make a https/git protocol git server without auth (no annex possible, right?)
- Use the assistant to set up local pairing and have it do the key setup (should work, though I don't know if it's reliable in that uni WiFi)
Any more ideas?
Maybe a bare git repo on a nfs or smb share? I'm not sure if concurrent pushes work right with that.
It's probably also a good idea to set
git annex config --set annex.dotfiles true, so no one gets into a situation where they have to resolve a merge conflict manually.😂 That kinda defeats the purpose of teaching git-annex, doesn't it?
You can use https and have an annex in the repo, but it will be read-only.
In a classroom setting,
git-annex multicastcan sometimes be useful. You'd still need a publically writable git repository hosted somewhere.I'd use ssh though, and automate the key enrollment.
Turns out, both WiFi networks here disallow broadcasting, so the local pairing of the webapp doesn't work. Just tried it with two laptops, the pairing request is never shown.
So the server solution with SSH keys it is, then!