mirror of
https://github.com/meta-llama/llama-stack.git
synced 2025-12-16 20:59:27 +00:00
73e33fb747
The Self-Hosted Distribution documentation contain steps to start llama server via conda environment. If the user generates conda environment using llaama build command and template, it generate an environment with name of the distribution and not defaulyt name of local as per the example run yaml file. It will thereore fail when user tried to run the server. This PR fixes the conda env name in the run yaml file. Signed-off-by: Martin Hickey <martin.hickey@ie.ibm.com>
46 lines
1.1 KiB
YAML
46 lines
1.1 KiB
YAML
version: '2'
|
|
built_at: '2024-11-01T17:40:45.325529'
|
|
image_name: local
|
|
name: bedrock
|
|
docker_image: null
|
|
conda_env: bedrock
|
|
apis:
|
|
- shields
|
|
- agents
|
|
- models
|
|
- memory
|
|
- memory_banks
|
|
- inference
|
|
- safety
|
|
providers:
|
|
inference:
|
|
- provider_id: bedrock0
|
|
provider_type: remote::bedrock
|
|
config:
|
|
aws_access_key_id: <AWS_ACCESS_KEY_ID>
|
|
aws_secret_access_key: <AWS_SECRET_ACCESS_KEY>
|
|
aws_session_token: <AWS_SESSION_TOKEN>
|
|
region_name: <AWS_REGION>
|
|
memory:
|
|
- provider_id: meta0
|
|
provider_type: inline::meta-reference
|
|
config: {}
|
|
safety:
|
|
- provider_id: bedrock0
|
|
provider_type: remote::bedrock
|
|
config:
|
|
aws_access_key_id: <AWS_ACCESS_KEY_ID>
|
|
aws_secret_access_key: <AWS_SECRET_ACCESS_KEY>
|
|
aws_session_token: <AWS_SESSION_TOKEN>
|
|
region_name: <AWS_REGION>
|
|
agents:
|
|
- provider_id: meta0
|
|
provider_type: inline::meta-reference
|
|
config:
|
|
persistence_store:
|
|
type: sqlite
|
|
db_path: ~/.llama/runtime/kvstore.db
|
|
telemetry:
|
|
- provider_id: meta0
|
|
provider_type: inline::meta-reference
|
|
config: {}
|