9 commits

Author	SHA1	Message	Date
ryan-crabbe-berri	fe480533e8	feat(proxy)!: refuse to start with an unset, empty, or publicly known master key ... The proxy used to boot with no master key (every request accepted without authentication) and with sk-1234, the key every example used. It now stops at startup, before it connects to the database, and prints how to fix it: where the bad key came from, a copy-pastable command that generates a secure key, and, when the public key is also encrypting a database, a link to the rotation guide general_settings.dangerously_allow_unsafe_proxy: true or LITELLM_DANGEROUSLY_ALLOW_UNSAFE_PROXY=true starts the proxy anyway, for local development. CI and test boots that rely on sk-1234 or on no key set it BREAKING CHANGE: deployments with no master key, an empty one, or sk-1234 no longer start until they set a real key or opt in to the override	2026-09-19 13:44:00 -07:00
Krrish Dholakia	f8a82f5779	build(render.yaml): fix health check route	2024-05-24 09:45:28 -07:00
Krrish Dholakia	cf4ca0ef64	build(render.yaml): fixes with redhat extension	2024-05-24 09:33:24 -07:00
Krrish Dholakia	3ec0f8f591	build(render.yaml): render.yaml fixes	2024-05-24 09:28:57 -07:00
Krrish Dholakia	2b865ec12c	build(render.yaml): fix image name	2024-05-24 09:21:36 -07:00
Krrish Dholakia	4a63411f6c	build(render.yaml): add render.yaml to github	2024-05-24 09:15:20 -07:00
ishaan-jaff	cbc358ef77	(docs) proxy: Render deploys	2023-11-30 09:21:07 -08:00
Krish Dholakia	bcc869402e	update render.yaml	2023-10-21 17:43:06 -07:00
Krish Dholakia	bd99a8303b	Create render.yaml	2023-10-21 17:38:12 -07:00