How do I sync files from mobile to a repo?

I have a local repo on a computer with some folder on the path /computer1/annex/

Then I tried to run git annex on my phone and added a remote ssh repo syncing to /computer1/annex/mobile/ from my mobile's picture folder.

But the files ending up there are: ls /computer1/annex/mobile/ annex branches config description HEAD hooks info objects refs

I chose "full backup"

Why dont I see my pictures there, even if they are hiding in the metadata ?

RSS Atom

addition

I understand that the copy of the cellphones' photos are stored on the server too, when typing git annex whereis I see that it exists on the server, but I need to be able to, at will copy out the jpg files for editing and using in other places.

Comment by Petter_petterson — Sat Sep 13 07:54:58 2014

Remove comment

comment 2

If /computer1/annex/ was already an annex repository you should have synced the phone to that, not to a new bare repository at /computer1/annex/mobile/

Comment by Justin — Sun Sep 14 18:57:12 2014

Remove comment

comment 3

Thanks Justin, but that wont work. Even pointing out a normal, non-bare repo and then adding it as a ssh remote will convert it into a bare repo. I confirmed that, and then I read this post:

http://git-annex.branchable.com/forum/Local_and_remote_in_direct_mode/

that states that

The "Remote server using ssh" option in the webapp is intended to set up a bare git repository on a server, not a non-bare git repository on a client."

I even tried to do git remote add B ssh://machineB:/~/annex but to no avail, the created annex on machine B becomes a bare repo.

The only way to do it for me was to do the following, Assume my cellphone is device A, and my desktop is device B:

On machine B:

cd ~/DCIM
git init
git annex init "B"
git annex direct
echo '*/5 * * * * * cd ~/DCIM; git annex sync' > crontab

On machine A:

git clone ssh://user@machineB:/home/user/DCIM
git annex sync
git annex webapp

now pictures are synced to the computer in direct, non-bare format every 5 minutes. I have spent literally days on this and now I finally nailed it in a crude but working fashion.

Comment by Petter_petterson — Tue Sep 16 08:13:59 2014

Remove comment

comment 4

I have double-checked, and when I already have an existing, non-bare repository, pointing the webapp at it over ssh keeps it as a non-bare repository. As I would expect.

I even tried to do git remote add B ssh://machineB:/~/annex but to no avail, the created annex on machine B becomes a bare repo.

I didn't try this because it's such a violation of the way git actually works that I just can't believe it could happen. If it does, you've found the git bug of the year.

But, I think you just got confused about whether the repository existed before, or gave the wrong path to the existing repository which would result in a new, bare repository being created in the location you told it.

If you really think this happens, show a transcript with enough details for me, or the git developers, to reproduce the problem.

Comment by joeyh.name — Thu Sep 18 18:00:42 2014

Remove comment

comment 5

It occurs to me that another way you could have gotten confused is, if ssh://machineB:/~/annex was eg, created in the first place by running the git-annex webapp on machineB, then it would be a direct mode repo. In this case, yes core.bare=true, but so does annex.direct=true. And that repository will not be a bare repo really; it will contain the same file tree as you have on your mobile.

Comment by joeyh.name — Thu Sep 18 18:05:33 2014

Remove comment

Add a comment