Is it possible to add the hash database to the hashed remote? And exclude it from the hasher view.
It can be useful when you use the remote from different places or is used by different people
And add an ‘all’ option to the hashes saved. If I have to calculate and save a hash, why not do it with all hashes? It isn’t expensive
Isn’t pre-seeding exactly what you are after?
It’s a little different: if I save the full .bolt file I can use any hash stored instead the one in the command. And if the hash isn’t stored, the hasher will calculate all the hashes in the config and save them into the file
I’m asking for something like this when I send a command:
rclone copy -u MyHasher:rclone_hasher.bolt ./cache/kv/MyHasher~hasher.bolt
do actual command here
rclone copy -u ./cache/kv/MyHasher~hasher.bolt MyHasher:rclone_hasher.bolt
The rclone has to know where the cache is located locally and the hasher remote name for the local file name. The file name in the remote is better to leave it always the same, we only need one.
Maybe is good if the hasher remote has always --exclude /rclone_hasher.bolt