[HN Gopher] Atuin's New Runbook Execution Engine
___________________________________________________________________
Atuin's New Runbook Execution Engine
Author : emschwartz
Score : 100 points
Date : 2025-11-24 21:06 UTC (4 days ago)
(HTM) web link (blog.atuin.sh)
(TXT) w3m dump (blog.atuin.sh)
| piqufoh wrote:
| I love atuin -- the shared shell command memory function solves a
| problem that I had (recalling obscure CLI commands)
|
| I'll try atuin desktop and I hope it succeeds, but I can't say
| that it solves any particular problem that I have and am aware
| of.
| Ghoelian wrote:
| I had the same feeling. It looks like a super cool product, and
| I'd love to do something with it. I just have no idea what.
| robinhood wrote:
| I had the same thoughts a few months ago, and then someone told
| me Atuin Desktop is made for DevOps and the likes, in order to
| scale manual and repetitive operations accross many teams. This
| made sense to me.
| nickspacek wrote:
| We have CI actions we use to configure and deploy dev
| namespaces. We document a bunch of steps for these actions in
| a doc, including situational tweaks. I could see this being a
| great replacement for that, given the right integrations.
| azuanrb wrote:
| Tried it few days ago, and came to same conclusion myself. In
| a way, it's like Ansible but simpler for some use cases.
| gtirloni wrote:
| Manual repetitive processes are already a smell. Shared
| across teams?
| imiric wrote:
| Atuin seemed like an interesting way to sync shell history across
| machines. That wasn't a problem I personally had, but I could've
| seen myself giving it a try.
|
| These recent developments with the Desktop tool, and now what
| seems like a Jupyter-like replacement for... shell scripts(?)...
| sounds completely alien to me. I'm sure it solves some problem
| for somebody, but it's far removed from any problem I've ever
| had. Good luck with the project, as it does look like a lot of
| work and thought went into it.
| acedTrex wrote:
| Honestly atuin is great even if you dont sync history.
| quasigod wrote:
| Yeah even the completely offline features make it much nicer
| than a standard shell history
| theoldgreybeard wrote:
| Atuin Desktop is wonderful.
|
| At first I didn't know what I wanted to do with it...then I
| realized basically anything I would want to do more than once
| should go in here.
|
| One off CSV export from a custom sql query? It's in Atuin.
|
| Need to onboard a new dev across all our various repos and tools?
| Shared Atuin runbook.
|
| Basically any kind of manual process I've ever needed now lives
| in Atuin and is almost entirely automated. It's wonderful.
|
| Used to do all this stuff with Confluence and a bunch of copy-
| paste. No more.
| jdorfman wrote:
| I haven't tried the desktop but I use the CLI tool multiple times
| a day (sometimes hour) and I just want to thank the team for
| making my life easier.
| quasigod wrote:
| Ive been wanting to give this a try. I see that it mentions
| markdown formatting support, but I wonder if it actually supports
| markdown. I'd love to find a way to integrate it with my Obsidian
| vault, since I already have all my shell snippets and homelab
| docs there
| slurrpurr wrote:
| Very cool, but what is the advantage of this over something like
| marimo?
| mkl wrote:
| What is the advantage of a screwdriver over something like a
| saw?
|
| Atuin Desktop and Marimo have quite different purposes and not
| much in common. Atuin Desktop is a runbook system for devops,
| to store, document, and run sequences of templated terminal
| commands (and some other things). Marimo is a reactive Python
| notebook development system for programming, data science,
| etc., which can't run terminal commands.
| zem wrote:
| this looks wonderful, will have to see if I can get permission to
| use it at work.
___________________________________________________________________
(page generated 2025-11-28 23:00 UTC)