phoenix/litellm-mirror
0
0
Fork 1
mirror of https://github.com/BerriAI/litellm.git synced 2025-04-26 19:24:27 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

doc using gcs bucket config.yaml

Browse source
This commit is contained in:
Ishaan Jaff 2024-08-30 10:44:41 -07:00
parent c60125d7be
commit a36edbcd4c
1 changed files with 29 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

31
docs/my-website/docs/proxy/deploy.md
View file

@ -705,11 +705,36 @@ docker run ghcr.io/berriai/litellm:main-latest \
Provide an ssl certificate when starting litellm proxy server
### 3. Providing LiteLLM config.yaml file as a s3 Object/url
### 3. 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
LiteLLM Proxy will read your config.yaml from an s3 Bucket or GCS Bucket
<Tabs>
<TabItem value="gcs" label="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 s3
```shell
docker run --name litellm-proxy \
-e DATABASE_URL=<database_url> \
-e LITELLM_CONFIG_BUCKET_NAME=<bucket_name> \
-e LITELLM_CONFIG_BUCKET_OBJECT_KEY="<object_key>> \
-p 4000:4000 \
ghcr.io/berriai/litellm-database:main-latest --detailed_debug
```
</TabItem>
<TabItem value="s3" label="s3">
Set the following .env vars
```shell
@ -727,6 +752,8 @@ docker run --name litellm-proxy \
-p 4000:4000 \
ghcr.io/berriai/litellm-database:main-latest
```
</TabItem>
</Tabs>
## Platform-specific Guide