docs: Document AWS_ENDPOINT_URL for S3 configuration #285
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit updates the documentation related to S3 storage configuration to include the `AWS_ENDPOINT_URL` environment variable. This variable was introduced in PR [#6431](danny-avila/LibreChat#6431) to allow users to specify a custom endpoint URL for S3 connections, but the documentation is not update. The changes include: - Adding a description for `AWS_ENDPOINT_URL`, clarifying its purpose and indicating that it's optional.
|
@lensfa-lzd is attempting to deploy a commit to the LibreChat's projects Team on Vercel. A member of the Team first needs to authorize it. |
danny-avila
approved these changes
Apr 25, 2025
danny-avila
pushed a commit
that referenced
this pull request
Apr 25, 2025
This commit updates the documentation related to S3 storage configuration to include the `AWS_ENDPOINT_URL` environment variable. This variable was introduced in PR [#6431](danny-avila/LibreChat#6431) to allow users to specify a custom endpoint URL for S3 connections, but the documentation is not update. The changes include: - Adding a description for `AWS_ENDPOINT_URL`, clarifying its purpose and indicating that it's optional.
danny-avila
added a commit
that referenced
this pull request
Apr 25, 2025
* Create optimizing-rag-performance-in-librechat.md This PR adds a detailed blog post written by Henk van Ess that covers how to optimize Retrieval-Augmented Generation (RAG) performance in LibreChat. The guide walks through: Improving vector database performance (PostgreSQL/pgvector) Chunking strategies (CHUNK_SIZE / CHUNK_OVERLAP) Embedding provider options (OpenAI, Azure, Ollama) Retrieval settings (RAG_API_TOP_K) Monitoring and server resource tips It's designed to help developers fine-tune their LibreChat instances for speed and quality. All content is based on hands-on testing and is Markdown-formatted for blog use. Looking forward to feedback — happy to revise if needed! * Update optimizing-rag-performance-in-librechat.md This PR adds a detailed blog post written by Henk van Ess that covers how to optimize Retrieval-Augmented Generation (RAG) performance in LibreChat. The guide walks through: Improving vector database performance (PostgreSQL/pgvector) Chunking strategies (CHUNK_SIZE / CHUNK_OVERLAP) Embedding provider options (OpenAI, Azure, Ollama) Retrieval settings (RAG_API_TOP_K) Monitoring and server resource tips It's designed to help developers fine-tune their LibreChat instances for speed and quality. All content is based on hands-on testing and is Markdown-formatted for blog use. Looking forward to feedback — happy to revise if needed! * Optimizing-rag-performance-in-librechat.md This PR adds a detailed blog post written by Henk van Ess that covers how to optimize Retrieval-Augmented Generation (RAG) performance in LibreChat. The guide walks through: Improving vector database performance (PostgreSQL/pgvector) Chunking strategies (CHUNK_SIZE / CHUNK_OVERLAP) Embedding provider options (OpenAI, Azure, Ollama) Retrieval settings (RAG_API_TOP_K) Monitoring and server resource tips It's designed to help developers fine-tune their LibreChat instances for speed and quality. All content is based on hands-on testing and is Markdown-formatted for blog use. Looking forward to feedback — happy to revise if needed! * docs: Document AWS_ENDPOINT_URL for S3 configuration (#285) This commit updates the documentation related to S3 storage configuration to include the `AWS_ENDPOINT_URL` environment variable. This variable was introduced in PR [#6431](danny-avila/LibreChat#6431) to allow users to specify a custom endpoint URL for S3 connections, but the documentation is not update. The changes include: - Adding a description for `AWS_ENDPOINT_URL`, clarifying its purpose and indicating that it's optional. * 🎨 feat: Adds Image Gen Docs, fix broken links, usage stats, missing .env vars, formatting issues, bump Next.js (#288) * docs: enhance API key setup instructions for clarity * docs: update section title for API key setup clarity * docs: add comprehensive guide for OpenAI image generation and editing tools * docs: clarify Stable Diffusion section and update link in Image Generation overview * docs: add Flux cloud generator configuration details and environment variables * fix: Firebase CDN configuration link * docs: enhance fileStrategy section with CDN options and notes * docs: enhance Image Generation section with improved structure and pricing details * docs: add Code Interpreter section with environment variable details and enterprise plan notes * fix: formatting * chore: bump next * fix: correct markdown formatting for artifact example in agents documentation * docs: add deprecation notices for tools, plugins, presets, and enhance image generation section * feat: implement GitHub stats API and update Usage component to fetch stars dynamically * fix: update Docker pulls value in Usage component * 🫙 fix: Azure Blob Storage Documentation (#289) * fix: Update fileStrategy option to use "azure_blob" in configuration docs * fix: Update CDN documentation for Azure Blob Storage and improve navigation * fix: Remove Hetzner reference from deployment comparison, closes #271 * fix: Update RAG API documentation for clarity on feature availability, closes #249 * feat: Update demo images (#290) * docs: Clarify configuration file usage and API key settings in documentation, closes #238 * fix: Add instructions to remove existing Docker images for local and remote setups * 🌊 docs: Flux (#203) * feat: Enhance documentation for Flux and related tools, including setup instructions and parameters * docs: Update image generation documentation with additional notes on output handling and MCP server format * feat: Add blog post on optimizing RAG performance in LibreChat with accompanying image * chore: Remove unused image for RAG performance blog post --------- Co-authored-by: Henk van Ess <[email protected]> Co-authored-by: lensfa <[email protected]> Co-authored-by: Marco Beretta <[email protected]> Co-authored-by: heptapod <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit updates the documentation related to S3 storage configuration to include the
AWS_ENDPOINT_URLenvironment variable. This variable was introduced in PR #6431 to allow users to specify a custom endpoint URL for S3 connections, but the documentation is not update.The changes include:
AWS_ENDPOINT_URL, clarifying its purpose and indicating that it's optional.