32
points
Nukesor
Joined 38 karma
- So, there's a wiki which explains many of the usecases.
I specifically didn't want to further bloat the README, as it's already super long as it is.
- Interesting.
May I ask how many tasks you were managing with Pueue and what your usecase was?
I also thought about using alternative formats such as CBOR, but choosing a human-readable format like JSON made debugging and such a lot easier.
If there's a good usecase for it, I might consider switching to a more compact format.
- 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.
I'm generally a big fan of showing alternatives: https://github.com/Nukesor/pueue/?tab=readme-ov-file#similar...
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.
- Also, editing a command in the middle if you notice a mistake becomes tricky.
Pueue also allows you to do stuff like dependencies, which get tricky in bash if a task depends on more than one tasks finishing.
- 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.
See https://github.com/Nukesor/pueue/wiki/FAQ#what-can-i-use-it-...
- Not that I know of. If anyone knows of stuff like that, please let me know, as this is regularly asked for :D.
I would be pretty stoked to be hired to build something like that, though.
- Yep, that's exactly how it's done :)
- Nope. Pueue is designed to handle your usecase times 5+.
I'm still using it for your usecase, as I'm already used to the interface by now :D.
- This question has been asked quite a lot, so I wrote a FAQ ;D :
https://github.com/Nukesor/pueue/wiki/FAQ#why-should-i-use-i...
- Hey @abelanger,
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?
- Always happy to see my stuff getting recommended :D
- I actually wrote a more modern solution to `nq` named Pueue. (https://github.com/Nukesor/pueue)
There are a lot of examples and a FAQ section + a Wiki, if you're interested in more information why one might need such a tool.
- 2 points
- 4 points
- 12 points
- 2 points
- 2 points
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.