Mikrotik backup script | simple bash script for doing encrypted backups of mikrotik devices(Routeros) via ssh. Script will do password-protected binary and encrypted with openssl export on regular basis
MIT License
25
stars
12
forks
source link
Feature Request: Implement Tagging System for Backups with Configurable Option #12
an enhancement for the project that I believe could significantly improve the manageability and organization of backups. It would be beneficial to introduce a tagging system for backups, allowing users to assign custom names or identifiers to their backups. This feature could serve as a way to easily distinguish and manage backups over time.
The idea is to implement this functionality as an additional option in the configuration settings, where users can specify a tag for each backup operation. By default, this feature could be disabled (i.e., no tag is assigned), ensuring backward compatibility and not imposing any changes on users who may not need this functionality.
The end implementation could be as straightforward as creating a symbolic link (symlink) on the file system that points to the actual backup file. This symlink would be named after the tag, providing a user-friendly way to access and identify backups based on their designated tags.
Implementing such a feature could enhance the user experience by providing more flexibility in organizing and retrieving backups, especially in environments where backups are frequent and need to be categorized or identified quickly.
an enhancement for the project that I believe could significantly improve the manageability and organization of backups. It would be beneficial to introduce a tagging system for backups, allowing users to assign custom names or identifiers to their backups. This feature could serve as a way to easily distinguish and manage backups over time.
The idea is to implement this functionality as an additional option in the configuration settings, where users can specify a tag for each backup operation. By default, this feature could be disabled (i.e., no tag is assigned), ensuring backward compatibility and not imposing any changes on users who may not need this functionality.
The end implementation could be as straightforward as creating a symbolic link (symlink) on the file system that points to the actual backup file. This symlink would be named after the tag, providing a user-friendly way to access and identify backups based on their designated tags.
Implementing such a feature could enhance the user experience by providing more flexibility in organizing and retrieving backups, especially in environments where backups are frequent and need to be categorized or identified quickly.