-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Redis Unix sockets #15962
Comments
From previous tickets: Proposed FunctionalityImplement unix-socket support for Redis cache and webhook Use CaseWhen Redis is installed on the same Server as netbox, then the possible usage of unix sockets for redis would be nice. When using unix sockets, there is no need for localhost loopback with the whole IP-Stack. The usage with unix sockets can improve the performance too (even if it doesn't matter). Database ChangesNo DB-Changes needed. Just some small changes in settings.py and configuration.py |
Hello, I have a patch that I'm willing to upstream that was made to support Redis Unix sockets. (Note: the linked patch also modifies This patch defines new REDIS = {
"tasks": {"URL": "unix:///run/redis-netbox/redis.sock?db=0", "SSL": False},
"caching": {"URL": "unix:///run/redis-netbox/redis.sock?db=1", "SSL": False},
} In the case of the tasks Redis database, if and only if In the case of the caching Redis database, This should be backwards compatible. |
@minijackson sounds good, I'll assign this to you for a PR. Thanks! |
@minijackson are you still interested in working on this? |
Yes, sorry. Went on a quick vacation, then that task fell through the cracks. I'll submit a PR soon. |
* Fixes #15962: support Redis Unix sockets * Clean up language & remove obsolete note --------- Co-authored-by: Jeremy Stretch <jstretch@netboxlabs.com>
NetBox version
3.7.5
Feature type
Change to existing functionality
Proposed functionality
Support Redis connectivity through Unix sockets
Use case
Binding to Redis servers on localhost or sidecars without exposing a TCP listener.
Database changes
No response
External dependencies
No response
The text was updated successfully, but these errors were encountered: