Open langestefan opened 1 year ago
Hey no worries. Glad someone found it useful.
1) The reason for the docker network is to make sure it's private, exactly. I wanted to make sure everything was only exposed through the Proxy connection, so players don't connect to "gameserver_ip:game_port", but rather always the hub through the proxy.
2) I didn't end up doing as much Minecraft work as I had hoped, but future plans were to add mounted volumes for plugins
, and I planned to use MariaDB at this time.
3) I haven't been playing or working with latest versions lately, so I don't know too much about ProtocolLib, but something I had planned to do when we rolled out our custom plugins, to do a bit better job deploying plugins, and baking in core dependancies.
You could build upon the base Minecraft image in the Dockerfiles, add in a sharedPlugins
file, and bake in plugins such as ProtocolLib that you plan to use across each server. This does have the downside of increasing image size, and would require you to build new images to update those core plugins, which could be a hassle. It would allow you to roll out one .jar of ProtocolLib, core plugins, etc to every server, exact same version.
Happy to help, best of luck with your hosting. Let me know if there's any other questions.
Hi, great template! I really like the way this is setup so I am going to use it myself. I just have a couple of questions since I am relatively new to docker/minecraft server hosting: