Deploys this fork alongside the Mythica web page, reading the AzerothCore
databases over the LAN. Nothing runs on the game server itself.
docker-compose.mythica.yml differs from upstream's compose because Portainer
deploys from a git checkout it manages:
- Configuration comes from Portainer stack environment variables rather than
a .env file in the repo, which git stacks do not provide.
- Only the four large model-data directories are bind-mounted from the host,
so the DBC csv files stay versioned with the code in the image and a repo
re-clone cannot wipe the 2 GB of model data.
- The unused ac-network block is dropped.
The doc also records why the model data is a manual step: upstream's fetchdata
tool no longer works, because Zam reorganised the CDN and every character path
now 404s. A run appears to succeed while producing no character data, and the
app then fails at startup on meta/charactercustomization2/1_0.json. The v1.0.0
snapshot mirrored into this fork's release is the only remaining source.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NW2ooBP2KPqQVzdZZDMvZd
52a3af6642