Crates.io | config-store |
lib.rs | config-store |
version | 1.0.0 |
source | src |
created_at | 2024-11-08 18:51:18.58143 |
updated_at | 2024-12-08 18:08:51.42236 |
description | config-store is a simple and lightweight key-value store designed for easy use from shell scripts |
homepage | |
repository | https://github.com/DOD-101/config-store |
max_upload_size | |
id | 1441438 |
size | 39,070 |
Config-Store is a simple key-value store designed to be used from shell scripts.
Say, for example, you have a keybinding that switches between two applications. For this, you will probably need to save what app you are currently in.
Now you could create an entry with the set
command and then toggle between the states with toggle
config-store --help
or see doc comments in ./src/commands.rs
Config-store has shell completions. Simply add eval "$(config-store completions *your_shell*)"
to your shell config.
/tmp
Most distros will clear /tmp
on boot. You should check what the case is for your distro and write your scripts accordingly, or change /tmp
to clear on boot.
On NixOS this can be done by setting boot.tmp.cleanOnBoot = true;
.
Simply run cargo install
.
The data (aka the key-value pairs) are stored in /tmp/config-store.db
, which is a sqlite3 database.
Internally, the commands are mostly wrappers around SQL statements.
While it is technically possible to have multiple different entries with the same name, because the primary key is not the name.
This is impossible to do with the commands provided, since set
will always update a value if it exists.
Because the data is stored on disk, config-store needs no server process. Not only does this make it simpler, it also means there is no overhead to using it to store your variables.
This project is licensed under either of
at your option.