doc: add info on running with remote ollama

[mhdawson]

I think running with a remote ollama instance will be a relatively common use case.

Having this little bit of extra info would have
saved me time and void me having to hunt through the code and other examples to figure out how to use my remote instance.

Which issue(s) does this pull-request address?

While working through the initial example I had to spend some time figuring out how to use my existing remote ollama instance. I believe this will be common enough that it's worth adding a small section to help people avoid that additional effort when trying out the first example.

Closes: #

Description

Adds the info to the README.md to show how to use a remote ollama instance.

Checklist

• I have read the contributor guide
• Linting passes: yarn lint or yarn lint:fix
• Formatting is applied: yarn format or yarn format:fix
• Unit tests pass: yarn test:unit
• E2E tests pass: yarn test:e2e
• Tests are included
• Documentation is changed or added
• Commit messages and PR title follow conventional commits

[Tomas2D]

IDEs provide type-hints on what you can pass to the class.
This code snippet only bloats the README, but feel free to add this here examples/llms/providers/ollama.ts .

[mhdawson]

Lots of us don't use an IDE but up to you.

When adding to examples/llms/providers/ollama.ts do you mean to add the client options to one of the existing examples or adding a new one with something like "===REMOTE OLLAMA===" ?

[Tomas2D]

Yes, please add it to the example.

===REMOTE OLLAMA== or ===CUSTOM CONFIGURATION=== whatever you deem appropriate 👍🏻

[Tomas2D]

@mhdawson, are you still going to do it?

[mhdawson]

@Tomas2D will do it today, Monday was a holiday in Canada where I am.

[mhdawson]

@Tomas2D updated.

[Tomas2D]

Thank you.