Hello everyone,
my problem is: I have added a Bitbucket gcrypt repository (to be used for metadata only); it works via git-annex sync but the Assistant ignores it completely. I can check from the Bitbucket webpage that the remote repository never gets updated by the Assistant, it only does when i run 'git-annex sync' manually.
Adding the repository:
git remote add bitbucket gcrypt::https://bitbucket.org/omissis/basic.git
Syncing to it is ok:
$ git-annex sync
commit ok
pull bitbucket
gcrypt: Development version -- Repository format MAY CHANGE
gcrypt: Decrypting manifest
[...]
ok
push bitbucket
gcrypt: Development version -- Repository format MAY CHANGE
gcrypt: Decrypting manifest
[...]
ok
But it doesn't appear at all in the Assistant webapp!
Even if I do "restart daemon".
BTW, adding a local gcrypt repo works fine and it gets synced normally by the Assistant (after creating a bare Git repo):
git remote add enc gcrypt::/tmp/enc
My Git-annex version:
$ git-annex version
git-annex version: 5.20140412ubuntu1
Anybody has any idea? My use case is that I have a computer behind a very restrictive firewall (only http and https are allowed) and I don't know how to sync it otherwise. I would like to avoid XMPP. Thanks!
I think this is due to the format of the url. The webapp only supports gcrypt repos that are using ssh uris, or are on local drives.
I think, though that this might only prevent the assistant from displaying the repo in the list of repos. I think it might still sync with it?
Unfortunately the Assistant doesn't sync to the https gcrypt repository at all! E.g. if I add a file, the file gets added to the other repositories (the Assistant syncs it in the background) but it doesn't get added to Bitbucket (https gcrypt). I know that because Bitbucket tells me when the latest change has been made; I can see that no change is reported unless I perform 'git-annex sync' manually.
Well, the file is not uploaded to the bitbucket remote, because bitbucket doesn't support git-annex. Without git-annex-shell on the remote, git-annex cannot send files to it.
Even if it did, it would need to be a ssh transport, not a http transport, since git-annex doesn't upload files over http (except to S3 or webdav remotes).
I think that the assistant also assumes that http transport git remotes are read-only, and doesn't try to push to them. Which might be improvable, perhaps.