1,103 karma · joined December 17, 2021
building atuin.sh
ellie@elliehuxtable.com
40% battery for 4hrs of real work is better than pretty much any linux supported laptop I've ever used
We shelled out to fzf in the very early days, but found the initial indexing to be a bit slower + add latency vs SQLite
We will have better markdown support soon
Atuin runbooks (mentioned in the article) do this! Pretty much anywhere we allow users to start typing a shell command we feed shell history into the editor
1. TUI for interactive terminal runbooks
2. CLI for hands-off execution, CI, etc
we already support execution of script + terminal blocks over SSH, but want much tighter integration. Parallel execution is certainly a part of that too. anything else you'd want to see?
We're aiming to be flexible enough, so that if you can do it in a terminal then you can _also_ do it with a runbook
BUT it does also make a nice environment for rich text, with markdown support, so can easily replace internal docs in general
---
The runbook files are just YAML (for now). They're more verbose than I'd like, but do convey a lot of information - both rich text and executable.
There's an example here: https://github.com/atuinsh/desktop/blob/8ebed35d7efe68a92363...
I'm aware this isn't ideal, and longer term we want something that looks much more like markdown. A key requirement for us here is that it's easy + convenient to type - just like normal markdown - so putting everything as a code block annotation isn't ideal.
The current sketch of what that could be looks like this: https://forum.atuin.sh/t/desktop-devlog-markdown-vim-local-f...
Would love to know if you have any thoughts!
There's an example here: https://github.com/atuinsh/desktop/blob/8ebed35d7efe68a92363...
I'm aware this isn't ideal, and longer term we want something that looks much more like markdown. A key requirement for us here is that it's easy + convenient to type - just like normal markdown - so putting everything as a code block annotation isn't ideal.
The current sketch of what that could be looks like this: https://forum.atuin.sh/t/desktop-devlog-markdown-vim-local-f...
Would love to know if you have any thoughts!
We don’t yet support full remote execution, but should do soon!
It’s definitely baked into the approach here. You could just write a bullet point list of what needs doing. Then maybe sprinkle some blocks on top so the user can do things faster. Then in the end, work towards the whole thing being automated
No all or nothing, no YAML needed ;)
Let us know if you try it and have any feedback or questions at all
Happy to answer any questions
I can’t guarantee we never will, but I am only interested in such things if they are genuinely useful
If we won’t use it internally, and no significant % of users will, then it won’t happen
It's always been opt-in, or "opt-out by default".
And also the default is now to use 40 lines, not the alt screen (has its own drawbacks)
You can set “inline_height”
Also has functions for filtering command search by directory
Being backed by SQLite tends to mean your history is more durable + is properly saved across shells too
Otherwise consistency is nice if you use a few setups