How tekgator/docker-mcmyadmin works
This repository packages McMyAdmin and a Java Minecraft server as a Docker container. The documented workflow is to expose the panel, configure a server version and settings in McMyAdmin, then start the server; persistent data and container logs are also product capabilities. Source excerpts were unavailable, so implementation-level script relationships are not asserted.
Main entry points: Dockerfile Docker image · docker-entrypoint.sh Container entrypoint · app.sh App launcher · McMyAdmin.conf Panel configuration
Components 11
Server management
- McMyAdmin panel
- Minecraft server
Container runtime
- Docker image
Dockerfile - Container entrypoint
app/docker-entrypoint.sh - App launcher
app/app.sh - Container logs
Persistent state
- Panel configuration
app/config/McMyAdmin.conf - Server configuration
app/config/Minecraft/server.properties - Minecraft EULA
app/config/Minecraft/eula.txt - Mounted data
Other components
- Administrator
Connections 9
- Administrator → McMyAdmin panel: configures
README.md - McMyAdmin panel → Minecraft server: starts
README.md - McMyAdmin panel → Panel configuration: uses settings
README.md - Minecraft server → Server configuration: uses settings
README.md - Administrator → Mounted data: mounts volume
README.md - Docker image → Container entrypoint: starts
- Container entrypoint → App launcher: invokes
- Docker image → Container logs: tails logs
README.md - Administrator → Minecraft EULA: accepts via setting
README.md