Skip to content

docs(proxy): add config-only docker compose setup to quickstart - #707

Open
devin-ai-integration[bot] wants to merge 1 commit into
mainfrom
devin/1785326845-config-only-compose
Open

docs(proxy): add config-only docker compose setup to quickstart#707
devin-ai-integration[bot] wants to merge 1 commit into
mainfrom
devin/1785326845-config-only-compose

Conversation

@devin-ai-integration

Copy link
Copy Markdown
Contributor

Summary

Addresses litellm#35084: the quickstart only offered a Compose path for the Postgres-backed stack, so anyone wanting a pure litellm_config.yaml setup was left with a bare docker run at the bottom of the page.

Adds static/docker-compose-config.yml (served at https://docs.litellm.ai/docker-compose-config.yml, mirroring the existing docker-compose.yml): a single litellm service on the non-database image, mounting ./litellm_config.yaml at /app/config.yaml and passing --config=/app/config.yaml. No Postgres, no LITELLM_SALT_KEY (nothing is stored encrypted in a DB in this mode); provider keys come from the environment, defaulted so Compose does not warn when unset:

environment:
  LITELLM_MASTER_KEY: sk-1234
  OPENAI_API_KEY: ${OPENAI_API_KEY:-}
volumes:
  - ./litellm_config.yaml:/app/config.yaml
command: ["--config=/app/config.yaml"]

The "Running without a database" section now tabs between Docker Compose and docker run. It also corrects a gap the issue implies: verified locally that with no DB the Admin UI login fails with "Authentication Error, Not connected to DB!", so the docs say so explicitly and point at GET /v1/models with the master key as the verification step instead.

Validated by running the new compose file with a litellm_config.yaml: /health/liveliness returns 200 and /v1/models lists the configured model. npm run build passes (only pre-existing warnings).

Link to Devin session: https://app.devin.ai/sessions/c756e335895f4a819d57afcb9f39d215

@devin-ai-integration

Copy link
Copy Markdown
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment, CI, and merge conflict monitoring

@vercel

vercel Bot commented Jul 29, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
litellm Ready Ready Preview, Comment Jul 29, 2026 12:11pm

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant