I have been away from minecraft for a while but I decided to swing by and see what my favorite minecraft management software has been up too. It looks like the community is doing well. I am excited that MineOS has a docker setup. I like tinkering with docker somewhat so here is a gist that show an example of how to use docker-compose to setup up MineOS with nginx-proxy, and letsencrypt. The url for your site must be publicly reachable for lets encrypt to work and the mineos-proxy handles taking the standard web request on port 80 and proxy passing it to your mineos instance on port 8443. Maybe someone will find it helpful.
This is excellent–my exposure to docker-compose is very limited and it’s been a huge hurdle to treating mineos-docker like it’s a production-ready deployment platform.
I was able to get this up and running in no time, with a single, minor adjustment:
Simply because the docker host doesn’t likely have /etc/nginx, but it is present in the current working directory when docker compose is run. Able to make this change to the gist? I’d be more than happy to use yours as the authoritative gist and give you the credit you deserve!
I’ll tool around with this more and explore all the use cases I might get help requests about but I’d definitely like to make this an official deployment method.
I made that change for you. I have many other projects that I tie into docker so I don’t like to clutter up the root space on my own system. If this is all you are setting up its easier to have the mineos.conf in the root. Feel free to use this example however you want. I have been using mineos for a few years now to run servers for my kids so Its good that I can give something back. Thanks for all your work.
I did a bit of research and you can actually specify a port range to bind to the host machine. so the minecraft ports that are exposed can all be mapped in aa single port config like - "25565-25570:25565-25570". I haven’t tried it out yet but it should work according to the docker-compose docs. Also I left port 8443 bound but it does not need to be because of the proxy layer handling the translation of 80 to 8443 behind the scene. After I test that out tomorrow on my own server I will make that change if you are interested.
apologies, for resurrecting an old thread but this looks like the best place to solve my problem.
I’m running the official mineos docker and the Linuxserver Letsencrypt docker. I’ve got other dockers working with LE like Plex, Ombin and calibre-web and I want to get mineos. I’ve tried:
I recently took the time to simplify my setup so I updated the the gist in the first post and my home-server setup. The gist is a very lightweight solution using docker-compose.
The simple Mineos Gist is a very fast way to have a public instance of minoes with a reverse proxy secured by lets encrypt.
The Home Server setup is a more complete example with other integrated services such as a plex server and nextcloud.