Closed oliver-la closed 1 month ago
Backrest definitely works for me without opening the browser, so the main point that it cancels the execution when the browser is closed
isn't clear to me. I'm on Windows, perhaps you use a different OS? Please clarify
@SerVB I think you misunderstood. This is regarding the "Run Command" feature in the web UI. Not about executing backrest itself.
Right — thanks for making an issue to track this. It’s definitely in my plans to make command executions into entries in the operation history.
I expect to get to this sometime in the next month.
Implemented in https://github.com/garethgeorge/backrest/pull/516
@garethgeorge That was super quick, thank you so much! <3 I'm gonna go ahead and close this issue.
Just remembered I never created a feature request for this. At last, here it is. :)
Is your feature request related to a problem? Please describe. Backrest currently runs custom commands in the foreground/browser and cancels the execution when the browser is closed or the connection interrupts. It's therefore unsuitable to run commands that may take a long time. For example, I'd like to run prune with extra flags which is going to take quite some time.
Describe the solution you'd like The commands should be sent to the background. A new entry both in the Tree View and Operation List of the repository should appear, with a visual indication of the command's status. (running/ended/failed) As a user I should also be able to view the output of the command.
Or, as Gareth put it:
Discussed in https://github.com/garethgeorge/backrest/discussions/482