denoflow VS debug-toolkit

I'm doing something[0] similar with Deno, currently it configures workflows based on yaml files, but my goal is to make a gui tool to help generate yaml config files. My work is still very early stage, currently it can use any remote Deno module or typescript/javascript to execute steps and fetch and filter source data.

The Deno runtime is great for workflows because Deno is lightweight and can import modules using arbitrary URLs.

[0]: https://github.com/denoflow/denoflow

We're very much not a company of one anymore, but I used Unicorn Platform for our startups website (http://robusta.dev)

It's optimized for building a decent looking startup website in half an hour.

We now have an in house designer and frontend team so the whole thing will be replaced soon... But it got us fairly far.

I use it all the time when hiring!

We're open source (https://robusta.dev) and very involved in the kubernetes ecosystem so GitHub history is extremely relevant when we look at candidates.

We'll hire people with no GitHub activity too, but when it's available it's great

Github: https://github.com/robusta-dev/robusta Marketing site: http://robusta.dev/ Docs: https://docs.robusta.dev/master/

We're using Hikaru extensively in Robusta. The best part (well, other then the ease of use) is that Tom is super responsive to issues on GitHub and always happy to help.

To everyone saying that Kubernetes is unnecessary, try implementing autoscaling, service discovery, secrets management, and autohealing in a vendor independent way without it.

Of course none of that is necessary for a self hosted home lab, but neither is gitops.

This is a very nice example of how to set stuff up properly.

OP, I would love to see Robusta (https://robusta.dev) as part of this too. It's definitely in line with your vision of automating everything, as it let's you automate the response to alerts and other events in your cluster. (Disclaimer: I'm one of the maintainers)