openwisp
Here are 18 public repositories matching this topic...
Fix statement condition on "Install custom OpenWISP 2 Python packages" task in pip.yml:
TASK [openwisp.openwisp2 : Install custom OpenWISP 2 Python packages] **********
[DEPRECATION WARNING]: evaluating 'openwisp2_python_packages' as a bare
variable, this behaviour will go away and you might need to add |bool to the
expression in the future. Also see CONDITIONAL_BARE_VARS configurReserved for Google Code-In 2020.
Depends on openwisp/openwisp-utils#98.
Use the decorators mentioned in the issue linked above to silence the output of noisy tests.
I just noticed the template tags featue (#34) is not mentioned in the README.
It would be appropiate to mention the config option in the beginning of the README as well as dedicate a brief section to explain how it works.
Reserved for Google Code-In 2020.
Depends on openwisp/openwisp-utils#98.
Use the decorators mentioned in the issue linked above to silence the output of noisy tests.
In this test utility code (which is reused across openwisp modules):
The test expects the permission of the operator to be defined as a class attribute.
This is obsolete, because in more recent versions of OpenWISP we added two default auth.Group instances: oper
Check comment here: openwisp/docker-openwisp#101 (comment)
-
Updated
Jun 28, 2020 - Python
-
Updated
Oct 23, 2018 - Python
-
Updated
Feb 20, 2017 - Shell
The best practices in security suggest that a cluster & it's nodes should only be granted access to GCP services that are to be used by the application, hence, we should create a service account for the same and assign it to the cluster.
The best practices suggest that each application should have it's own isolated namespace.
We should create a namespace for openwisp and move it away from default namespace!
Improve this page
Add a description, image, and links to the openwisp topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the openwisp topic, visit your repo's landing page and select "manage topics."
The freeradius configuration documentation page assumes the configuration is being done to set up for a captive portal wifi setup, other configurations like WPA2 Enterprise are implemented differently so we need to make this more explicit.