So I'm working on a router-config-as-a-service kind of setup, where we provide routers, and a central configuration website (possibly with integration into config for other non-router systems too later on). The main goal is to let them set up VPN based routing between their office networks easily, but I don't want to limit what they can do with their routers. At the same time, there is no way they'll get to be root on our servers :)
I do see the versioning issue - and have thought about letting you save user-defined backends as json-files (with both the schema and transform) in the source tree and have them appear next to the database backed ones, or adding a generic import/export functionality. I just haven't gotten there yet... I guess what's special about our set up is that the users of the config ui are actually customers, not our technicians... But on the other hand, maybe I'm over-engineering :P -- 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.
