search

moorkop / mccy-engine

Provides a web based "Minecraft Server as a Service" (MCaaS?) to deploy Minecraft server containers on any Docker Swarm cluster or standalone Engine instance.
Apache License 2.0
12 stars 4 forks source link

Backend data handling for mod testing #10

Open danpolanco opened 8 years ago

danpolanco commented 8 years ago

Typically I want to test new mods on my current world. Right now, I typically do it on the live world, which leads to down time. Perhaps something like this would work:

screen shot 2015-12-26 at 8 19 24 pm

itzg commented 8 years ago

If --volumes-from had an option for an overlay/copy-on-write strategy, then that would be a really slick way to solve this. Until then a commit could work to snap the live container and let you spin off an effective clone for mod testing. That wouldn't work if the /data was mounted in the live one...so not totally robust.

What are your ideas for the equivalent manual process?

sshipway commented 8 years ago

The pull req I submitted earlier for the minecraft-server container added the optional /mods read-only volume; the start script copies any mods found there into /data/mods before starting the server. This was intended for this sort of situation, where the world is provided by a zip file or a seed but you don't want to have a mounted /data. Maybe this can help?

itzg commented 8 years ago

Definitely @sshipway , even if not as a full blown host volume attachment (since Swarm/Carina may not allow for that) the /mods staging logic will be leveraged.

danpolanco commented 8 years ago

Rather than upload all of my different ideas, I'm just going to post them to my xmind profile. I'll still put up the ones I think are helpful.

Below, the most important part is the data vs daemon containers seen below World X.

screen shot 2016-01-05 at 4 22 30 pm

danpolanco commented 8 years ago

I'm thinking this is a pretty heavy feature for 0.2. Gonna push it even further for now.