# Start on a database-backed prompt library \(\#12468\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/5f98b9617a30b5e8a85a0393cf021ec1db02e2e5)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: 5f98b9617a30b5e8a85a0393cf021ec1db02e2e5

Requested commit: 5f98b9617a30b5e8a85a0393cf021ec1db02e2e5

Commit: 5f98b9617a30b5e8a85a0393cf021ec1db02e2e5

Tree: a4bba52a7b604ea791675ceb95d900ca3b5cbed5

Author: Nathan Sobo

Committer: GitHub

## Message

```
Start on a database-backed prompt library (#12468)

Using the file system as a database seems like it's easy, but it's
actually a real pain. I'd like to use LMDB to store the prompts locally
so we have more control. We can always add an export option, but I want
the source of truth to be somewhere other than the file system.

So far, I have a PromptStore which is global to the application and can
be initialized on startup. Then there's a `PromptLibrary` which is
intended to be the root of a new kind of Zed window. I haven't actually
seen pixels yet, but I've sketched out the basics needed to create a new
prompt, save, etc.

Still lots to figure out but the foundations of being backed by a DB and
rendering in an independent window are in place.

/cc @iamnbutler @as-cii 

Release Notes:

- N/A

---------

Co-authored-by: Antonio Scandurra <me@as-cii.com>
```

## Parents

- [18e2b43d6d3066cea08fe426f0d1c47bc048fdc5](https://git.cafe/gitcafe/zed/commit/18e2b43d6d3066cea08fe426f0d1c47bc048fdc5?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/5f98b9617a30b5e8a85a0393cf021ec1db02e2e5?format=markdown)