Go to file
2021-08-30 04:15:16 +01:00
app Fix no attribute 'Insert' bug 2021-08-26 23:39:11 +01:00
docker Add servers directory 2021-08-26 03:00:09 +00:00
.dockerignore Add ignore files 2021-08-26 03:54:39 +01:00
.gitignore Add ignore files 2021-08-26 03:54:39 +01:00
DBCHANGES.md Update DBCHANGES.md 2021-08-22 10:00:39 +00:00
docker_launcher.sh Fix directory creation issue with docker run 2021-08-30 03:48:36 +01:00
Dockerfile Create Dockerfile and Wrapper 2021-08-26 03:47:56 +01:00
main.py Fixed bugs from pretzel merge 2021-08-18 12:50:13 -04:00
README.md Add rough docker section to readme 2021-08-30 04:15:16 +01:00
requirements.txt Cleans up requirements from unused upload stuff. 2021-08-24 21:36:54 -04:00

Crafty Controller 4.0.0-alpha.2

Python based Control Panel for your Minecraft Server

What is Crafty Controller?

Crafty Controller is a Minecraft Server Control Panel / Launcher. The purpose of Crafty Controller is to launch a Minecraft Server in the background and present a web interface for the server administrators to interact with their servers. Crafty is compatible with Docker, Linux, Windows 7, Windows 8 and Windows 10.

Documentation

Temporary documentation available on GitLab

Meta

Project Homepage - https://craftycontrol.com

Discord Server - https://discord.gg/9VJPhCE

Git Repository - https://gitlab.com/crafty-controller/crafty-web

Basic Docker Usage

A Docker image pipeline is still to be implimented but for example you can expect the image to be located: crafty/crafty-commander and you would change the image in the below docker run to this image.

If you are building from the docker-compose you can find it in ./docker/docker-compose.yml just cd to the docker directory and docker-compose up -d

If you'd rather not use docker-compose you can use the following docker run:

$ docker build . -t crafty-commander
# REMEMBER, Build your image!
$ docker run \
	--name crafty_commander \
	-p 8000:8000 \
	-p 8443:8443 \
	-p 8123:8123 \
	-p 19132:19132/udp \
	-p 24000-25600:24000-25600 \
	-v "/$(pwd)/docker/backups:/commander/backups" \
	-v "/$(pwd)/docker/logs:/commander/logs" \
	-v "/$(pwd)/docker/servers:/commander/servers" \
	-v "/$(pwd)/docker/config:/commander/app/config" \
    crafty-commander

A fresh build will take several minutes depending on your system, but will be rapid there after.

If you have a config folder already from previous local installation or docker setup, the image should mount this volume, if none is present then it will populate its own config folder for you.