-
-
Notifications
You must be signed in to change notification settings - Fork 34
introduce a "base dir" option #183
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Makes sense. Could simplify the creation of reusable profiles, when relative paths can be used in source and the base is configured separately. |
@jkellerer Thanks for implementing this. Hope it will be merged soon :-). This option is important. |
@jkellerer I tested this pull request now. In case anybody else want to test it. Install git and go, then run
It works! Thanks for your code! But I have one wish. It seems not possible to set the base-dir on "command level" as well. But I would prefer to set the base-dir just for the backup command, because in most cases it is only necessary there. And then one question. If you do
where should resticprofile restore to if base-dir is set to '/' In my opinion it should be /tmp, but it is for some reason '/' That's why I would prefer to have an option to set the base-dir on command level. This would allow me to run restore without a base-dir. |
Thanks a lot for testing it. That is very good feedback. In the current form Will update the PR to add a separate option to set a base just for backup sources. |
Thanks! I will test when it is ready. |
Thanks for your PR! Just to clarify, did you add an option to set a base just for backup sources? |
Yes, there are 2 options, |
Thanks! Will test when 0.23 is available. |
Currently, resticprofile runs from the current directory that you are in when you run it. I was thinking that there could be a "base-dir" option that would set the directory that resticprofile runs from. If this option were implemented then you could run resticprofile from any directory and the backup would still work, since the backup (source option) could then be relative to the base-dir.
The text was updated successfully, but these errors were encountered: