[FEATURE] Static export

[freakhill]

Feature Summary

Markdown/Html/or other static export.

Problem/Use Case

Export a static version of the runbooks to include/archive in company wikis (and make searchable!).

Proposed Solution

A cli command / separate program / shell script would do the job.
The real problem is having to track the evolution of the file format...

Current Workaround

copy paste into the wiki...

Detailed Description

User Interface

atuin static-export workspace/runbook.atbr > runbook.md

Integration Points

Would this feature need to integrate with:

• Shell/Terminal
• Database clients
• HTTP/API calls
• File system
• External tools (specify): ___
• Other: ___

Alternatives Considered

Freeze atuin desktop version used and write our own export script.

Additional Context

• Priority: How important is this feature to your workflow? (Low/Medium/High/Critical)
  High
  it is very important to adoption for the team, but not urgent, as long as we know it is coming.
  Worst case we can freeze our atuin desktop version and write a simple script ourselves.

• Frequency: How often would you use this feature? (Daily/Weekly/Monthly/Occasionally)
  Daily

• Team Impact: Would this benefit just you or your entire team?
  Entire team

Related Issues/Discussions

Link any related issues, discussions, or community conversations about this feature.

Implementation Notes

If you have technical suggestions or constraints to consider, share them here.

[ellie]

Does the current markdown export work for you? File -> Export -> Markdown

(and make searchable!)

Does the desktop app search fit your needs?

[freakhill]

it needs to be automatable in a pipeline... (runbooks -> some_bot -> confluence/notion/etc.)

[freakhill]

that said i didn't know that option existed! some applescript could do the job as a workaround for a while.

[freakhill]

Desktop search app is not enough...

We do not have full team buy-in yet, meaning the runbooks need to be accessible from outside too.

Also they need to be accessible to some out-of-the-team members.

[ellie]

Ahh ok, totally makes sense! We've been thinking two things for exports

1. CLI, as you stated. Use however you'd like
2. Hub integration for automatic exports

[freakhill]

I sincerely apologize if it is not the right spot to talk about this.

We have one big blocker for the use of Atuin Hub.
The documentation about encryption for hub is not clear...

Our runbooks contain a lot of sensitive data. So we need one of the two:

• own the data
• or, be sure it is not usable if/once you eventually get breached

Currently we simply share "local" workspaces

Thanks for the great product! It is already pretty useful in its current state!

[ellie]

This is fine! Email ellie@atuin.sh might be better though, or just book some time - very happy to discuss

Self hosted hubs aren't currently a thing, but are something we're exploring. Obviously licensing + deployment stacks are things we still need to figure out.

Depending on the nature of your sensitive data, we are also exploring secrets: https://man.atuin.sh/secrets/

Currently we simply share "local" workspaces

Totally makes sense!

Glad it's working for you <3