From ed3c67daf9b63aac245cc77f072da5a3817c08ed Mon Sep 17 00:00:00 2001 From: David Dworken Date: Wed, 9 Nov 2022 15:12:23 -0800 Subject: [PATCH] Document hishtory import --- README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index bd49a7d..0d59218 100644 --- a/README.md +++ b/README.md @@ -68,7 +68,6 @@ You can customize the columns that are displayed via `hishtory config-set displa ``` hishtory config-set displayed-columns CWD Command ``` -
@@ -110,6 +109,11 @@ By default, hiSHtory relies on a backend for syncing. All data is end-to-end enc But if you'd like to self-host the hishtory backend, you can! The backend is a simple go binary in `backend/server/server.go` that uses postgres to store data. Check out the [`docker-compose.yml`](https://github.com/ddworken/hishtory/blob/master/backend/server/docker-compose.yml) file for an example config to start a hiSHtory server and how to configure it.
+
+Importing existing history +hiSHtory imports your existing shell history by default. If for some reason this didn't work (e.g. you had your shell history in a non-standard file), you can import it by piping it into `hishtory import` (e.g. `cat ~/.my_history | hishtory import`). +
+
Uninstalling If you'd like to uninstall hishtory, just run `hishtory uninstall`. Note that this deletes the SQLite DB storing your history, so consider running a `hishtory export` first.