Good day mentors. *Weekly Report*
I worked on the following PRs. PR 8 backend <https://github.com/openwisp/openwisp-template-library-backend/pull/8>. in which i created the directory structure of library backend, implemented socail and local login and enable APIs for CRUD of organizations from openwisp_users, external_template creation, get detail template and functionality to list and search for templates from openwisp_controller. With these, I think i have exhausted the objectives of this backend as per the the project idea page. (waiting for review). PR 81 CRUD org <https://github.com/openwisp/openwisp-users/pull/81>. Implemented API to list, create, update, delete and get details for a particular organization. (waiting for review) PR 115 create template <https://github.com/openwisp/openwisp-controller/pull/115>. Moved API to create external templates from django_netjsonconfig to openwisp_controller. (waiting for review) *Next work.* Next week, i intend to - perform changes requested by mentors if any - begin with the creation of the library frontend On Fri, Jul 5, 2019 at 7:44 PM Noumbissi Valere <[email protected]> wrote: > Good day mentors; > > *weekly report* > This is week, i worked on the following issues. > - PR 119. serialization API > <https://github.com/openwisp/django-netjsonconfig/pull/119> (waiting for > review) > - PR 123. import logic > <https://github.com/openwisp/django-netjsonconfig/pull/123> (waiting for > review) > I enhanced the API for serialization and import logic so that other > apps like openwisp-controller can use it without issues. > - PR 113. <https://github.com/openwisp/openwisp-controller/pull/113> This > PR added the serialization API and import logic from django_netjsonconfig > to openwisp-controller (waiting for review) > - notification model. > <https://github.com/openwisp/django-netjsonconfig/pull/124/commits/89a68ca46de77bfd5b281032edcce2ae7bb866d8> > This > PR handles subscription notifications to template designers > - PR 114. <https://github.com/openwisp/openwisp-controller/pull/114> Adds > the notification features from django_netjsonconfig to openwisp-controller > - API for external template creation > <https://github.com/openwisp/django-netjsonconfig/pull/125/commits/f5aa0c4b021c97e198d5deea860609d5df3dac96>. > This adds the base API for external template creation which will be used at > the template library backend (waiting for review) > > *Difficulties:* > - I am facing some issues with celery. i have done the setup as stated in > the documentation. but yet for me to work on the *notification model PR*, > i had to open extra terminals on which i ran the worker and the beat > process. without these, the celery will not behave as it opt to. I don't > think this is what will be done in production. > Secondly when i made this functionality present in openwisp-controller in *PR > 114*, the celery tasks didn't work as expected. > I am unable to figure out what the problem is. > Please can someone look at the PRs and tell me what am doing wrong? thanks. > > *Next week:* > I plan to work on openwisp-users repo to add APis for CRUD of organization > and user > > > > On Sat, Jun 29, 2019 at 12:32 AM Noumbissi Valere < > [email protected]> wrote: > >> *Weekly Update* >> >> This week, I worked on the notification model and the celery APIs for >> notifications. >> * what can be done now* >> As of this PR, it is possible for admins to >> -Receive notifications when a user imports their templates >> -Receive notifications when user delete their templates >> -Users who import templates get the contents of their templates >> periodically synchronized and a notification send to the designer to >> indicate last synchronized date. >> >> here is the PR: >> Notification model >> <https://github.com/openwisp/django-netjsonconfig/pull/124> >> >> *What to do next* >> - Perform changes which may be requested by mentors. >> - work solve the *ModuleNotFoundErrror* on openwisp_controller in order >> to make the APIs on django_netjsonconfig available to openwisp_controller. >> >> On Sun, Jun 23, 2019 at 4:41 PM Federico Capoano < >> [email protected]> wrote: >> >>> >>> >>> On Fri, Jun 21, 2019 at 2:41 PM Noumbissi Valere < >>> [email protected]> wrote: >>> >>>> *Weekly Report * >>>> During this week, i performed changes and optimized the following PRs >>>> as requested. And right now they are waiting for review. >>>> -PR 119 <https://github.com/openwisp/django-netjsonconfig/pull/119> >>>> >>> >>> PR approved, you can go ahead. >>> >>> >>>> -PR 123 <https://github.com/openwisp/django-netjsonconfig/pull/123> >>>> >>> >>> PR approved, you can go ahead. >>> >>> >>>> -PR 117 <https://github.com/openwisp/django-netjsonconfig/pull/117> >>>> >>> >>> >>> >>> >>>> After these, I decided to make these APIs available to the >>>> openwisp_controller repo. But i still got the following error >>>> *RuntimeError: Model class django_x509.models.Ca >>>> <http://django_x509.models.Ca> doesn't declare an explicit app_label and >>>> isn't in an application in INSTALLED_APPS.* >>>> I tried diverse debugging methods but i didn't find the solution. I >>>> will be glad to receive an idea on what to do. >>>> here is the PR of the work i have done so far on this issue. PR 101 >>>> <https://github.com/openwisp/openwisp-controller/pull/101> >>>> >>> >>> The problem is caused by this file: >>> https://github.com/openwisp/django-netjsonconfig/blob/gsoc2019/django_netjsonconfig/api/views.py >>> >>> That view is not programmed to be reusable by third party apps, because >>> it imports a concrete model, which will fail when you try to import that >>> view in a django project which does not list django_netjsonconfig in >>> INSTALLED_APPS (like we do in openwisp-controller, because we use >>> django-netjsonconfig as a base to extend). >>> >>> It looks like that view is being loaded automatically by django for some >>> reason. Check why it is being imported and avoid it, if you do that, the >>> problem will be fixed. >>> >>> >>>> Also, the openwisp_controller and openwisp-user does not have the >>>> gsoc2019 branch against which am suppose to send my PRs, Please i will love >>>> that this branch be created so that i can send my PRs to it rather than >>>> master. Thanks. >>>> >>> >>> Created for both. >>> >>> >>>> *Currently working on:* >>>> I have created the TemplateSubscription model and I am presently >>>> writing the various APIs for Celery. I will be sending PRs for this work in >>>> the next couple of days. >>>> >>> >>> Great. >>> >>> Thanks >>> Fed >>> >>> -- >>> 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]. >>> To view this discussion on the web, visit >>> https://groups.google.com/d/msgid/openwisp/CAERYH6XRL7hBZt6tLoYgzg99C%3DZpqjr67jc-hqMH1fMKpgR2Ew%40mail.gmail.com >>> <https://groups.google.com/d/msgid/openwisp/CAERYH6XRL7hBZt6tLoYgzg99C%3DZpqjr67jc-hqMH1fMKpgR2Ew%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> 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]. To view this discussion on the web, visit https://groups.google.com/d/msgid/openwisp/CAOwnGe57CzNDWYx%3DkLscx7mGvm3V6F4PrPgKfQXgExFGB-hgJg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
