Tasks for NetJSON Templates Website

[Aditya]

Hi. @nemesisdesign asked me if there are any tasks regarding NetJSON Templates website, so here are two tasks.

Title - [NetJSON Templates] Create a popup to load templates asynchronously

Description - 

We have created a new site for storing and accessing community made NetJSON templates.

Currently, this website loads entire template script on the different page while the expected behavior is to create a popup that fetches code from the respective template and show it on the page. 

Github issue - https://github.com/openwisp/netjson-templates/issues/3

Title - [NetJSON Templates] Add guiding pages to NetJSON Templates Website

Description - 

OpenWISP uses a concept of NetJSON Templates which is the reusable piece of code. You can read more about it here.

We have created a website for storing and accessing community made NetJSON templates. This website does not have information about how to contribute and more info about templates. Your task is to create two pages stating the rules about contributing which you can find here (you can copy and paste this info) and create an information page that tells about templates.

[Federico Capoano]

Let's call this website OpenWISP 2 Template Library, we can mention NetJSON in a description or something like that, but we should make it clear that the goal of this website is to allow OpenWISP 2 users to share templates and hopefully find ready-made configurations in the near future.

We could also develop a feature in django-netjsonconfig which allows to load templates from an external URL!

That would be super cool.

Tasks added!

[Stuart Trusty]

HI Federico!

Do we have an OpenWisp2 template library setup anywhere presently?  I saw you had one setup in the video, but I think that site is different now.  In particular, it would be nice to get some of the 802.11s templates posted somewhere if they aren't already.

Thank you much,

Stuart

[Federico Capoano]

Hi Stuart,

a template library attempt was started with https://github.com/openwisp/netjson-templates but hasn't gained traction yet.

Regarding 802.11s, you can find an example which should work (I use it myself) in the netjsonconfig documentation: Wireless Mesh (802.11s).

I hope this helps.

Federico

[Stuart Trusty]

Hi Federico,

That does help, but I think we also need some more accessible howto's and examples for 802.11s, batman-adv, etc.  I would be happy to host a repository for some templates like 802.11s-gateway, 802.11s-repeater, etc. and set about some Wiki area to make this easier for people if you would care to share what you have already.

Thanks for all you do,

Stuart

[Federico Capoano]

Hey Stuart,

the best way to do that is to add a "tutorials" section in the openwisp user documentation, the README explains how to generate the HTML from the ReStructuredText documents.

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 openwisp+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Stuart Trusty]

Hi Federico,

After following the instructions I conclude that this way of sharing information is actually an impediment to the project.  For one thing, the 'make html' command doesn't work (need to 'sudo apt install sphinx-common' to work), and for another the 'help' link is a 404.  People in the trenches working on this stuff need a simple wiki to share notes, and may not have the level of expertise required to even understand the gist of what is happening if they fork the github repository docs.  We need to simply this entire process with an emphasis on practicality, as this entire enterprise is a quickly moving target and most of the docs are at least moderately deprecated as even this exercise demonstrates.

On my original statement, let's take for example the 802.11s template.  This will not work for anyone to setup 802.11s.  Anyone that does this will get the same br-lan IP number- which won't work, and if they actually do use this config the way it is, they will have to reflash their firmware.  So, they need to know, for example, that they need to change the IP on each 802.11s node for the interface.  What would really be helpful is a way to assign each new radio an incremented IP number on the br-lan interface, or maybe a quick setup guide to use babeld.

Then there is the question of an encrypted 802.11s mesh.  It is barely documented.  To make it useful for everyone, all I have to do here is post right here the working config and at least someone can search for it on Google and find the answer (Thanks to Franco Damian Castillo).  

/etc/config/wireless

config wifi-iface
option device 'radio0'
option ifname 'mesh0'
option network 'lan'
option mode 'mesh'
option mesh_id 'meshdeprueba'
option mesh_fwding '1'
option encryption 'psk2 + ccmp'
option key 'meshdeprueba'
option sae_password 'meshdeprueba'

At one time you had a repository on polesine.publicwifi.it with what looked like a lot of good templates, although I didn't see anything for batman-adv; what would really be useful is even an anonyous-ftp to encourage people to share these types of files and comment around them. 

Please let us know your thoughts on this.

Thank you for all you do,

Stuart

You received this message because you are subscribed to a topic in the Google Groups "OpenWISP" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openwisp/PgUn8q-lnqs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openwisp+u...@googlegroups.com.