-
Notifications
You must be signed in to change notification settings - Fork 11
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
Document difference in CLI options rustic vs. restic (was: rustic does not support restic's -H
for --host
)
#6
Comments
There is no Also, there is no Note that you can define global snapshot filters in the config file, e.g.
If you like, I can also add support for env variables to filter snapshots... |
Maybe we are speaking past each other. I am referring to the following flag.
I have assumed it corresponds to rustic's
|
And btw: Thank you for your awesome support. |
Ah, sorry. Didn't realize there is another You are right, |
I can tell that restic's UI is confusing. Is flag-to-flag compatibility not a goal? If not, I'll propose a PR with some documentation regarding incompatible flags. |
No, acutally the goal is to stay repository-compatible. This means a restic repo should be always processable by rustic and vice versa. I like people being able to switch software at any time because having choice of the software increases the reliability to work with the data and this IMO is important for a backup software.
That would be awsome! There is actually rustic-rs/rustic#302 open but so far I got too much "distracted" with improving the rustic codebase... |
As far as i analyze the situation, there's no goal for command-line compatibility. @ibotty I'd be interested in a flag match table. |
I'll see whether I can write some script that compares the flags and submit a small document. The documentation issue is too big for me to handle atm. I usually also prefer writing code to documentation 🙃. |
@ibotty By pointing to the docu I actually just thought that your comparison would very much fit into it. But we can start with having it documented and once there is more docu try to put it in the right structure.
Nitpicking: It actually becomes |
-H
for --host
-H
for --host
)
No description provided.
The text was updated successfully, but these errors were encountered: