The CLI likely won't be the right way to update the application, but users might reach for it under the assumption it's the official approach. Would be ideal to have some level of warning.
Often these environments won't have the local git repo.
This leads to failure anyway, avoiding the above, but we should be more graceful.
Potential implementation:
Check for <app>/.git. Exit early if not existing, showing a warning along the lines of:
Could not find a local git repository, It does not look like this instance is managed via normal means.
If you are running BookStack via a docker container, you should update following the advised process for the docker container image in use. This typically involves pulling and using an updated docker container image.
The CLI likely won't be the right way to update the application, but users might reach for it under the assumption it's the official approach. Would be ideal to have some level of warning.
Often these environments won't have the local git repo. This leads to failure anyway, avoiding the above, but we should be more graceful.
Potential implementation: Check for
<app>/.git. Exit early if not existing, showing a warning along the lines of: