Settings
Note
If you're unsure about what "Django settings" are, you can refer to How to Edit Django Settings in OpenWISP for guidance.
OPENWISP_NETWORK_TOPOLOGY_PARSERS
type: |
|
default: |
|
Additional custom netdiff parsers.
OPENWISP_NETWORK_TOPOLOGY_SIGNALS
type: |
|
default: |
|
String representing Python module to import on initialization.
Useful for loading Django signals or to define custom behavior.
OPENWISP_NETWORK_TOPOLOGY_TIMEOUT
type: |
|
default: |
|
Timeout when fetching topology URLs.
OPENWISP_NETWORK_TOPOLOGY_LINK_EXPIRATION
type: |
|
default: |
|
If a link is down for more days than this number, it will be deleted by
the update_topology
management command.
Setting this to False
will disable this feature.
OPENWISP_NETWORK_TOPOLOGY_NODE_EXPIRATION
type: |
|
default: |
|
If a node has not been modified since the days specified and if it has no
links, it will be deleted by the update_topology
management command.
This depends on OPENWISP_NETWORK_TOPOLOGY_LINK_EXPIRATION
being
enabled. Replace False
with an integer to enable the feature.
OPENWISP_NETWORK_TOPOLOGY_VISUALIZER_CSS
type: |
|
default: |
|
Path of the visualizer css file. Allows customization of css according to user's preferences.
OPENWISP_NETWORK_TOPOLOGY_API_URLCONF
type: |
|
default: |
|
Use the urlconf
option to change receive API URL to point to another
module, example, myapp.urls
.
OPENWISP_NETWORK_TOPOLOGY_API_BASEURL
type: |
|
default: |
|
If you have a separate instance of the OpenWISP Network Topology API on a
different domain, you can use this option to change the base of the URL,
this will enable you to point all the API URLs to your API server's
domain, example value: https://api.myservice.com
.
OPENWISP_NETWORK_TOPOLOGY_API_AUTH_REQUIRED
type: |
|
default: |
|
When enabled, the API endpoints will only allow authenticated users who have the necessary permissions to access the objects which belong to the organizations the user manages.
OPENWISP_NETWORK_TOPOLOGY_WIFI_MESH_INTEGRATION
type: |
|
default: |
|
When enabled, network topology objects will be automatically created and updated based on the WiFi mesh interfaces peer information supplied by the monitoring agent.
Note
The network topology objects are created using the device monitoring data collected by OpenWISP Monitoring. Thus, it requires integration with OpenWISP Controller and OpenWISP Monitoring to be enabled in the Django project.