-
-
Notifications
You must be signed in to change notification settings - Fork 0
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 - Backup before update flag #13
Comments
Thanks for the suggestion @slimninja. Maybe we can come at this from a different angle though, and look to implement a ./bookstack-system-cli check-update && ./bookstack-system-cli backup backups/ && ./bookstack-system-cli update |
That's a great idea, and solves my initial problem as well. Reduces overlap as well |
Hi. First of all, great work on everything. I've been using Bookstack since about 2017 with very few issues :)
I currently run a script monthly via cron that:
With system-cli, life is a little easier, and I can run something along the lines of this every month:
However, this means that regardless of whether there's a bookstack update available or not, my instance is backed up.
Ideally I would be able to run something like below, where If I provide a flag, e.g. --backup, bookstack would backup before it updates to the backup path provided (else default backup path)
That way, this can be a defined as a standalone cron task
Additionally, I noticed that even if you are on the latest version of Bookstack and run update, you receive a "Your BookStack instance at [path/BookStack] has been updated!". It would be great if this returned a "Your BookStack instance is already on the latest version" instead.
The text was updated successfully, but these errors were encountered: