Hey, On Tue, Mar 28, 2017 at 9:06 PM Arpit Nandwani <[email protected]> wrote:
In this project we aim to reimplement the basic, "core" features of OWUMS in a new lightweight django <https://www.djangoproject.com/> reusable app so it can fit with the emergent OpenWISP 2 ecosystem. Other than managing the FreeRadius database, implementing the batch add user feature and the Django REST APIs, are there any other core features that need to be implmented? There is the need of having extensible base classes as django-netjsonconfig does, see https://github.com/openwisp/django-netjsonconfig/#extending-django-netjsonconfig If the student finishes this project earlier and is willing to help out with adding more features we'll welcome that very gladly. But if I was you, I wouldn't undervalue the time that needs to be spent in ensuring that the freeradius integration really works. model references to the User must should be implemented using the swappable user model mechanism of django <https://docs.djangoproject.com/en/1.10/topics/auth/customizing/#referencing-the-user-model> and default to django.contrib.auth.models.User Can someone please explain this in detail? It's linked: https://docs.djangoproject.com/en/1.10/topics/auth/customizing/#referencing-the-user-model The user model must be referenced in the generic way provided by django, this feature is called swappable user model, if you need more information consult the django docs. Federico -- 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.
