Commit graph

5 commits

Author SHA1 Message Date
ryan-crabbe-berri
c8e0f2ddb4 docs: stop advertising sk-1234 as the master key in shipped configs and examples
Shipped proxy configs now read general_settings.master_key from
os.environ/LITELLM_MASTER_KEY, the .env examples ship a blank value with
the openssl generate command above it, and READMEs, the missing env vars
page and Admin UI code snippets show a generate command or the
<your-master-key> placeholder instead of the literal sk-1234

The two CircleCI docker runs that mount proxy_server_config.yaml and
oai_misc_config.yaml now pass LITELLM_MASTER_KEY so their runtime key is
unchanged
2026-09-19 12:59:48 -07:00
ishaan-jaff
357c6c56bd Revert "build(Dockerfile): move prisma build to dockerfile"
This reverts commit 2741835605.
2024-01-06 09:51:44 +05:30
Krish Dholakia
b4901e6dea
Update .env.example 2024-01-05 19:14:48 +05:30
Krrish Dholakia
2741835605 build(Dockerfile): move prisma build to dockerfile
Seems to solve - https://github.com/BerriAI/litellm/issues/1321
2024-01-05 19:03:41 +05:30
Krrish Dholakia
14e501845f fix(proxy_server.py): add support for setting master key via .env 2024-01-03 15:10:25 +05:30