mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Added a comment: use case

Browse source
This commit is contained in:
andrew 2018-05-23 00:12:11 +00:00 • committed by admin
parent f7a474124b
commit 078e41f02e
1 changed files with 20 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

20
doc/forum/Dealing_with_crippled_Android_file_system/comment_1_1b17852211108d9ab4d3959d7f57a9df._comment Normal file
View file

@ -0,0 +1,20 @@
[[!comment format=mdwn
username="andrew"
avatar="http://cdn.libravatar.org/avatar/acc0ece1eedf07dd9631e7d7d343c435"
subject="use case"
date="2018-05-23T00:12:11Z"
content="""
Hmmm. Could you talk more about your use case “The use case I have in mind is syncing photos to an Android tablet in a v5 repository.”?
Lets say I have a nice collection of family photos on my desktop computer annexed in a folder called `family`. Lets say we have `numcopies` set at 1. I keep only the best photos, so it always takes up about 1gb. In the family folder I have nice organized sub-folders and I add new images occasionally. I have an Android tablet that sits on my coffee table and I want visitors to be able to open the tablet, run some gallery app and view all my family photos. Sometimes i'll grab the tablet and take it with me to family gatherings, so I want all the photos on in, ready for offline viewing.
With this use case, perhaps I run assistant inside termux. I clone family into `/data/data/com.termux/files/home` set it as standard group transfer and call it `t`, I also clone it into `/storage/emulated/0`, set it as standard group client, and call this crippled client repo `c`. Our `c` folder should now be accessible to any Android photo gallery app. As we make changes to `family`, on our desktop, assistant on the Android tablet brings them in, when we have wifi, it will probably copy them directly to `c`?
If I take a photo on my tablet, put it in the `c` directory (which is accessible from my photo app), then this photo should be copied directly to family (if I have wifi). If I don't have have wifi, this photo should be immediately copied to `t` in which case I have two copies of the file on my tablet (I think)? If I delete the photo from the crippled filesystem `c` I still have the one that was already copied to `t`. If I re-connect to wifi, perhaps the photo will get sent to `family` from `t`. It might stay in `t` since it is missing from `c`, not sure how this would work (but anyhow, see archive folders in the next paragraph).
Maybe I want to save some space on my tablet (deleting from photo app might work?, but archiving is more likely to work). So I open up my photo app, browse to my `c` folder and start putting a bunch of files in a sub-folder named `archive`. They are then immediately deleted from my tablet (unless they were never synced to `family` in which case I have two copies of them, so I would still have a copy sitting in transfer `t`). If I archive files when I have no wifi, presumably they will just get moved to `t` by assistant since git-annex cannot verify the copy at `family`?
Would something like that work for your use case? I don't actually use Android termux, so I am sure others might have some insight into use of the various directories.
—Andrew
"""]]