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
In a config with a source like /path/to/a/directory/ the resulting archive will also contain a fully qualified path to that exact same directory.
There should be a config variable to enable relative paths. That way the archive would only contain e.g. the name of the backup source directory instead of the whole absolute path.
In the above case, the archive would contain only one dir called directory instead of path/to/a/directory on the root level.
Issue with multiple sources
When using multiple sources and some of the 'relative' paths are the same
.
├── another
│ └── path
│ └── to
│ └── another
│ └── directory
└── path
└── to
└── a
└── directory
In the above example we got 2x "directory" as relative source paths. What should happen to those? Put them into the same dir? Use directory and directory1 etc.?
The text was updated successfully, but these errors were encountered:
In a config with a source like
/path/to/a/directory/
the resulting archive will also contain a fully qualified path to that exact same directory.There should be a config variable to enable relative paths. That way the archive would only contain e.g. the name of the backup source directory instead of the whole absolute path.
In the above case, the archive would contain only one dir called
directory
instead ofpath/to/a/directory
on the root level.Issue with multiple sources
When using multiple sources and some of the 'relative' paths are the same
In the above example we got 2x "directory" as relative source paths. What should happen to those? Put them into the same dir? Use
directory
anddirectory1
etc.?The text was updated successfully, but these errors were encountered: