-
Notifications
You must be signed in to change notification settings - Fork 481
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
[Enhancement]: Modify path of backups #2973
Comments
Duplicate of #199 but this uses the new issue format and looks nicer :) |
Amazing that I'm just finding this right now and the request is so new! I'm currently moving ABS from Docker to an LXC and I'm having a hard time linking it to my standard services backup share. Either changing it from within the app or allowing it to be set in the config file at /etc/default/audiobookshelf would be amazing. Thank you all for your effort! |
As I'm running ABS as a Docker container on TrueNAS Scale. I just set up a mapping from /metadata/backups to my backups folder. That folder is then uploaded nightly to a off-site backup. |
I made an update so that the backup path can be overridden with an environment variable BACKUP_PATH. It is now stored in server settings so that we can eventually make the path editable in the UI. That may not make it in the next release so for anyone that wants to modify it now will be able to pass in the env variable. |
Thank you so much for that change! I just tried an LXC where I edited the audiobookshelf config file at /etc/default/audiobookshelf to include BACKUP_PATH. As that didn't work yet, I'm assuming I'll need to wait for the next release after 2.10.1? Again, thank you so much for this quality of life upgrade, I really appreciate it! |
Yes, you'll need to either way for the next release, build form source, or use the |
- Added api endpoint PATCH /api/backups/path - Cleanup backup page UI for mobile screens
…CKUP_PATH env variable advplyr#2973
- Added api endpoint PATCH /api/backups/path - Cleanup backup page UI for mobile screens
Added in v2.11.0 |
Type of Enhancement
Web Interface/Frontend
Describe the Feature/Enhancement
The target for where the backups are located is on the same volume where the application is installed
Best practice for backups is to put them on a volume other than where you are running the application or where the dataset is located. While it is possible for me to symlink a location to where my backup drive it, the better option is to allow the path to be modified.
As a temp work around document where the pathing is stored. I'm assuming it is in a config file somewhere.
Why would this be helpful?
Adhering to best practices for backups. As in the event of the drive where the app is stored you would also lose the backup.
Allowing the changing of the path to another drive would allow for better data protection.
Future Implementation (Screenshot)
Audiobookshelf Server Version
v2.9.0
Current Implementation (Screenshot)
No response
The text was updated successfully, but these errors were encountered: