Hey Hargovind, I don't find that exact passage in the idea list <http://openwisp.org/gsoc/ideas-2018.html>, I find instead:
*integrate django-freeradius in the rest of the openwisp2 ecosystem; we will create a new wrapper python package (openwisp-radius) that will wrap django-freeradius and add multitenancy features to it, similarly to how openwisp-controller wraps django-netjsonconfig or openwisp-network-topology wraps django-netjsongraph* To understand this point in practice, take a look at how openwisp-controller basically wraps and extends other base modules: - https://github.com/openwisp/openwisp-controller/blob/master/openwisp_controller/config/models.py - https://github.com/openwisp/openwisp-controller/blob/master/openwisp_controller/config/controller/views.py - https://github.com/openwisp/openwisp-controller/blob/master/openwisp_controller/pki/admin.py If you have further questions, please don't hesitate. Federico On Sun, Mar 18, 2018 at 10:18 AM Hargovind Singh Arora < [email protected]> wrote: > Hey Fed and Rohith I wanted to know that what do you mean about this in > the Django-freeradius project - "integrate Django-freeradius in the rest of > the openwisp2 ecosystem ForeignKey/PrimaryKey in the model". Can you please > explain more? > > > -- > You received this message because you are subscribed to the Google Groups > "OpenWISP" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "OpenWISP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
