mirror of
https://github.com/zadam/trilium.git
synced 2025-12-04 22:44:25 +01:00
Updated Anonymized database (markdown)
parent
612786c8a8
commit
2fb0b841f4
@ -1,19 +0,0 @@
|
||||
### Anonymized database
|
||||
|
||||
In some cases, it's necessary to see the database structure to be able to debug the problem. Of course, we can't ask you to send us your [[document|Document]] file with your notes.
|
||||
|
||||
For this, Trilium supports anonymization of the database - you can trigger this in Options -> Advanced tab.
|
||||
|
||||
[[images/anonymization.png]]
|
||||
|
||||
This will create a copy of your document and remove all sensitive data (currently note titles, contents, revisions, history and some of the options, and non-system attributes) while leaving all structure and metadata (e.g. date of last change). After this is done, the database is [VACUUMed](https://sqlite.org/lang_vacuum.html) to make sure there's no stale sensitive data in the document file. The resulting file is stored in `anonymized` directory (placed in the [[data directory]]). You can safely attach it with your bug report or send it to zadam.apps@gmail.com
|
||||
|
||||
#### Command line anonymization
|
||||
|
||||
If the database is corrupted in a way which prevents Trilium to start up, you won't be able to trigger the anonymization from the UI. For such a case, anonymization is also available from command line:
|
||||
|
||||
```
|
||||
node src/anonymize.js
|
||||
```
|
||||
|
||||
This needs to be executed in the directory with Trilium source files, for desktop builds this in `resources/app` directory.
|
||||
1
Anonymized-database.md
Normal file
1
Anonymized-database.md
Normal file
@ -0,0 +1 @@
|
||||
See https://docs.triliumnotes.org/user-guide/troubleshooting/anonymized-database.
|
||||
Loading…
x
Reference in New Issue
Block a user