mirror of
https://github.com/databasus/databasus.git
synced 2026-04-06 00:32:03 +02:00
Clarification on Backup Naming Conventions and Encryption Key Requirements #133
Assignees
MrUnknownDE
Clear assignees
MrUnknownDE
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github/databasus#133
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Triskae on 2/16/2026
I have been looking through existing issues and noticed that, currently, backup filenames are not very descriptive. From what I’ve gathered in previous discussions, there might be plans to allow for more "meaningful" or custom naming conventions in the future.
Could you confirm if there is a roadmap or an upcoming task to improve how backups are named? It would be very helpful for organization if the names could be more "human-readable" or descriptive.
I also have a technical question regarding security. My setup is as follows:
All database backups are unencrypted at the application level.
Encryption is handled externally.
Do I still need to backup the encryption key within this system if the backups themselves are unencrypted? I want to ensure I’m not missing a dependency where the system might require a key to restore a backup.