Repository navigation
🛠️ docs: Correct the Configuration Guides Against LibreChat - #864
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1e7095acfd
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ['IMPORT_VIOLATION_SCORE', 'integer', 'Score for import conversation violations.','IMPORT_VIOLATION_SCORE=0'], | ||
| ['FORK_VIOLATION_SCORE', 'integer', 'Score for conversation fork violations.','FORK_VIOLATION_SCORE=0'], |
There was a problem hiding this comment.
Restore the import and fork violation scores
These examples now set both violation scores to 0, while the environment reference still specifies IMPORT_VIOLATION_SCORE=1 and FORK_VIOLATION_SCORE=1 in content/docs/configuration/dotenv.mdx:2400-2409. An operator copying this table would disable ban-score accumulation for repeated import and fork violations, so the documented values need to match the actual defaults.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Fixed in f952f51: both examples are back to 1 with 'Defaults to 1 when unset' (logViolation's default score when the variable is undefined).
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 05420f9fec
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| services: | ||
| api: | ||
| environment: | ||
| - RAG_API_URL=http://host.docker.internal:8000 |
There was a problem hiding this comment.
Add the Linux host gateway to the RAG override
On Linux Docker Engine, this example points the api container at host.docker.internal without defining that hostname, so a RAG API running on the Docker host remains unreachable. Docker provides this name automatically on macOS and Windows, but its Compose networking documentation requires an extra_hosts entry such as host.docker.internal:host-gateway on Linux; add that mapping under api, as the Ollama example later on this page already does for rag_api.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Fixed in ac7c775: the override maps host.docker.internal:host-gateway, with a note that Linux needs it.
|
|
||
| ### One provider per service | ||
|
|
||
| Configure exactly one provider block under `speech.stt` and exactly one under `speech.tts`. If more than one is set, requests fail with the error "Multiple providers are set. Please set only one provider." |
There was a problem hiding this comment.
Allow deployments to configure only one speech service
When an operator wants server-side STT with browser TTS, or server-side TTS with browser STT, this says they must configure provider blocks for both services even though either section can be omitted. The page's own STT-only and TTS-only examples demonstrate that these are independent; the actual restriction described by the following error is at most one provider under each section that is present, not exactly one provider under both.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Fixed in ac7c775: each section takes at most one provider and either can be omitted.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ac7c775766
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
b9f6ad3 to
9082fe1
Compare
9082fe1 to
b47d0b6
Compare
📦 Next.js Bundle Analysis for librechat.aiThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
Check the authentication, CDN, Redis, logging, metrics, Meilisearch, RAG API, moderation, token usage, speech, banner, provider and tool guides against the LibreChat source, fix wrong variables, defaults and behavior, and repair the two broken anchors on the metrics and RAG API pages.
The bundled compose files set RAG_API_URL on the api service, which takes precedence over .env, so adding it to .env does not redirect a Docker deployment. Show the docker-compose.override.yml form instead.
…ults The import and fork limiters are always active, so the LIMIT_IMPORT_* and LIMIT_FORK_* switches did nothing. IMPORT_VIOLATION_SCORE and FORK_VIOLATION_SCORE default to 1 when unset.
The RAG override needs host.docker.internal mapped on Linux. Each speech section takes at most one provider and either can be omitted. The Argon region rule applies to Vertex AI only; the Gemini API serves it too.
b47d0b6 to
23df3d0
Compare
📦 Next.js Bundle Analysis for librechat.aiThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
Summary
Checks the configuration guides (authentication providers and LDAP, CDN, Redis, logging, metrics, Meilisearch, RAG API, moderation, token usage, speech, banner, preconfigured providers and tools) against the LibreChat source. It fixes variables, defaults and behavior that had drifted, and repairs the broken anchors on the metrics and RAG API pages.
Stacked on #863; review only this PR's diff.
Change Type
Testing
dev, then rechecked by a second independent passmain)Checklist