mingzailao
/
silverbullet
mirror of https://github.com/silverbulletmd/silverbullet.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Database recommendations #1092

pull/1098/head
Zef Hemel 2024-09-26 23:00:14 +02:00
parent 4eae0c975b
commit 4bb99a40fe
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
website/Install/Configuration.md
View File

@ -61,7 +61,11 @@ SilverBullet requires a database backend to (potentially) keep various types of
Currently, only two databases are supported: [Deno KV](https://deno.com/kv) and a dummy in-memory database. Currently, only two databases are supported: [Deno KV](https://deno.com/kv) and a dummy in-memory database.
## Deno KV database ## Deno KV database
When self-hosting SilverBullet (that is, on any server other than on [[Install/Deno Deploy]]), KV uses a local SQLite file to keep data. This is efficient and performant. When self-hosting SilverBullet (that is, on any server other than on [[Install/Deno Deploy]]), KV uses a local SQLite file to keep data. This is efficient and performant, at least if your disk is.
If you are hosting your space on a NAS, you may consider storing the database somewhere else. You can do this by setting the `SB_KV_DB` path to a path outside your space, e.g. `SB_KV_DB=/var/lib/silverbullet/silverbullet.db`
If you use [[Install/Docker]], and set `SB_KV_DB`, make sure you bind mount an external folder into your container for this data to be persistent, e.g. by passing `-v /var/lib/space_db:/var/lib/silverbullet` to your `docker run` command.
KV can be configured as follows: KV can be configured as follows: