Nukesor

18 ms·

1.
by Nukesor 2y ago
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 con
2.
by Nukesor 2y ago
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.
3.
by Nukesor 2y ago
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.
4.
by Nukesor 2y ago
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://g
5.
by Nukesor 2y ago
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.
6.
by Nukesor 2y ago
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#wh
7.
by Nukesor 2y ago
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.
8.
by Nukesor 2y ago
Yep, that's exactly how it's done :)
9.
by Nukesor 2y ago
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.
10.
by Nukesor 2y ago
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...
11.
by Nukesor 3y ago
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&
12.
Pueue – a beautiful Unix job queue system(github.com)
32 points by Nukesor 6y ago|2 comments
13.
by Nukesor 6y ago
Always happy to see my stuff getting recommended :D
14.
by Nukesor 6y ago
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 s
15.
Show HN: Pueue An executor for long running shell commands, rewritten in Rust(github.com)
2 points by Nukesor 7y ago|0 comments
16.
Show HN: Gitalizer – A tool to evaluate the thread of exposing Git metadata(github.com)
4 points by Nukesor 8y ago|0 comments
17.
Show HN: Pueue: A daemonized Unix command line queue utility(github.com)
12 points by Nukesor 9y ago|1 comments
18.
Daemonized sequential command execution tool for heavy load tasks(github.com)
2 points by Nukesor 10y ago|0 comments
19.
A neat command scheduler for shells(github.com)
2 points by Nukesor 11y ago|0 comments