llama-stack-mirror/llama_stack/templates
Ashwin Bharambe fd2aaf4978
fix: use OLLAMA_URL to activate Ollama provider in starter (#2963)
We tried to always keep Ollama enabled. However doing so makes the
provider implementation half-assed -- should it error when it cannot
connect to Ollama or not? What happens during periodic model refresh?
Etc. Instead do the same thing we do for vLLM -- use the `OLLAMA_URL` to
conditionally enable the provider.

## Test Plan

Run `uv run llama stack build --template starter --image-type venv
--run` with and without `OLLAMA_URL` set. Verify using
`llama-stack-client provider list` that ollama is correctly enabled.
2025-07-30 10:11:17 -07:00
..
ci-tests fix: use OLLAMA_URL to activate Ollama provider in starter (#2963) 2025-07-30 10:11:17 -07:00
dell fix: separate build and run provider types (#2917) 2025-07-25 12:39:26 -07:00
meta-reference-gpu fix: separate build and run provider types (#2917) 2025-07-25 12:39:26 -07:00
nvidia feat(starter)!: simplify starter distro; litellm model registry changes (#2916) 2025-07-25 15:02:04 -07:00
open-benchmark feat(openai): add configurable base_url support with OPENAI_BASE_URL env var (#2919) 2025-07-28 10:16:02 -07:00
postgres-demo fix: separate build and run provider types (#2917) 2025-07-25 12:39:26 -07:00
starter fix: use OLLAMA_URL to activate Ollama provider in starter (#2963) 2025-07-30 10:11:17 -07:00
watsonx fix: separate build and run provider types (#2917) 2025-07-25 12:39:26 -07:00
__init__.py Auto-generate distro yamls + docs (#468) 2024-11-18 14:57:06 -08:00
template.py fix: separate build and run provider types (#2917) 2025-07-25 12:39:26 -07:00