zlacker

>>tosh+(OP)
My usecase for Termux: most pictures get backed up properly into the home NAS, but the sync process sometimes skips a few [1] (which is exasperating, but here we are still not migrated to Immich).

So I have a python script in the NAS that calculates the MD5 checksum of every photo and video, and generates a shell script that, when executed on the phone, will calculate the MD5 on the local device, and delete if it is equal to the NAS.

The generated shell script gets sent to the phone, then I execute it from within a Termux window, pointing at the DCIM folder.

I can free up tens of GB of memories with reliability in the face of a misbehaving sync algorithm.

[1] https://help.nextcloud.com/t/auto-upload-is-skipping-random-...

>>Rygian+Qi
With Termux I have rsync at hand, which can compute checksums, delete files after the transfer, etc. That's why I do my complete backup with Termux. And I sort the images on the phone into dated subfolders before syncing them.

And having tools like exiftool, ffmpeg, and ImageMagick among others available in Termux is wonderful.

>>jcynix+Fp
Yeah same in fact that's how I discovered Termux. I had an rsync.net account and thought that since rsync and ssh are so ubiquitous it should be simple to set up back-ups from my android phone. Boy was I wrong. The android apps that support rsync were all janky or suspiciously closed. Termux + rsync + Termux API's job scheduler does the trick. I think it's a bit of a drain on my phone battery but I won't complain given I own my photo back-ups from top to bottom (though I rent from rsync.net)