extern/hishtory
1
0
Fork 0
mirror of https://github.com/ddworken/hishtory.git synced 2025-06-21 04:17:45 +02:00
Code Issues Packages Projects Releases Wiki Activity

Fix typo

Browse Source
This commit is contained in:
David Dworken 2022-10-09 10:45:00 -07:00 committed by GitHub
parent 68416f9d0f
commit f7a1e14451
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -1,6 +1,6 @@
# hiSHtory: Better Shell History
`hishtory` is a better shell history. It stores your shell history in context (what directory you ran the command it, whether it succeeded or failed, how long it took, etc). This is all stored locally and end-to-end encrypted for syncing to to all your other computers. All of this is easily queryable via the `hishtory` CLI. This means from your laptop, you can easily find that complex bash pipeline you wrote on your server, and see the context in which you ran it.
`hishtory` is a better shell history. It stores your shell history in context (what directory you ran the command in, whether it succeeded or failed, how long it took, etc). This is all stored locally and end-to-end encrypted for syncing to to all your other computers. All of this is easily queryable via the `hishtory` CLI. This means from your laptop, you can easily find that complex bash pipeline you wrote on your server, and see the context in which you ran it.
![demo](https://raw.githubusercontent.com/ddworken/hishtory/master/backend/web/landing/www/img/hishtory.svg)
@ -84,4 +84,4 @@ When the user runs `hishtory query`, it retrieves all unread blobs from the back
This all ensures that the minimalist backend cannot read your shell history, it only sees encrypted data.
If you find any security issues in hiSHtory, please reach out to `david@daviddworken.com`.
If you find any security issues in hiSHtory, please reach out to `david@daviddworken.com`.