Open weak-head opened 3 months ago
Consider alternative approach with a template path for a destination:
commands:
backup:
destination: "/mnt/backups/{group}/{folder_name}/{folder_name}_{datetime}.{ext}"
archive: rar_protected
upload: aws_archival
directories:
apps:
- /mnt/ssd/apps/plex
media:
- /mnt/hdd/music
photos:
- directory: /mnt/hdd/photos/2024
destination: "/mnt/backups/photos/{folder_name}.{ext}"
Description
For some particular use cases we need to support different rules for custom backup and upload key naming.
Changes
As an option, replace the way how destination path is composed. Right now, the following method is used:
It should be replaced with a Strategy that is injected into Backup command.
The possible extension could include a configurable smart Strategy per a particular backup entry.
Proposed changes to the config:
Simplified short:
Expanded complete: