On Wed, Apr 15, 2020 at 09:20:23AM -0500, Federico Capoano wrote: > > You've been focused on the controller functionality. > > The other modules bring other set of dependencies (radius, > openwisp-monitoring).
That's true. There are some modules we don't have in our environment. > > It would be really great to have a procedure that installs everything (with > flags to disable what is not needed) and a firmware image as well which has > everything (so one can also try the complete feature set on OpenWRT, being > a physical device or a VM). > It will take a while to get there but we can start gradually. That would be really handy. I would vote for an image for virtualbox to be independent of a physical device and to be able to cover the whole feature set. If somebody has a physical device, he can install openwisp-config on it anyway (if it's OpenWrt based of course). > The feature set of OpenWISP is quite big and the problem is that most users > are not aware of it. Automating the development environment could also push > us and new contributors to document everything. The reproducibility will be better too because there won't be such a big diversity in dev environments anymore, hopefully. Greetings, Oliver -- 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/20200416054129.GA32514%40okWS.
