GitLab

update faq

update faq

Co-authored-by: Jeffrey Morgan <jmorganca@gmail.com>

Log Analysis Example 

Co-authored-by: Jeffrey Morgan <jmorganca@gmail.com>

On debian 12, sources definitions have moved from
/etc/apt/sources.list to /etc/apt/sources.list.d/debian.sources

Add example using JSON format output

create remote models

Co-authored-by: Bruce MacDonald <brucewmacdonald@gmail.com>

Co-authored-by: Bruce MacDonald <brucewmacdonald@gmail.com>

* faq: does ollama share my prompts
Signed-off-by: Matt Williams <m@technovangelist.com>

* faq: ollama and openai
Signed-off-by: Matt Williams <m@technovangelist.com>

* faq: vscode plugins
Signed-off-by: Matt Williams <m@technovangelist.com>

* faq: send a doc to Ollama
Signed-off-by: Matt Williams <m@technovangelist.com>

* extra spacing
Signed-off-by: Matt Williams <m@technovangelist.com>

* Update faq.md

* Update faq.md

---------
Signed-off-by: Matt Williams <m@technovangelist.com>
Co-authored-by: Michael <mchiang0610@users.noreply.github.com>

replace go-humanize with format.HumanBytes

Previously, `ollama run` treated a non-terminal stdin (such as `ollama run model < file`) as containing one prompt per line. To run inference on a multi-line prompt, the only non-API workaround was to run `ollama run` interactively and wrap the prompt in `"""..."""`.

Now, `ollama run` treats a non-terminal stdin as containing a single prompt. For example, if `myprompt.txt` is a multi-line file, then `ollama run model < myprompt.txt` would treat `myprompt.txt`'s entire contents as the prompt.
Co-authored-by: Quinn Slack <quinn@slack.org>

This field is optional and should be under the `Advanced parameters` header