fix: improve Redis and health check reliability - #12
Merged
Merged
Conversation
Collaborator
|
That is correct patching, Thank you |
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.
Summary
docs.nestjs.comrequest from the application health check.Why
BullMQ was connecting to the password-protected Redis instance without authentication,
resulting in
NOAUTH Authentication requirederrors when it issued Redis commands.The health endpoint also depended on
docs.nestjs.com, causing the API to reportunhealthy when external DNS/connectivity was unavailable.
Both changes make the development environment more reliable without changing the
application's core functionality.