My SaaS is not that big and doesn't need very complicated CRON management. I tried different options like dkron but it doesn't hold any job data after for example removing the container, according to a discusion issue I created. Source: about 1 year ago

Well, you can either use this as an example or use it cause the work is done: dkron. Source: over 1 year ago

I'am also familiar to hangfire, used in the past as distributed job scheduler for Owin microservices in C# too. Btw when we moved towards Golang stack realized that hangfire wasnt really necessary. It was enough standard and idiomatic Go code, learning using Go Routine adding any Cron library and maybe a Redis dependency if persistence is needed. But if you really prefer something hangfire-like, give a try to... Source: about 2 years ago

Perhaps https://dkron.io/ can solve your problem? Source at https://github.com/distribworks/dkron. Source: over 2 years ago

Oops, my bad. I was trying to refer to dkron https://dkron.io/. Source: over 2 years ago

Jsonnet[1] and kapitan[2] are the tools I currently use. Their learning curve is not optimal (and I tried to contribute to smoothen it with a jsonnet course[3] and a 'get started wit kapitan' blog post[4]), but once used to it it's hard to do without, and their combination makes them even more useful (esp. If you deploy K8s). In Ruud's case, Jsonnet might have been worth looking at as Hashicorp tools can be... - Source: Hacker News / 4 months ago

Kubernetes config is a decent example. I had ChatGPT generate a representative silly example -- the content doesn't matter so much as the structure: https://gist.github.com/cstrahan/528b00cd5c3a22e3d8f057bb1a75ea61 Now consider 100s (if not 1000s) of such files. I haven't given Pkl an in depth look yet, but I can say that the Industry Standard™ of "simple YAML" + string substitution (with delicate, error prone... - Source: Hacker News / 4 months ago

Maybe you'd like jsonnet: https://jsonnet.org/ I find it particularly useful for configurations that often have repeated boilerplate, like ansible playbooks or deploying a bunch of "similar-but" services to kubernetes (with https://tanka.dev). Dhall is also quite interesting, with some tradeoffs: https://dhall-lang.org/ A few years ago I did a small comparison by re-implementing one of my simpler ansible... - Source: Hacker News / 9 months ago

Apologies for the lack of context, and for missing this comment until today. Both are tools for defining kubernetes manifests (which are YAML) in a reusable manner. Jsonnet is a formally specified extension of JSON. It’s essentially a functional programming language (w/some object oriented features) that generates config files in JSON/YAML/etc, so it’s straightforward to determine whether an input file is valid,... - Source: Hacker News / about 1 year ago

I like Google's Jsonnet [1], which has all of this except for 4. Jsonnet is quite mature, with fairly wide language adoption, and has the benefit of supporting expressions, including conditionals, arithmetic, as well as being able to define reusable blocks inside function definitions or external files. It's not suitable as a serialization format, but great for config. It's popular in some circles, but I'm sad that... - Source: Hacker News / about 1 year ago