Hi, On Mon, Apr 8, 2019, 2:49 AM Federico Capoano <[email protected]> wrote:
> *Provide the OpenWISP Admin interface and the views managing account > information (password reset, email confirmation) in a dedicated container.* > From http://openwisp.org/gsoc/ideas-2019.html > > We can also run migrations only there, it should work, because if we > update any dependency that affects any of the services, most likely the > admin/dashboard container will have to be re-deployed as well. > I think I am still a bit unclear about "admin interface"/dashboard. From what I understand now, dashboard means all the OpenWISP services in one container. i.e openwisp-radius, openwisp-controller, openwisp-network-topology and in future openwisp-ipam and other services would be available in this container. By this understanding, a basic user would only need the dashboard container in the beginning and should they feel the need to add instance of a specific service like radius, they can simply add a new container for openwisp-radius and additional traffic would flow to the new instance with the help of a load balancer. Is this understanding correct and by dashboard we mean all the services? Please correct me otherwise. I have also sent the proposal on GSoC's website. Please let me know if there are any final corrections to be made or any section / information to be added or removed in the application. Thanks, Ajay Tripathi -- 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.
