You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Specifying folder without /**/* backups only this folder and not any of its content, but this is useless and inconsistent with the fact that when glob isn't specified, the source is backed up recursively.
More?
Requirements of the new implementation
Relative paths works properly.
You don't need to specify nested folders separately.
When specifying folder, it's content included recursively (but you can specify this explicitly, so "a" == "a/**/*").
If a file/subfolder is specified separately, it takes precedence over the specified parent folder, regardless of its position in the list.
It's possible to include only files, but not subfolders, like
glob = [
"a/*",
"!a/**/*"
]
or
glob = [
"a/*",
"!a/**/"
]
or even just
glob = [
"a/*"
]
More?
Why new implementation?
I'm not sure that walkdir can give such flexibility.
Backward compatibility
TODO
The text was updated successfully, but these errors were encountered:
I wrote a workaround for this for nix configuration. Link to lines where main work done. Basic idea:
For files and directories add additional nesting directories, like:
For source /home/user and file /home/user/.config/rustic/rustic.toml (specified as (dir ".config/rustic/rustic.toml")) also add directories
/home/user/.config
/home/user/.config/rustic
For folders in include additionally append /**/* to full directory
Current limitations
Tested on rustic v0.7.0
You should specify nested folders separately, e.g.
File matching is affected by order of the glob patterns in config, but should be based on globs precedence. For example, this excludes
a/b.txt
:but this don't:
Relative paths don't match files, only folders, e.g. this won't backup files, only folders:
Specifying folder without
/**/*
backups only this folder and not any of its content, but this is useless and inconsistent with the fact that whenglob
isn't specified, the source is backed up recursively.More?
Requirements of the new implementation
Relative paths works properly.
You don't need to specify nested folders separately.
When specifying folder, it's content included recursively (but you can specify this explicitly, so
"a" == "a/**/*"
).If a file/subfolder is specified separately, it takes precedence over the specified parent folder, regardless of its position in the list.
It's possible to include only files, but not subfolders, like
or
or even just
More?
Why new implementation?
I'm not sure that walkdir can give such flexibility.
Backward compatibility
TODO
The text was updated successfully, but these errors were encountered: