Skip to content

Conversation

@WhammyLeaf
Copy link
Contributor

@WhammyLeaf WhammyLeaf commented Oct 16, 2025

This PR inlines the charts for mongodb so that librechat will not have a dependency on bitnami which has become unreliable after their recent transition into commercial offerings.

I know the amount of code is alot. It may be better to host the code in a registry that librechat owns long term. But for now this works.

Pull Request Template

⚠️ Before Submitting a PR, Please Review:

  • Please ensure that you have thoroughly read and understood the Contributing Docs before submitting your Pull Request.

⚠️ Documentation Updates Notice:

  • Kindly note that documentation updates are managed in this repository: librechat.ai

Summary

Please provide a brief summary of your changes and the related issue. Include any motivation and context that is relevant to your changes. If there are any dependencies necessary for your changes, please list them here.

Change Type

Please delete any irrelevant options.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update
  • Translation update

Testing

Please describe your test process and include instructions so that we can reproduce your test. If there are any important variables for your testing configuration, list them here.

Test Configuration:

Checklist

Please delete any irrelevant options.

  • My code adheres to this project's style guidelines
  • I have performed a self-review of my own code
  • I have commented in any complex areas of my code
  • I have made pertinent documentation changes
  • My changes do not introduce new warnings
  • I have written tests demonstrating that my changes are effective or that my feature works
  • Local unit tests pass with my changes
  • Any changes dependent on mine have been merged and published in downstream modules.
  • A pull request for updating the documentation has been submitted.
@danny-avila danny-avila marked this pull request as draft October 18, 2025 08:12
@danny-avila
Copy link
Owner

Thanks for raising this concern about Bitnami's transition. However, inlining 14,500+ lines of chart code isn't the right solution here.

The good news: Bitnami's Helm chart source code remains open source and actively maintained on GitHub under Apache 2 license. Only the pre-packaged OCI artifacts are affected.

Better alternatives:

  1. Use alternative providers:

    • Chainguard has forked Bitnami charts with drop-in compatibility: oci://cgr.dev/chainguard/mongodb
    • Percona MongoDB: https://percona.github.io/percona-helm-charts/
  2. Override image sources in the existing chart:

mongodb:
  image:
    registry: cgr.dev
    repository: chainguard/mongodb

Inlining makes the chart unmaintainable and harder to update.

References:

@WhammyLeaf
Copy link
Contributor Author

@danny-avila

First of all, I agree that inlining 15 K lines of code is not ideal. As for your suggestions, I am not sure either is a good option.

Chainguard does not open source their charts and their helm chart documentation is not very good. This seems like another commercial company that may do a bitnami rug pull at any time.

Percona is also a commercial company but their charts are open sourced I think. However, I dont think their chart is a drop in replacement. Their chart is specifically made for their own MongoDB offering (which is built on top of the community version). It is free but the chart is using an operator so the setup is different.

In general: there are very few, if any, alternatives to bitnami, which are both drop-in and open-sourced. The only I could really find is this: https://github.com/CloudPirates-io/helm-charts. Their MongoDB chart might work well for LibreChat, although from what I can tell it is somewhat barebones.

Unless you want to wait until the ecosystem has matured and a full-fledged open-sourced alternative is available, I think the best solution is for you to host a MongoDB chart yourself. I found this tool from bitnami, which supposedly allows you to easily sync charts to your own registry. That might be useful for you, although I have not tried it myself.

@WhammyLeaf WhammyLeaf force-pushed the inline-mongo-db-chart branch 2 times, most recently from 9e5bebd to 2dd3359 Compare October 26, 2025 18:00
@WhammyLeaf WhammyLeaf force-pushed the inline-mongo-db-chart branch from ce989a3 to 76a845d Compare October 31, 2025 15:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants