Ansible Role for Managing your Minecraft Server

This role installs Minecraft or Spigot and configures it to run under systemd or Supervisor. Its recommended to use the systemd process management

Note

For all steps (Development,starting the Server and executing tests) the User must accept the Minecraft EULA, by own configured properly!
by example setting a envierment property like export mc_accept_eula=true

This Documentation should be describe how you use and develop this Ansible Role. You find a list of possible role configurations at Role variables.

Table of Contents

Structure

A finished installation can be looks like:

[vagrant@localhost minecraft]$ tree -L 4
.
├── plugins
│   ├── current -> /opt/minecraft/plugins/releases/minimal
│   ├── releases
│      └── minimal
│          ├── Multiverse.jar
│          ├── PermissionsEx.jar
│          ├── report-jenkinsbuild.yml
│          ├── report-permissionsEx.yml
│          ├── report-vault.yml
│          ├── TNE.jar
│          └── Vault.jar
│   └── shared
│       ├── Multiverse.jar -> /opt/minecraft/plugins/releases/minimal/Multiverse.jar
│       ├── PermissionsEx
│          └── config.yml
│       ├── PermissionsEx.jar -> /opt/minecraft/plugins/releases/minimal/PermissionsEx.jar
│       ├── TheNewEconomy
│       ├── TNE.jar -> /opt/minecraft/plugins/releases/minimal/TNE.jar
│       └── Vault.jar -> /opt/minecraft/plugins/releases/minimal/Vault.jar
└── server
    ├── current -> /opt/minecraft/server/releases/1.13.2
    ├── releases
       └── 1.13.2
           ├── ...
           ├── spigot-1.13.2.jar
           └── work
    └── shared
        ├── plugins -> /opt/minecraft/plugins/shared
        ├── server.properties
        └── spigot.jar -> /opt/minecraft/server/current/spigot-1.13.2.jar