Migrate, upgrade, and build from source

Migrate, upgrade, and build from source

Migrate in

# from daimon-memory v1 (JSONL export), preserving original timestamps:
dmem migrate --url https://v1-host:8080 --token <admin-token>   # TLS verified; --insecure or --ca-cert <pem> for a self-signed v1
dmem migrate --file export.jsonl          # or - for stdin

# from a folder of markdown (e.g. an Obsidian vault):
dmem import ~/vault/                       # folder -> namespace, # H1 / filename -> title

migrate carries each v1 record across 1:1 (dm-lite's kinds match v1 exactly) and preserves its original creation time (as valid-time) and importance. import walks the tree, uses frontmatter when present and infers otherwise.

Keep it updated

dmem upgrade           # latest stable release
dmem upgrade --pre     # include release candidates (rc/beta)

It replaces the binary in place. Your data lives in a separate directory and is never touched; the schema migrates forward on the next run.

Build from source

cargo build --release                            # pure Rust, keyword recall, no models
cargo build --release --features zvec,candle     # add the dense vector store plus bge-small semantics
cargo build --release --features dist            # the full release binary (all of the below)

The default build is offline and light. zvec adds the dense vector store (downloads a prebuilt native lib). candle adds real bge-small embeddings (downloads the model once on first use), the embedder the release binaries use, overridable to a multilingual checkpoint by env (see "Embedding models"); fastembed is an alternative embedder behind its own feature. server adds the axum HTTP API with built-in TLS. client adds remote-client mode. wizard adds dmem setup. self-update adds dmem upgrade. ui adds the optional offline graph viewer (dmem ui). dist bundles zvec, candle, server, client, wizard, self-update, and ui, which is what the release binaries ship.