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
Use .nobackup by default, if no other exclusions set #314
Comments
Hi all --- Run into this issue today when I tried to backup with a .nobackup file in an early directory in the backup process without success. After finding this post, I was able to tag the directory with an .exclude file and it worked just fine. Thanks for the post! |
I am actually a little irritated by the (new) placeholders texts as well. |
Yeah, that would probably be better. |
macOS uses file attributes and folder lists, not
Hope this clarifies it. If you have better placeholders, please let me know by tomorrow, so I can merge the next PR. Thanks! |
My last comment was probably posted too early. I completed it. I had noticed your comparisons with the documentaries of Borg and Borgmatic. But I wonder if it doesn't take a lot of technical knowledge to understand these options. And whether it needs examples that are closer to everyday life. Hence my reference to Déjà Dup Backups. |
The issue with your Deja Dup comparison is that one can only add folders, not expressions that apply to many files and folders. So the current field may be confusing to some, but offers more power and reflects the functionality provided by Borg. I use it to e.g. exclude all video files across many project folders. Instead of .nobackup, we could also use .gitignore, which is very familiar. Or both. |
Thanks for the clarity! Then I think it would be good if there were examples for folders/files as well as for patterns. Then you can see the whole range of Borg. How do you feel about that? Or is it not Borg's idea that at this point folders should also be excluded? Exactly, It's also a question of Vorta's target user group, isn't it? |
Still not clear to me then: Do we need the split screen in Vorta at this point? |
The two bottom fields do different things and cant be combined. For further discussion on exclusion patters, please see here: #399 |
Is your feature request related to a problem? Please describe.
Without user action, Vorta will show
.nobackup
under the sources tab, suggesting that this is the default. In reality, we don't exclude anything unless the user adds his own settings in that field.This lead to some confusion, where the functionality was expected:
Describe the solution you'd like
.nobackup
file when the user doesn't change the field.E.g. .nobackup
The text was updated successfully, but these errors were encountered: