I have a server with multiple VMs. Each one of them has a different service running on it but what all of them have in common is: they backup some data of the service they are running to an encrypted remote.
The challenge I'm facing is that I end up with multiple rclone.conf files, one per VM, meaning that when I change one of them, I have to change the rest of them manually, one by one.
How do you guys keep an rclone.conf that is the source of truth, meaning the file where all the configs are, and then sync that one to all the different destinations, in this case, my VMs?
Also, extra bonus question. Do you keep only one crypt remote with different different directories in it (1) or you have a different crypt per directory (2)? What's your preferred and why?
(1)
remote:
config remote:
encrypted_remote:
remote = remote:
usage:
rclone sync local encrypted_remote:VM1
rclone sync local encrypted_remote:VM2
Yup, that was an idea, but then we factor in I also use rclone in my laptop which is not connected to this host... And then another computer...
In regards to the bonus extra question, I've been using (2) as I thought it's a way to increase security. But if somebody manages to decrypt the content of one remote, I don't think decrypting the content of the other remotes will be difficult anymore. Just a nuisance, I guess. Both passwords and salt contain more than 50 characters, but technology advances fast.