Description
Currently #1 exposes git-annex-shell to the ssh environment that ./gitea serv presents to clients.
This is enough to make work
git clone [email protected]:some/repo.git
cd repo
git annex get .
But this fails:
git clone https://data.example.com/some/repo.git
cd repo
git annex get .
So, this is fine for data curators and data collaborators, but it is not fine for downstream users trying to use our open access data.
It also means that the prototype we built over in https://github.com/neuropoly/computers/issues/167 that uses DroneCI is broken. Drone clones over https -- passing itself an HTTP Bearer token in lieu of adding an extra ssh user.
There are some instructions on how to make this work with git-annex, and a live repo that functions this way at https://downloads.kitenet.net/.git/.
Implement this into #1.
Also, make sure to respect access control. That demo is meant as a public repo, so there's no access control deployed -- it literally just exposes the .git/ folder, including .git/annex, to the whole web, using Apache -- so we need to instead layer Gitea's auth system and Gitea's built in web-server in. The use-case I have in mind is only our own public repos, but I don't want to do a half-job where security is involved.