When I installed duplicacy web on my home server (debian/ OMV), it took me several tries before I got it to work. I think part of the reason was that before using the web-ui, I was already running the cli version and I confused about how the two relate (I learned that they are completely separate) but also where exactly the web-ui creates its local cache, preferences and filters files etc. Eventually it worked, but left behind a number of duplicacy paths which I probably can delete.
The question is: which ones can I delete? What’s a safe way of checking that?
Here are some of the paths I see:
/.duplicacy-web/repositories/localhost/all/.duplicacy/cache
/tmp/.duplicacy-web/repositories/localhost/all/.duplicacy/cache/
/zfs/NAS/duplicacy/duplicacy-web/repositories/localhost/0/.duplicacy/cache /zfs/NAS/duplicacy/duplicacy-web/repositories/localhost/all/.duplicacy/cache
/zfs/NAS/duplicacy/server/cache/
/root/duplicacy_linux_x64_2.7.0
/root/.duplicacy-web/bin/duplicacy_linux_x64_2.6.2
/.duplicacy-web/bin/duplicacy_linux_x64_2.7.2
/zfs/NAS/config/homedirs/christoph/.duplicacy-web/bin/duplicacy_linux_x64_2.6.1
In /usr/bin
I also have
lrwxrwxrwx 1 root root 29 Sep 30 2020 duplicacy-web -> duplicacy_web_linux_x64_1.4.1
-rwxr-xr-x 1 christoph users 31359571 Apr 16 2020 duplicacy-web-1.3.0
-rwxr-xr-x 1 root root 31436080 Aug 23 2020 duplicacy_web_linux_x64_1.4.1
And in /usr/bin
I have
lrwxrwxrwx 1 root root 29 Sep 30 2020 duplicacy-web -> duplicacy_web_linux_x64_1.4.1
-rwxr-xr-x 1 christoph users 31359571 Apr 16 2020 duplicacy-web-1.3.0
-rwxr-xr-x 1 root root 31436080 Aug 23 2020 duplicacy_web_linux_x64_1.4.1
It looks to me as if my current install is in /.duplicacy-web/
so that I could delete all the other duplicacy paths and symlinks. Does that sound reasonable?