A tiny project for deploying Minecraft to Fly.io.

First things first, setup the WHITELIST env var in the fly.toml. This should be the Minecraft usernames you want to grant access to the server. Be sure to include your Minecraft username for testing.

Also add your Minecraft username to the OPS env var. These are server administrators.

First decide on a globally unique Fly app name, and assign it to a an env var. Then create necessary resources in Fly with the script below.

When running the fly deploy command below, be sure to follow the prompt to setup the Volume, and allocate dedicated ipv4 and ipv6 addresses.

# The FLY_APP env var is used by the `fly` CLI
export FLY_APP="minecraft-ckreiling" # replace with your unique name
fly apps create $FLY_APP
fly volumes create minecraft_data
fly deploy \
  --vm-size shared-cpu-4x \
  --vm-memory 4096

Shortly after roll-out, you should be able to connect directly to $FLY_APP.fly.dev via the Minecraft client.

You can monitor the rollout in the Fly UI:

open https://fly.io/apps/$FLY_APP/monitoring

Destroying the Minecraft server is easy:

fly apps delete minecraft-$UNIQUE_NAME