Make loadBalancer component optional, enabled by default. - #67
Open
gpenaud wants to merge 1 commit into
Open
Conversation
TartanLeGrand
approved these changes
Mar 23, 2026
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
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.
Hi,
I recently tried to install grist as a tiny instance for my association. The loadBalancer component throws me a 413 http error when I try to import a 3.6mb .grist file, despite my client_max_body_size like configuration. I'm currently using traefik as ingress controller.
I also had 404 errors. Instead of tryin to debug these issues, i wonder myself what was the purpose of thoses loadbalancers ? I do not get that.
Maybe in case of huge deployment, as is probably the one at dirnum.
My PR concerns a proposal to disable the LB if those are not required. Probably more fit for tiny organizations.
I'd be happy to discuss it further with you.