I just submitted a draft of my proposal please can you review it. I will be very happy to receive corrections so that i can correct it in order to send a final and correct proposal before the deadline which is April 9th, 2019. Thanks
On Sun, Mar 31, 2019 at 7:10 PM Federico Capoano <[email protected]> wrote: > Look (CTRL+F or CMD +F on mac) for the keyword "variable" in these pages: > > - http://netjsonconfig.openwisp.org/en/latest/ > - https://github.com/openwisp/django-netjsonconfig > > See also this issue: > https://github.com/openwisp/django-netjsonconfig/issues/93 > > Federico > > On Sun, Mar 31, 2019 at 1:44 PM Noumbissi Valere < > [email protected]> wrote: > >> Ok thanks Federico, >> There are somethings i have been trying to understand on the project >> idea, Please what do you mean when you say **variable** in the following >> points >> >> - shared templates will likely contain mostly variables (for example, >> imagine a coova-chilli captive portal configuration, the captive page URL, >> interface name, radius ip and ports will always differ for each user that >> wants to use the shared template), this may cause the backend validation to >> fail because variables are not recognized; find a way to overcome this >> problem, for example, sample values for each variable may be provided by >> the designer of the template and these values can be substituted to the >> variables so the validation doesn't fail, this means the template designer >> user should be allowed to fill these variables in some way >> >> - templates taken from external sources will likely contain variables >> that have to be filled by the user which imports that template from the >> external source, this means that the admin UI of OpenWISP should allow the >> user to fill these variables in some way; the list of variables may also be >> provided by the instance which shares the template >> >> On Sun, Mar 31, 2019 at 2:29 AM Federico Capoano < >> [email protected]> wrote: >> >>> The vagrant installation is one thing, your development environment >>> another thing. >>> >>> If you want to connect an OpenWRT device to your development environment >>> (the openwisp instance that you run with ./manage.py runserver) you can do >>> that instead of installing the vagrant instance, but you have to do the >>> following: >>> >>> ./manage.py runserver 0.0.0.0:8000 >>> >>> That will bind the development server to all interfaces so it can be >>> reached from your LAN using the ip address of the interface which is >>> connected to the internet, ethernet interface if you are connected via >>> ethernet cable, or wifi interface if you're connected via wifi. >>> >>> Do ifconfig on the terminal to find out your local ip address of your >>> LAN, let's pretend you find out that your local address is 192.168.0.132, >>> then you can access the OpenWISP instance at https://192.168.0.132/, if >>> the OpenWISP instance loads correctly at that URL, you can then configure >>> that in the OpenWRT device, as long as the OpenWRT device can reach it >>> (depends on how the virtualbox OpenWRT instance is configured). >>> >>> Fed >>> >>> On Sat, Mar 30, 2019 at 6:43 PM Noumbissi Valere < >>> [email protected]> wrote: >>> >>>> "pip install -e <shared_folder/repo/path>" is not found in the >>>> vagrant-openwisp2 instructions but i was looking for a way to integrate my >>>> development local repo into the vagrant-openwisp2 VM instance so the use of >>>> "pip ..." was proposed to me but it didn't still work >>>> >>>> On Thu, Mar 28, 2019 at 3:22 PM Federico Capoano < >>>> [email protected]> wrote: >>>> >>>>> I do not understand, are you following the instructions in >>>>> vagrant-openwisp2? >>>>> >>>>> Where does that "pip install -e <shared_folder/repo/path>" come from? >>>>> >>>>> >>>>> >>>>> On Wed, Mar 27, 2019 at 1:15 PM Noumbissi Valere < >>>>> [email protected]> wrote: >>>>> >>>>>> I even created a shared folder between my local machine where my >>>>>> repos are found and the Vagrant VM. then tried to used pip install -e >>>>>> <shared_folder/repo/path> but it didn't work >>>>>> >>>>>> On Wed, Mar 27, 2019 at 6:11 PM Noumbissi Valere < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> I created a shared fo >>>>>>> >>>>>>> On Wed, Mar 27, 2019 at 5:36 PM Noumbissi Valere < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Hello Federico, >>>>>>>> Yes i have tried that tutorial, i have openwrt and >>>>>>>> vagrant-openwisp2 on my VM (Virtualbox) but i have been trying to >>>>>>>> install >>>>>>>> my development repo into the vagrant-openwisp instance using pip >>>>>>>> install -e >>>>>>>> <source-path> to no avail. i wanted to do this so that i can >>>>>>>> appreciate the >>>>>>>> changes on vagrant-openwisp and openwrt when i edit my local repos. >>>>>>>> >>>>>>>> On Wed, Mar 27, 2019 at 5:13 PM Federico Capoano < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> Hi Noumbissi, >>>>>>>>> >>>>>>>>> that's great. I suggest cloning the project and start playing with >>>>>>>>> it. >>>>>>>>> >>>>>>>>> Have you tried the tutorial to connect a virtual OpenWRT device >>>>>>>>> to OpenWISP Controller yet >>>>>>>>> <http://openwisp.io/docs/user/configure-device.html>? >>>>>>>>> >>>>>>>>> Fed >>>>>>>>> >>>>>>>>> On Tue, Mar 26, 2019 at 6:01 PM Noumbissi Valere < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> Federico am interested in this project >>>>>>>>>> >>>>>>>>>> On Tue, Mar 26, 2019 at 9:10 PM Federico Capoano < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> Hey everyone, >>>>>>>>>>> >>>>>>>>>>> during the weekend I added a new idea named "OpenWISP Template >>>>>>>>>>> Sharing & Template Library" >>>>>>>>>>> >>>>>>>>>>> This project involves a lot of python & django and some >>>>>>>>>>> javascript (React JS). >>>>>>>>>>> It's not really trivial, but I would say not very hard, the >>>>>>>>>>> hardest part would be to make the template sharing feature really >>>>>>>>>>> work, the >>>>>>>>>>> rest then would be easier. >>>>>>>>>>> >>>>>>>>>>> I want to encourage students to take a look at it, because it's >>>>>>>>>>> one of the projects that would allow our community to reach a >>>>>>>>>>> turning >>>>>>>>>>> point, because we can then have an official template library where >>>>>>>>>>> we share >>>>>>>>>>> some good templates that users can import into their OpenWISP >>>>>>>>>>> instance, >>>>>>>>>>> which would make it easier for beginners to start using OpenWISP: >>>>>>>>>>> infact >>>>>>>>>>> the hardest part of using OpenWISP, after the set up, is to prepare >>>>>>>>>>> the >>>>>>>>>>> right templates with configurations that work in the real world. >>>>>>>>>>> >>>>>>>>>>> Find out more about this idea here: >>>>>>>>>>> http://openwisp.org/gsoc/ideas-2019.html#template-library >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> 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. >>>>>>>>>> >>>>>>>>> -- >>>>>>>>> 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. >>>>>> >>>>> -- >>>>> 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. >>>> >>> -- >>> 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. >> > -- > 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.
