Fair point, but to be honest, at this point it's just easier to do a:
pueue add 'rsync somestuff host:location'
And if I notice any problems, I just do a `pueue edit $id` and I'm good to go.
It's just a lot more convenient than manually building pipelines with files that'll be executed.
It would be something different if this was about recurrent tasks that needed to be done, though. But for one-off stuff, your approach seems a bit cumbersome.
You can probably achieve a good subset of its functionality in bash, it's just a nicer interface with a lot of configurability and several convenience features.
Would you be willing to write a proper guide on how to do all of these things in bash? It would be great to have such a guide inside the Pueue wiki and link to it. It'll help people to make a more informed decision on whether they need this tool or not.
Well, if you're planning on running 10 commands sequentially that might take a few hours each, you would have to keep those windows open for quite a while.
I got a few feature request for Pueue that were out of the scope as they didn't fit Pueue's vision, but seem to fit hatchet quite well (e.g. complex scheduling functionality and multi-agent support) :)
One thing I'm missing from your website however, is an actual view from how the interface looks like, what does the actual user interface look like.
Having the possibility to schedule stuff in a smart way is nice and all, but how do you *overlook* it? It's important to get a good overview of how your tasks perform.
Once I'm convinced that this is actually a useful piece of software, I would like to reference you in the Readme of Pueue as a alternative for users that need more powerful scheduling features (or multi-client support) :) Would that be ok for you?
pueue add 'rsync somestuff host:location'
And if I notice any problems, I just do a `pueue edit $id` and I'm good to go. It's just a lot more convenient than manually building pipelines with files that'll be executed.
It would be something different if this was about recurrent tasks that needed to be done, though. But for one-off stuff, your approach seems a bit cumbersome.