Skip to main content

Crate packset_daemon

Crate packset_daemon 

Source
Expand description

The loopback pack writer.

One process owns memory.lmdb and every client speaks HTTP to it, so an isolated harness home does not get a private store. Cards stay files because a person edits them; atoms are a database because a program does.

Re-exports§

pub use home::Home;
pub use service::Service;
pub use store::Store;

Modules§

cards
USER.md and MEMORY.md: the parts of the pack a person edits.
context
What the checkout says, as opposed to what the pack remembers.
embed
The dense projection as a kept child process (packset-embed), one per direction. An absent encoder is a supported state: every failure falls back to the lexical scorers. A vector is derivable from the text, never the store.
glob
Shell-style name matching, the way fnmatch does it.
home
Where the pack lives on disk.
http
The /v1 surface.
milli
The search projection, driven as a separate process.
proposals
Mining an archived day into proposals a person can accept.
service
What the writer does, apart from how a client asked.
store
Atoms in LMDB: key workspace\0id, value the record as JSON. A seat’s existing memory.lmdb opens here unchanged; the NUL makes a workspace scan a prefix scan.
workspace
Naming the workspace a client is in.

Functions§

run
The packsetd binary. Also the packset crate’s packsetd bin.