From d596cb5e7e0b3a6e4137a4585efabfd4781e2ab8 Mon Sep 17 00:00:00 2001 From: zadam Date: Sun, 14 Aug 2022 15:08:54 +0200 Subject: [PATCH] Updated Document (markdown) --- Document.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/Document.md b/Document.md index 22c6e16..ddde6ec 100644 --- a/Document.md +++ b/Document.md @@ -22,4 +22,18 @@ In some cases you might want to take a look at the demo document after you delet Trilium provides a lot of flexibility, but with that you can also potentially shoot yourself in the foot (e.g. with startup script which blanks the app view). -In such cases you can manually fix notes on the database layer - you can use e.g. [https://sqlitebrowser.org/](https://sqlitebrowser.org/) to open `document.db` file, find problematic notes and manually fix them. Don't forget to commit / write changes after you're done. \ No newline at end of file +In such cases you can manually fix notes on the database layer - you can use e.g. [https://sqlitebrowser.org/](https://sqlitebrowser.org/) to open `document.db` file, find problematic notes and manually fix them. Don't forget to commit / write changes after you're done. + +## How to reset document + +If you previously just experimented with Trilium and want to get it to the initial state, you can do that by deleting the `document.db*` files, e.g. like this: + +```bash +rm document.db* +``` + +If you don't need to preserve e.g. the `config.ini`, then you can also delete the whole [[data directory]] like this: + +```bash +rm -r ./trilium-data +``` \ No newline at end of file