Joseph Huckaby

Hello, and thanks for the issue report. I don't know of any current solution to this issue. But in a future release I can make the server-to-server communication available on...

Hi there! So sorry for the 7-year delay on this. I have not forgotten! Cronicle v2 has a completely redesigned server-to-server communication system, where the worker nodes now connect to...

Thank you so much for this feature request! Cronicle v1 is in maintenance mode, so I am not adding new features, HOWEVER... I can happily report this feature is actually...

Coming in v2! Releasing in 6 weeks.

Dark mode is coming in v2! 😃 I am targeting end of year (2025) for release, and I am on track to make the date. So sorry for the long...

Hmmm, I am unable to reproduce this issue. I have nginx setup with a simple proxy to a backend: ``` server { listen 3001; server_name localhost; location /sleep { proxy_pass...

I did what you asked, but got the same result. It completes the job with a HTTP 504 with no problem.  Note that if you leave the HTTP Plugin...

I'm sorry for the confusion over the Plugin JSON STDIO system. Cronicle will always "eat" JSON detected in the STDOUT stream of the child process, if it is compacted onto...

Coming in v2! Releasing in a month or so. I'll update this issue as soon as it launches.

Do you mean you want a job to run continuously? Like, as soon as it completes, run it again? If so, check out this Wiki article: https://github.com/jhuckaby/Cronicle/wiki/Continuously-Running-Jobs