mikeTWC1984

Below is the ngnix config I've used to use for reverse https (to rout localhost:3012 to https://myhost.com and https/myhost.com/cronicle). The only trick was to handle route for socket.io. It worked...

Yes, there will be problems with livelog in this case. Check that issue: https://github.com/jhuckaby/Cronicle/issues/426

Based on you recent issues, I guess what you are requesting is a workflow, like running N jobs as a single unit (concurrently or in sequence). There is no in-the-box...

I think at this point filtering existing tabular views would be challenging. The storage basically is a collection of pages (storing N records each). Page number on tabular view just...

I think you just observing catch-up. If your server is down, and then up - the missing job will run on the next tick. But in case when next tick...

Just to clarify - are you saying cronicle keeps launching jobs as you hit run API?

I just tried to start a job singleton job hitting run API multiple time - everything works as expected (only 1 job is running)? Is that something you can reproduce...

I guess that make sense. What you see is process uid/gid, when cronicle spawns a child process it only sets uid and gid. It sounds like it's possible to set...

Yeah, looks like it's impossible to assign secondary groups to child process, at least in node. I guess setgroups would only work for root user, which make no sense (can...

I believe single node should work fine under reverse proxy if you are using same protocol on both sides. But if Cronicle is http but proxy is https it won't...