-
Notifications
You must be signed in to change notification settings - Fork 5
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
[Feature Request] A "full checkout" / "full backup" option #111
Comments
Hi! I like that, just wondering if that is not already there with the |
I actually have missed that option 😅 In any case, it got some files in place and I see that the file hierarchy is a bit challenging to understand because it uses indexed hashes which are less of the human friendly type. I do like the This brings to the table the question whether a change of the hierarchy or an additional option ( |
Good :) and thanks for the report! There is an option |
I think the issue #114 would then solve this by allowing to create custom hierarchies. So I'm closing this one. |
Hi,
I've had this idea to use
dsc
in order to make a full backup of the documents in an organized structure that'll represent the structure in Docspell as closely as possible.What I had in mind is something like the following structure:
This could then be extended to include other "metadata" represented in a file directory structure using symlinks.
For example,
by-date
:or
by-tag
: (note how it appears multiple times to represent multiple tags)The main goal for me at least is to have another backup copy independent of Docspell that I can have alongside Docspell backups for any catastrophe situation. Somewhat gloomy but if I'm gone or unable to maintain the Docspell instance anymore, my family would still have access to all the documents through those backups.
What do you think?
The text was updated successfully, but these errors were encountered: