So, there actually are two separate questions here:
-
Where to take executables from
-
How to make them accessible from the terminal.
Answer on the first question is here: Releases · gilbertchen/duplicacy · GitHub
It is linked to in the side bar on the main page of this forum. Alternatively, you can build one from sources, link to the how-to is also in the sidebar: Build Duplicacy from source
The easiest way to get golang build environment on a Mac, if you want to go that route, is via MacPorts since most likely you already have them: you literally type sudo port -N install go
and it will bootstrap golang 1.x and then build current golang with that. Then you just execute go get -u github.com/gilbertchen/duplicacy/...
and you will end up with duoplicacy binary under ~/go/bin/duplicacy
Next, answer on the second question: the accepted practice is to place executable into /usr/sbin
. That folder is designated location for “System daemons and system utilities executed by users”, which duplicacy is.
You an either rename the downloaded executable into “duplicacy” and place is there or you can save it into another folder and just create a symlink to it under /usr/sbin/
like so: sudo ln -s ~/Tools/duplicacy_osx_x64_2.0.10 /usr/sbin/duplicacy
, or if you built it yourself - sudo ln -s ~/go/bin/duplicacy /usr/sbin/duplicacy
Then you can just call duplicacy
directly since default `$PATH$ contains that folder.
Furthermore, if you want to setup unattended backup by schedule using native macOS scheduler - this post might help: Mac/OS X launchd example
I’m not sure I understand your question so if I missed the point please feel free to ask further questions, I’ll elaborate.