MineOS 0.6.x is now over a year old on github, and I feel it meet my expectations of the 0.6.x milestone. In this iteration, I learned how to write code more platform-agnostic, achieving successful installs on more than half a dozen different distinct distributions/package managers.
Also in this iteration, I moved away from heavy-duty webserver models (Hiawatha) to a service-oriented model, much like those found in Plesk or cPanel. There perhaps may be too many things to list of what I’ve learned and how 0.6.x has readied me for the next version, which aims to address the many calls for greater Minecraft-specific functionality.
I have, over the years, repeatedly emphasized how MineOS (at least up through 0.6.x) aimed to focus on the administration side of things, from a Linux admin viewpoint, rather than a Minecraft server admin. Since I feel satisfied that this version can continue to have usability and educational/functional value for time to come, I can now–without reserve–embrace the other side of Minecraft hosting.
Users have, over the years, continually asked for features like:
- live feed data, such as logs and memory usage
- plugin downloading and installation
- plugin configuration
- firewall configuration
- file uploading through the web-ui
Put another way, many of these tasks–if automated by a web-ui–would inhibit learning how to be a Linux admin. I still feel that way, but with the end-product of 0.6.x as-is, I am satisfied that for the future MineOS users who still want to learn Linux administration rather than avoid it, they have a polished, accessible means.
I will continue to maintain 0.6.x as the need arises, such as any area where failing to update it would make it obsolete, but I’d like to move my efforts to learning something new: not Python.
Node.js has stuck out as a particularly promising technology to build a new web-ui in. Since I know little of node.js and I can see the merits of event-based web-servers, it is a natural fit. Hopefully, too, by being Javascript it may also encourage new contributors, who previously were deterred by Python.
That said, I welcome any feedback about this–regarding any of the following ideas!
- feature requests for a new web-ui
- ideas about the size and scope of a new web-ui
- pledges of help
- whatever else!
Will