4 Commits

Author	SHA1	Message	Date
ed	889bd3242a	hooks: retcode 100, zmq json; ... hooks returning exitcode 0 will: * run the next hook, if any * allow the original action, unless successive hook opposes hooks returning exitcode 100 will: * abort running successive hooks * allow the original action hooks returning anything other than 0 or 100 will: * abort running successive hooks * REJECT the original action zmq can now respond with json; a dict with "rc", "rejectmsg", "reloc" and so on, just like other hooks replying with json	2025-11-30 19:29:09 +00:00
ed	42fd66675e	tests: improve specificity	2024-12-01 15:36:35 +00:00
ed	2ab8924e2d	tests/debug: plug some resource leaks	2024-11-22 22:21:43 +00:00
ed	6c94a63f1c	add hook side-effects; closes #86 ... hooks can now interrupt or redirect actions, and initiate related actions, by printing json on stdout with commands mainly to mitigate limitations such as sharex/sharex#3992 xbr/xau can redirect uploads to other destinations with `reloc` and most hooks can initiate indexing or deletion of additional files by giving a list of vpaths in json-keys `idx` or `del` there are limitations; * xbu/xau effects don't apply to ftp, tftp, smb * xau will intentionally fail if a reloc destination exists * xau effects do not apply to up2k also provides more details for hooks: * xbu/xau: basic-uploader vpath with filename * xbr/xar: add client ip	2024-08-11 14:52:32 +00:00