Continuing what we started here.
I think the Cuberite binary should have a simple web server, maybe moving webadmin to a plugin, thus allowing any plugin to display webpages on it's own namespace. ie. cuberiteserver.com/webadmin for the webadmin plugin, cuberiteserver.com/dynmap for dynmap, etc. I guess this would be more resource efficient then each plugin running it's own webserver, and as such, only a single port would be mapped, as opposed to each plugin's web server running on a different port.
This is not meant to deprecate the current webadmin API. And moving webadmin into a plugin should be considered as it's own thing. The main discussion here is how and should add a /namespace for plugins, outside of webadmin namespace.
I think the Cuberite binary should have a simple web server, maybe moving webadmin to a plugin, thus allowing any plugin to display webpages on it's own namespace. ie. cuberiteserver.com/webadmin for the webadmin plugin, cuberiteserver.com/dynmap for dynmap, etc. I guess this would be more resource efficient then each plugin running it's own webserver, and as such, only a single port would be mapped, as opposed to each plugin's web server running on a different port.
This is not meant to deprecate the current webadmin API. And moving webadmin into a plugin should be considered as it's own thing. The main discussion here is how and should add a /namespace for plugins, outside of webadmin namespace.