4 ms·
I've wanted to write something like this for years! For me it's always long running rsync commands I want to chain. I still might write one as it would be a fu
by seabrookmx 3y ago
I've wanted to write something like this for years! For me it's always long running rsync commands I want to chain.
I still might write one as it would be a fun way to play around with some low level code, but when I actually want to get things done I'll be checking this out.
- kjkjadksj 3y agoCould you just chain them in bash script? You can do it in a dumb way or you can even do it conditionally on the exit status of the previous rsync command.
- seabrookmx 3y agoYes or I could use the bash `&&` but the issue is I need to know all the commands at the start. I want to be able to come back an hour later and easily add a command to the end of the chain.
- kjkjadksj 3y agoYou can do that by abrogating your pid
- Nukesor 3y agoAlso, 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.
- kjkjadksj 3y agoIf this ability is important to you then you can break your pipeline into individual files that aren’t going to be read until they are executed, giving you time to edit.
- Nukesor 3y agoFair 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.