Not sure if the first video demo matches the hero statement. Professionals with deadlines doesn’t really map to “here is how to start a Minecraft server”
The problem with that is going to be the same as with other similar projects: single instance only. This puts the projects into a desert valley: from one hand, they are interesting to professionals; from another, the absence of horizontal scaling makes them just a toy. Meanwhile, home users for whom single instance would be enough cannot care less about this kind of technology.
We're working on migrating our abstractions to k3s, for now the system is powered by docker compose. Wouldn't be that much work to move from DR to HA deployments. Thanks for the feedback.
Not sure if the first video demo matches the hero statement. Professionals with deadlines doesn’t really map to “here is how to start a Minecraft server”
Fair point, what should we feature in the hero video?
The problem with that is going to be the same as with other similar projects: single instance only. This puts the projects into a desert valley: from one hand, they are interesting to professionals; from another, the absence of horizontal scaling makes them just a toy. Meanwhile, home users for whom single instance would be enough cannot care less about this kind of technology.
We're working on migrating our abstractions to k3s, for now the system is powered by docker compose. Wouldn't be that much work to move from DR to HA deployments. Thanks for the feedback.
I don't see any robust backup for restore mechanisms.
We replicate incremental BTRFS snapshots behind the scenes. Planning on adding snapshot management UI soon.
Thank you for the update. Is the backup or start mechanism per application or some sort of larger dataset?