From 60baa65e0ec4827d27c3b15c14a4f921b1e66121 Mon Sep 17 00:00:00 2001 From: Krrish Dholakia Date: Wed, 9 Oct 2024 09:07:38 -0700 Subject: [PATCH] docs(configs.md): add litellm config / s3 bucket object info in configs.md --- docs/my-website/docs/proxy/configs.md | 50 +++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) diff --git a/docs/my-website/docs/proxy/configs.md b/docs/my-website/docs/proxy/configs.md index af29f13ce..e1f929c5a 100644 --- a/docs/my-website/docs/proxy/configs.md +++ b/docs/my-website/docs/proxy/configs.md @@ -882,3 +882,53 @@ $ litellm ``` +### Providing LiteLLM config.yaml file as a s3, GCS Bucket Object/url + +Use this if you cannot mount a config file on your deployment service (example - AWS Fargate, Railway etc) + +LiteLLM Proxy will read your config.yaml from an s3 Bucket or GCS Bucket + + + + +Set the following .env vars +```shell +LITELLM_CONFIG_BUCKET_TYPE = "gcs" # set this to "gcs" +LITELLM_CONFIG_BUCKET_NAME = "litellm-proxy" # your bucket name on GCS +LITELLM_CONFIG_BUCKET_OBJECT_KEY = "proxy_config.yaml" # object key on GCS +``` + +Start litellm proxy with these env vars - litellm will read your config from GCS + +```shell +docker run --name litellm-proxy \ + -e DATABASE_URL= \ + -e LITELLM_CONFIG_BUCKET_NAME= \ + -e LITELLM_CONFIG_BUCKET_OBJECT_KEY="> \ + -e LITELLM_CONFIG_BUCKET_TYPE="gcs" \ + -p 4000:4000 \ + ghcr.io/berriai/litellm-database:main-latest --detailed_debug +``` + + + + + +Set the following .env vars +```shell +LITELLM_CONFIG_BUCKET_NAME = "litellm-proxy" # your bucket name on s3 +LITELLM_CONFIG_BUCKET_OBJECT_KEY = "litellm_proxy_config.yaml" # object key on s3 +``` + +Start litellm proxy with these env vars - litellm will read your config from s3 + +```shell +docker run --name litellm-proxy \ + -e DATABASE_URL= \ + -e LITELLM_CONFIG_BUCKET_NAME= \ + -e LITELLM_CONFIG_BUCKET_OBJECT_KEY="> \ + -p 4000:4000 \ + ghcr.io/berriai/litellm-database:main-latest +``` + + \ No newline at end of file