In Ecobytes, we are also struggling to keep a concise environment for users, developers and administrators alike. @yova and @gandhiano know what I am talking about.
After we invoked ispcoop / souk · GitLab with @pierreozoux three years ago, we have learned a lot. The project for Kubernetes now continues in
Following on with our current hybrid infrastructure, we are very interested in having a Webmin-/Virtualmin-/Cloudmin-, ISPConfig-, WHCMS-, Froxlor-, Ajenti-, Vesta-like control panel, which eventually emulates an environment like Cockpit, Rancher or Portainer, to allow users manage their domains, zones, emails, databases, applications, backups, invoicing, support, users and the likes.
Especially transitioning from the shared hosting to the cloud native design pattern brings hardship to the case.
I suggest we recombine our efforts and agree on common design principles plus clearly defined use cases, before laying out an architecture with user journeys. We can start from what is there already, and iterate from here.
@gandhiano I would be interested in hearing your current approach to designing a distributed software system. What can we learn from you, to have the design concise, and get a working prototype within a foreseeable time span? How about the requirements definition, not too loose, not too strict, how to structure our process? I’d really like to give souk/souq/sook another shot, and if only in my imagination first.