Skip to content

Ansible playbook for my Minecraft server

License

Notifications You must be signed in to change notification settings

werebus/mc-config

Repository files navigation

Ansible playbook to configure my (private) Minecraft server. The philosophy here is that everything should be configured here and deployed over Ansible. Any manual changes to the server configuration will likely be overwritten.

Installed components

  • Paper server
  • Systemd service
  • mcrcon to interact with the console
  • Daily server backups
  • Lighttpd server (with SSL) for access to DynMap

Plugins

Prereqs

  • Ubuntu 24.04
  • A user capable of sudoing
  • Pipenv (for Python dependencies) on your workstation - pip install pipenv

Setup

  1. Clone this repository
  2. Get the vault password and put it in a file named vault-password. You can, of course, start from scratch. All "secret" variables are proxied in vars.yml.
  3. Install the required Python packages
    source .envrc # done automatically if you have direnv
    pipenv install

Configuration

  • production - Server inventory
  • group_vars/servers/vars.yml - Configuration values
  • group_vars/servers/vault.yml - Secret configuration values
  • /files and /templates - Config files for the Minecraft server itself

Use

$ ansible-playbook main.yml --user <remote_user>

About

Ansible playbook for my Minecraft server

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published