I think a tar.gz would be a good starting point. At the very first stage, we should just make sure netjsonconfig generates valid configuration files that when installed on the device work well.
How to install and update these configuration on the device should be analyzed at later step and if you want to help out in that you will be very welcome. For example, I have been thinking about adding a "push" mode to openwisp in order to push the configuration via ssh, that could be a way. In this scenario, the logic which installs and updates the config of the device would be in the server and we wouldn't neet a local deamon. We could, of course, write a deamon for raspbian too if we need. Keep in mind I don't know every technical detail of each project yet. We should dedicate the first period of the program to research this kind of doubts and gather all the information to make good decisions. It is also a responsibility of GSOC students to come up with good solutions for the open problems we have. I hope it helps. Federico Il ven 24 mar 2017, 14:05 Ritwick D'Souza <[email protected]> ha scritto: > Like the other backends rely on some kind of firmware that runs on the > router. What should the Raspberry Pi use ? > > > On Friday, March 24, 2017 at 4:32:14 PM UTC+4, Ritwick D'Souza wrote: > > How will the configuration archive that needs to be generated be used on > Raspberry Pi ? > Can you give a brief on how things should work on the Raspberry Pi side ? > > Thanks > > -- > 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.
