I’m slowly designing my new backup system based on duplicacy.
- All my data are stored on my QNAP NAS. (home folders, Shared folders)
- I plan to use Onedrive as remote storage.
- Quite a few directories are synched on mas NAS and on my mac desktops thanks to syncthing.
- I Heavily rely on Docker for deploying additional capabilities on my NAS.
- I do not want the .duplicacy directory being replicated on all the partners computers of synching
- Moreover I’d like the container having only read only access to the repository while doing the back ups.
I though about creating the repository on the NAS and add a symbolic link to the real directory to back up, but due to the Volume mapping of docker, I doubt following symbolic links inside the container would be OK.
For those reasons, I’d like to be able to store the .duplicacy directory outside of the repository.
- Is there a way to to it without modifying the duplicacy-cli source code ?
Else I though about the forking ducplicacy-cli and preparing a pull request with
- a new string parameter valid to all the subcommands eg: -confdir absolute_path
- Patching the getRepositoryPreference function in src/main/duplicacy_main.go to use the -confdir value instead of looking inside the current directory all the way up in the path hierarchy
- Alternatively, keeping the .duplicacy directory inside the repository but put a config file in it redirecting to another path elsewhere… ( more robust in case of forgetting the -confdir parameter)
Any comments ?
Is there any interest beside me to add this extra feature ?
Thanks for your time reading me