SQLite-backed Key / Value Store
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

chore: update README and version bump

+1 -11
+1 -1
Cargo.toml
··· 1 1 [package] 2 2 name = "safir" 3 - version = "0.11.0" 3 + version = "0.11.1" 4 4 edition = "2021" 5 5 authors = ["Graham Keenan <graham.keenan@outlook.com>"] 6 6 license = "MIT OR Apache-2.0"
-10
README.md
··· 46 46 -V, --version Print version 47 47 ``` 48 48 49 - ## File Mode vs Database Mode 50 - 51 - File mode is just like the old version of `safir` - all KV pairs are stored in a JSON value like before. 52 - 53 - Database mode uses an SQLite database as storage instead which is _technically_ more secure. 54 - 55 - Switching between modes does not carry over any changes from the previous mode (i.e. KV pairs added in File mode are not present in Database mode unless you add them yourself). 56 - 57 - This could change in a future release 58 - 59 49 ## Environments 60 50 61 51 Safir now supports storing KV pairs in specific environments which will declutter the `list` command and also keep all related KV pairs in one single place.