filed
Job queue using FUSE
git clone git://mccd.space/filed
| Log | Files | Refs | README | LICENSE |
commit c2ba453d5e7492a8dfa4854e98c808c1bd8e326a parent da905cf68817197e8f56118ab66c2916a649f325 Author: Marc Coquand <marc@coquand.email> Date: Sun, 14 Dec 2025 20:58:39 +0100 More readme and comparisons Diffstat:
| M | README.md | | | 15 | ++++++++++++++- |
1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md @@ -1,6 +1,6 @@ # qj - queue jobs -`qj` is a simple job queue that is manipulated using files. It is intended for single-server workloads and features: +`qj` is a simple job queue that is manipulated using files. It is intended for single-server workloads, for example as a companion to another app, and features: - Retries - Output logs @@ -67,5 +67,18 @@ $ mv /tmp/qj-jobs/failed/1 /tmp/qj-jobs/pending $ cat /tmp/qj-jobs/active/1 ``` +## TODO + +- [ ] Support chmod and chown +- [ ] State is configured via environment variable +- [ ] Customizable backoff and timeout before retries + +## qj compared to alternatives + +- [nq] - `nq` is simpler and not a persistent process, but does not feature retries. They serve different purposes: `nq` for ad-hoc queuing of command lines. `qj` serves well as a job manager for your server, where you want admins to see jobs and be able to rerun them. +- [task-spooler] - `ts` has better control over how you want the task executed (GPU or CPU), and a lot of other features. It does (AFAIK) not support retries, which are supported in `qj`. + +[nq]: https://github.com/leahneukirchen/nq +[task-spooler]: https://github.com/justanhduc/task-spooler