You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Fixesnetbox-community#15962: support Redis Unix sockets
* Clean up language & remove obsolete note
---------
Co-authored-by: Jeremy Stretch <[email protected]>
Copy file name to clipboardExpand all lines: docs/configuration/required-parameters.md
+15-5Lines changed: 15 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -94,15 +94,25 @@ REDIS = {
94
94
}
95
95
```
96
96
97
-
!!! note
98
-
If you are upgrading from a NetBox release older than v2.7.0, please note that the Redis connection configuration
99
-
settings have changed. Manual modification to bring the `REDIS` section inline with the above specification is
100
-
necessary
101
-
102
97
!!! warning
103
98
It is highly recommended to keep the task and cache databases separate. Using the same database number on the
104
99
same Redis instance for both may result in queued background tasks being lost during cache flushing events.
105
100
101
+
### UNIX Socket Support
102
+
103
+
Redis may alternatively be configured by specifying a complete URL instead of individual components. This approach supports the use of a UNIX socket connection. For example:
104
+
105
+
```python
106
+
REDIS= {
107
+
'tasks': {
108
+
'URL': 'unix:///run/redis-netbox/redis.sock?db=0'
109
+
},
110
+
'caching': {
111
+
'URL': 'unix:///run/redis-netbox/redis.sock?db=1'
112
+
},
113
+
}
114
+
```
115
+
106
116
### Using Redis Sentinel
107
117
108
118
If you are using [Redis Sentinel](https://redis.io/topics/sentinel) for high-availability purposes, there is minimal
0 commit comments