The base config files I use for each service I host, including a dockerized Nginx to glue it all together.
This repository has been archived on 2021-12-24. You can view files and clone it, but cannot push or open issues/pull-requests.
 
 
 
Go to file
Jef Roosens f25e3072b1 Fixed wrong db mountpoint 2021-01-05 12:07:55 +01:00
backups Moved minecraft to own folder 2021-01-04 21:00:25 +01:00
firefly Fixed wrong db mountpoint 2021-01-05 12:07:55 +01:00
minecraft Moved minecraft to own folder 2021-01-04 21:00:25 +01:00
nginx Split config file 2021-01-04 14:27:32 +01:00
tshock Added copyright boilerplate to all files 2020-12-31 11:46:00 +01:00
watchtower Added watchtower labels to firefly 2021-01-05 12:00:43 +01:00
.gitignore Added env files to global ignore 2021-01-05 11:56:37 +01:00
LICENSE Added fabric server 2020-12-30 12:24:21 +01:00
README.md Updated README 2021-01-04 22:53:34 +01:00

README.md

self-hosting

Contents

The repo contains setup guides for the following:

  • Vanilla Minecraft
  • Modded Minecraft using Forge
  • Modded Minecraft using Fabric
  • Vanilla Terraria
  • Modded Terraria (coming soon)
  • Firefly 3
  • Nginx
  • My own backup scripts

Each directory contains (or will contain) its own README.md to aid with the installation of that specific setup.

General info

This info applies to all configs.

Docker

All the setups named above use Docker and docker-compose. If you're on a Linux-based server, you can find both docker and docker-compose in your package manager (do note that the Docker package might be called docker.io). Otherwise, the install instructions can be found here.

Configuration

Most configuration can be done using a .env file with a provided .env.example file to start from. This means that you never have to edit the compose files, unless you wish to deviate from the default format.

Building the image

You can build the container image using the command docker-compose build. This will build all services specified in the docker-compose.yml file. Any build configuration/environment variables can be defined in a .env file. A .env.example file is given for each configuration.

Running the container

For running the server, we can use docker-compose up -d. This will start the service in the background. You can then see any logs using docker-compose logs. If you want the logs to update automatically, use docker-compose logs -f.

Why did I make this?

Well, I just wanted to put all my knowledge in one basket. this makes it easier to manage and share with others. I spend a lot of time tweaking these configs and figuring out how they work best (for me at least), and wanted to share this with everyone else.