You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 26, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Jul 26, 2024. It is now read-only.
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.
Thanks for the suggestion @slimninja.
Personally, I'm not too fond of this due to the added complexity of supporting the merging two commands, each with their own options. I really want to try to keep things simple in this CLI, with specific commands for specific jobs.
I can understand the scenario/need though.
Maybe we can come at this from a different angle though, and look to implement a check-update command (or similar), that returns a status code depending on if there's an update or not.
That way you'd be able to do something like:
Thanks for the suggestion @slimninja.
Personally, I'm not too fond of this due to the added complexity of supporting the merging two commands, each with their own options. I really want to try to keep things simple in this CLI, with specific commands for specific jobs.
I can understand the scenario/need though.
Maybe we can come at this from a different angle though, and look to implement a check-update command (or similar), that returns a status code depending on if there's an update or not.
That way you'd be able to do something like:
Activity
[-]Backup before update flag[/-][+]Feature request - Backup before update flag[/+]ssddanbrown commentedon Jul 25, 2023
Thanks for the suggestion @slimninja.
Personally, I'm not too fond of this due to the added complexity of supporting the merging two commands, each with their own options. I really want to try to keep things simple in this CLI, with specific commands for specific jobs.
I can understand the scenario/need though.
Maybe we can come at this from a different angle though, and look to implement a
check-updatecommand (or similar), that returns a status code depending on if there's an update or not.That way you'd be able to do something like:
slimninja commentedon Jul 25, 2023
That's a great idea, and solves my initial problem as well. Reduces overlap as well