Added Openrouter Support & chore: update .gitignore and Docker configurations - #979
Added Openrouter Support & chore: update .gitignore and Docker configurations#979Capp3 wants to merge 1 commit into
Conversation
- Added *.override.yml to .gitignore to exclude override files from version control. - Removed port mapping from docker-compose.yml to simplify service configuration. - Updated Dockerfile to install packages without pinned versions for better flexibility. - Enhanced OpenAI client creation in main.go and llm_provider.go to conditionally append base URL from environment variable.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
💤 Files with no reviewable changes (1)
📝 WalkthroughWalkthroughThis PR adds conditional OpenAI base URL support to the LLM client initialization, allowing configuration overrides for non-Azure OpenAI deployments. It also updates Docker and compose configurations by unpinning Alpine package versions, removing the port binding from the app service, and adding a git ignore rule for override configuration files. ChangesOpenAI Base URL Configuration
Infrastructure and Deployment Updates
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Actionable comments posted: 0 |
Six open issues (#864, #903, #908, #979, #1041, #830) request providers that already work today via LLM_PROVIDER=openai plus OPENAI_BASE_URL. One of them arrived as a PR adding a hardcoded per-vendor branch that was functionally identical to those two settings — and strictly less capable, having dropped the Azure and base-URL handling the shared path has. That many duplicate requests is a documentation failure, not six missing features: OPENAI_BASE_URL was mentioned only in one table row, so nobody looking for "does it support X" found it. Adds docs/openai_compatible_providers.md with copy-pasteable configs for OpenRouter, LM Studio, vLLM, LiteLLM, llama.cpp and Azure, the three things people get wrong (missing /v1, vendor-specific model names, placeholder keys for local servers), a troubleshooting section mapping the recurring errors to their causes (#1035, #791, #862, #1003), and the rationale for not adding per-vendor branches. Surfaces it from a new README section and the env-var table, and notes that Ollama should use its native provider rather than the shim, since the shim exposes neither OLLAMA_CONTEXT_LENGTH nor OLLAMA_THINK. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
icereed
left a comment
There was a problem hiding this comment.
🤖 Automated review — produced by Claude Code running in the maintainer's repo checkout and posted under the maintainer's account, not hand-written by them.
Declining the OpenRouter provider branch — because OpenRouter already works, and has all along:
environment:
LLM_PROVIDER: "openai"
OPENAI_BASE_URL: "https://openrouter.ai/api/v1"
OPENAI_API_KEY: "sk-or-..."
LLM_MODEL: "anthropic/claude-sonnet-4-5"paperless-gpt even already sends an X-Title: paperless-gpt header, which is the attribution header OpenRouter uses for its rankings.
That five separate issues and PRs asked for providers that already ship (#864, #903, #908, #1041, #830) is a documentation failure on our side, not five missing features — OPENAI_BASE_URL was mentioned only in one row of a 100-row table. #1060 fixes that with docs/openai_compatible_providers.md, where OpenRouter is the first worked example.
Two other things about this PR regardless of the provider question:
- It's based on your
mainand conflicts now;mainhas moved a lot since May. - It bundles unrelated
.gitignoreand Docker configuration changes with the provider addition. Those would need to be a separate PR anyway so they can be judged on their own — if any of them fix a real problem you hit, please do open that separately, it's easier to say yes to.
Closing recommendation rather than a close, in case the Docker changes are worth keeping.
Summary by CodeRabbit
Release Notes
Configuration
Chores