Documentation claims apiKey is inferred from MEILI_OLLAMA_URL

[ellnix]

apiKey
Authentication token Meilisearch should send with each request to the embedder.
This field is mandatory if using a protected rest embedder.
This field is optional for openAI and ollama embedders. If you don't specify apiKey, Meilisearch will attempt to read it from environment variables OPENAI_API_KEY and MEILI_OLLAMA_URL, respectively.
(emphasis mine)

I checked the source code, that env variable appears in

fn get_ollama_path() -> String {
    // Important: Hostname not enough, has to be entire path to embeddings endpoint
    std::env::var("MEILI_OLLAMA_URL").unwrap_or("http://localhost:11434/api/embeddings".to_string()) }

It only gets called once:

        let url = self.url.unwrap_or_else(get_ollama_path);

I cannot see how it interacts with the api key, if at all. This probably belongs in the documentation for the url parameter.

I don't use AI in anything, so I thought I'd post here just in case I'm misinterpreting something.

[guimachiavelli]

Thanks for bringing this to our attention, @ellnix. This information has been validated by our SMEs, but it's possible we missed that bit.

@dureuill, @macraig, can you provide some insight here?

[dureuill]

Hello, missed this, sorry,

@ellnix is correct, MEILI_OLLAMA_URL is used to infer the url parameter of ollama embedders if that parameter is unspecified.

AFAIK ollama does not support authentication by itself, it has to be provided by a proxy. We support apiKey for ollama (it adds an authentication header with a classic Bearer scheme), but this doesn't actually work without a proxy to support the authentication, so we're not also adding an env variable.