I have been playing around with annex assistent today (way late as I am one of the Kickstarter backers) and found the following puzzling.
I am running a fairly new version, my package manager calls it 4.20130323 (git-annex does not seem to have a --version switch).
I have been playing around with the annex assistent webapp today and have the following questions/observations:
1) The "remote" server creates a bare git repository as far as I can tell, the "local computer" probably does the right thing (but I cannot run it as the "other box" has no X or browser). Is there any way to remotely create a "local" copy (i.e. non-bare git repository, which can later be managed by the cli?) 2) It seems like git-annex-assistent (webapp) binds to localhost, is it possible to let it bind to either a specific ip-address (or all)? (Yes, I understand the security implications, but the use-case is the box from question 2 - i.e. on local network but no X and no browser). 3) what is being launched when I hit "files", on the video it starts a file-manager on my box nothing happens (and no errors as far as I can tell).
Thank you in advance
Svenne
If you want to use the cli for managing the repository, why not
git cloneit using the cli as well? Set up a remote in your existing repository pointing at the repository you cloned, and the assistant will push changes to it. This is all that the webapp would do when creating the repository. The webapp does not set up remote non-bare repositories because unless the user is comfortable with the cli, nothing is going to keep them up-to-date.Setting up the assistant on a headless box is something I need to support better, indeed. I've just now made
git annex webapp --listen=IPlisten on the specified IP address, and output the URL you can connect to from the remote side. Note that this does not yet use HTTPS, so use with caution.It uses the
xdg-openprogram to open a file manager. Ifxdg-openwas not in your PATH, it would instead point the web browser at a file:/// URI as a fallback. If it seems to do nothing, this probably meansxdg-openis in PATH but not working for some reason. Try runningxdg-open /path/to/your/repository