Create data folder on your box remote - rclone mkdir box_remote:data - it is better to keep data in specific folder rather than in root.
filename_encoding = base32768 option in crypt provides most space efficient file names encoding. Unlike e.g. Google, Box has much lower limits here and without this option it is very easy to get into "path too long" situation during data migration and crypt default base32 encoding.
Adjust chunk_size accordingly to your box account limits, e.g.: 4G, 14G, 49G
hash_type = sha1all option enables SHA1 hashes inside crypt/chunker combo which is very handy for content verification. Normal crypt check won't work as files are chunked. Downside is that extra json metadata file is created for every file. Normally only for chunked ones. If you have many big files it comes effectively at no cost. But if you have many small files it will result in double number of files in box_remote:. I am not aware of any limitations here though.
Always access your Box setup using chunker_remote, e.g.:
Do you have any tips for any rclone mount flags that can/should be used with Box to improve performance? It seems a little slower than Google Drive was for me when using the mount point to access files. Right now I'm just mounting without any flags.
Keep things as simple as possible. Use VFS full cache mode + cache pre-warming for best experience. I do not think you can do much to improve speed of mount on BOX. You could start new thread "recommended mount options for BOX" - maybe others have some useful tips.
this thread is about remotes' setup - and I'm happy for any comment and ideas - for mount I do suggest you open new thread.
Mixing every aspect of BOX in one thread does not make it easy to find anything.
I look at BOX purely as a storage option - I have no idea about plex (never used it) or any software operating on it - it is very different subject. mount for Plex might need different tweaking than Adobe rendering or ML software.
My only purpose here is to show how to use crypt and chunker to overcome BOX limitations.
⣛伔▢⤞ᣃተ - or aliens:) it is interesting set of characters used indeed - even if at the first look it looks like chinese it is not:) We tested every single character - and however unbelievably scary it looks it works perfectly.
only best practice and attempt to avoid any issues. root folder often is treated in special way by cloud providers - e.g. they put there some their solution specific objects like shared folders etc. I did not do any research on it with regards to box. No time and no reason. This approach is purely based on play safe tactic:) You can try crypt root folder of course. And share your findings.
I think some structured approach in data storage always helps. I have my crypt data in data_crypt folder. Then I can have different data in data1_crypt folder - different passwords etc. Could I have it all in one folder? Yes. But then I take a risk that I hit some edge cases of any software (rclone here) not working 100% to spec in extreme situations. So as lazy as I am I use separate folders:) Then I do not have to bother people on the forum with questions about missing data:)
Hey @kapitainsky why do you use sha1all and not sha1. Box supports sha1 checksums, so we can use sha1 to keeps hashes for composite files and falls back to the wrapped remote hash for non-chunked ones, rclone docs advise to choose the same hash type as supported by wrapped remote so that your file listings look coherent.
You are right that Box supports sha1 and your logic is correct but does not take into account crypt remote. So the way how you describe it would only work with this setup:
Crypt does not support any hashes. It could be theoretically implemented but is not. My workaround here is to utilize chunker capability to generate and store hashes for all files.
If you do not need it then you can use sha1 option - but then you will have hashes only for chunked files.
The downside of using sha1all is slower upload of small files (for every file another side-car json file has to be created). You have to decide based on your usage patters. If you constantly write tones of small files then maybe it is not worth. I use cloud as my backup storage and after initial upload (and I accept that instead of 1 day it might take 2 days) subsequent uploads are relatively small. Advantage is that I have very reliable way to verify my local files vs files stored in the cloud.
Kap - do you have recommendation for how to mount the rclone mount on your filesystem? I've been using an rclone_vsf.service to mount google drive, but using the same settings for box.com is unreliable (very very slow to update). If I use rclone move or sync to copy files to the mount (as you recommend - chunker_remote:), the files copy and I can see their obfuscated names in the box.com web interface, but on my file system looking in the directory I've mounted the rclone box.com mount to, I don't see anything. Looking for help!