search

creativeprojects / resticprofile

Configuration profiles manager and scheduler for restic backup
https://creativeprojects.github.io/resticprofile/
GNU General Public License v3.0
713 stars 33 forks source link

`restic-binary` should be honored in profiles #202

Open Gaibhne opened 1 year ago

Gaibhne commented 1 year ago

Yesterday, I opened a silly issue because I didn't read the documentation correctly (#198), but that got me thinking - I would think that kind of setting really SHOULD be honored by profiles. My plan was to create one global config for all my Windows and Linux machines, where I could have global/default settings for repository location, forget rules and such, and specific profiles for the separate machines.

But that will not work if I can set only a single global restic-binary that is valid for all machines using the config, which really doesn't make much sense if you think about it. I couldn't even set different restic binaries for different profiles on the same machine, like having different versions for different repos, or binaries with different suid bits/settings for different users.

So I guess this is a feature requestion for letting us overwrite/specify the binary in profiles.

creativeprojects commented 1 year ago

I didn't think it would be useful at the time, but now I can see how it can be in some cases.

It's not a big change.

In the meantime, you know resticprofile is usually doing a good job at finding the restic binary without help. And if it's in a funny location, you can still add it to the %PATH% 😉

Gaibhne commented 1 year ago

The winget installed version of restic was only added to the superusers path, for some reason, which is how I stumbled across the topic in the first place. I probably wouldn't HAVE to run resticprofile as a user, but typically I would think if I wanted to say, check snapshots, I wouldn't bother to do it as a superuser. Still, as you said, not that hard to add to the path manually.

toofunkybeats commented 11 months ago

I could add another use case - a few things I plan to backup with resticprofile are living in docker volumes, so in order to get to them I need to replace restic-binary with a call to docker run restic/restic.

Either that or find a way to expose the volumes to the host in a controlled manner, which AFAICS is not easily possible.

But it's not a showstopper - I can just keep a completely seperate configuration for docker volumes, which is totally fine for me.