Expand description
Where a remote embedding/extraction backend’s URL, model and credential come from, resolved from the environment once so the daemon and the language bindings read the same variables the same way (#1886). Where a remote embedding/extraction backend’s URL, model and credential come from — one shape for both roles, on purpose. The two were configured differently for historical reasons only — extraction by role, embedding by product — and an operator who has configured one should not have to learn the other (#1751, arbitration C1).
Lives in the library, not the daemon binary, so every caller that resolves
the embedding role’s remote backend reads the same four
VELESDB_MEMORY_EMBEDDER* variables the same way: the daemon and both
language bindings (#1886), instead of the bindings reimplementing (or, as
it was until #1886, simply never reading) the resolution the daemon
already had.
Structs§
- Remote
Endpoint - A remote backend’s configuration, read from one role’s environment.
Functions§
- embedder_
env_ endpoint - The embedding role’s endpoint, honouring the legacy
VELESDB_MEMORY_OLLAMA_*aliases (C1), plus an alias-conflict notice for the caller to print. - role_
auth - Read a role’s API token and turn it into what the transport will send.