HN user

itayd

69 karma
Posts15
Comments18
View on HN

Leash – I built an incident management system in ~200 lines of Python, production ready.

Tired of paying per-user for PagerDuty? I built an open-source alternative that handles on-call rotation, escalation, and multi-channel alerts (Slack/Email/SMS).

Workflows that wait hours for responses survive restarts without needing message queues or state machines. And your team edits schedules directly in Google Sheets instead of clicking through admin UIs.

Hiding is actually not the main thing here. AK allows you to "deploy in a click" instead of deploying the actual workers. We also provide integrations with built in authentication for external services such as Slack, JIRA, etc.

In previous life I've been self hosting Cadence and it worked quite well. We then moved to Temporal cloud which was even easier.

That said, if you use autokitteh.cloud, you don't need to worry about Temporal as we're doing all that management behind the scenes.

Starlark Language 2 years ago

the go implementation, at least, allows you to enable while loops among others, which makes it turing complete and not guaranteed to complete. obviously you should never turn this on for configuration, but it is useful for general scripting usage.

Starlark Language 2 years ago

Starlark is awesome. We studied the language quite a lot, Alan Donovan did awesome work on its golang runtime [1] and there are more implementations in rust [2] and others.

Since the language and the backend allow to write deterministic functions, we found it's really suited well for automations written as durable functions. We implemented exactly that [3] over Temporal [4], though we also support Python as well among other runtimes.

[1] https://github.com/google/starlark-go

[2] https://github.com/facebook/starlark-rust

[3] https://autokitteh.com, https://github.com/autokitteh/autokitteh

[4] https://temporal.io

Developer here.

This was actually made before GitHub Actions were out. This can potentially be converted in the future to function as a GitHub action.

That said - this gives a much faster reaction to events from GitHub as nothing needs to be provisioned before execution. Also allows for much simpler deployment and developemnt.

I discuss this in my EnvoyCon talk, see on repokitteh.io for video.