mirror of
https://github.com/meta-llama/llama-stack.git
synced 2025-12-23 02:52:25 +00:00
236a670fc1
in #2637, I combined the run and build config provider types to both use `Provider` since this includes a provider_id, a user must now specify this when writing a build yaml. This is not very clear because all a user should care about upon build is the code to be installed (the module and the provider_type) introduce `BuildProvider` and fixup the parts of the code impacted by this Signed-off-by: Charlie Doern <cdoern@redhat.com>
26 lines
770 B
YAML
26 lines
770 B
YAML
version: 2
|
|
distribution_spec:
|
|
description: Quick start template for running Llama Stack with several popular providers
|
|
providers:
|
|
inference:
|
|
- provider_type: remote::vllm
|
|
- provider_type: inline::sentence-transformers
|
|
vector_io:
|
|
- provider_type: remote::chromadb
|
|
safety:
|
|
- provider_type: inline::llama-guard
|
|
agents:
|
|
- provider_type: inline::meta-reference
|
|
telemetry:
|
|
- provider_type: inline::meta-reference
|
|
tool_runtime:
|
|
- provider_type: remote::brave-search
|
|
- provider_type: remote::tavily-search
|
|
- provider_type: inline::rag-runtime
|
|
- provider_type: remote::model-context-protocol
|
|
image_type: conda
|
|
image_name: postgres-demo
|
|
additional_pip_packages:
|
|
- asyncpg
|
|
- psycopg2-binary
|
|
- sqlalchemy[asyncio]
|