Add a Portainer stack and deployment doc for Nox

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

docker-compose.mythica.yml

@@ -0,0 +1,80 @@
+# Portainer stack for the Mythica armory.
+#
+# Differs from the upstream docker-compose.yml in three ways, all of them
+# because Portainer deploys from a git checkout it manages itself:
+#
+#   1. Configuration comes from environment variables set in the Portainer
+#      stack UI, not from a .env file in the repo (upstream uses env_file,
+#      which Portainer git stacks do not provide).
+#   2. Only the four large model-data directories are bind-mounted from the
+#      host. The DBC .csv files stay in the image so they stay versioned with
+#      the code, and Portainer re-cloning the repo cannot wipe the 2 GB of
+#      model data.
+#   3. The unused ac-network block is dropped.
+#
+# See docs/mythica-deploy.md for the full procedure.
+
+services:
+    armory:
+        build:
+            context: .
+            dockerfile: Dockerfile
+        container_name: mythica-armory
+        restart: unless-stopped
+
+        environment:
+            # --- site identity -------------------------------------------------
+            ACORE_ARMORY_WEBSITE_NAME: ${ARMORY_WEBSITE_NAME:-Mythica}
+            ACORE_ARMORY_WEBSITE_URL: ${ARMORY_WEBSITE_URL:-http://192.168.1.77:48733}
+            ACORE_ARMORY_WEBSITE_ROOT: ${ARMORY_WEBSITE_ROOT:-}
+
+            # Item tooltips and item icons are loaded from this AoWoW instance.
+            # The default is a public third-party site: point this at your own
+            # AoWoW if you do not want that dependency.
+            ACORE_ARMORY_AOWOW_URL: ${ARMORY_AOWOW_URL:-https://wowgaming.altervista.org/aowow}
+
+            # --- embedding -----------------------------------------------------
+            # Set both when embedding the armory in a page on the main site.
+            ACORE_ARMORY_IFRAME_MODE__ENABLED: ${ARMORY_IFRAME_ENABLED:-0}
+            ACORE_ARMORY_IFRAME_MODE__URL: ${ARMORY_IFRAME_URL:-}
+
+            # --- behaviour -----------------------------------------------------
+            ACORE_ARMORY_LOAD_DBCS: ${ARMORY_LOAD_DBCS:-1}
+            ACORE_ARMORY_HIDE_GAME_MASTERS: ${ARMORY_HIDE_GMS:-1}
+            ACORE_ARMORY_TRANSMOG_MODULE: ${ARMORY_TRANSMOG:-0}
+
+            # 0 = serve 3D model assets from the local data directory.
+            # Leave it at 0: the upstream fetch tool can no longer rebuild this
+            # data from the Zam CDN, so the local copy is the only source.
+            ACORE_ARMORY_USE_ZAM_CDN: ${ARMORY_USE_ZAM_CDN:-0}
+
+            # --- realm ---------------------------------------------------------
+            ACORE_ARMORY_REALMS__0__NAME: ${ARMORY_REALM_NAME:-Mythica}
+            ACORE_ARMORY_REALMS__0__REALM_ID: ${ARMORY_REALM_ID:-1}
+            ACORE_ARMORY_REALMS__0__AUTH_DATABASE: ${ARMORY_AUTH_DB:-acore_auth}
+            ACORE_ARMORY_REALMS__0__CHARACTERS_DATABASE__HOST: ${ARMORY_DB_HOST:-192.168.1.60}
+            ACORE_ARMORY_REALMS__0__CHARACTERS_DATABASE__PORT: ${ARMORY_DB_PORT:-3306}
+            ACORE_ARMORY_REALMS__0__CHARACTERS_DATABASE__USER: ${ARMORY_DB_USER:?set ARMORY_DB_USER}
+            ACORE_ARMORY_REALMS__0__CHARACTERS_DATABASE__PASSWORD: ${ARMORY_DB_PASS:?set ARMORY_DB_PASS}
+            ACORE_ARMORY_REALMS__0__CHARACTERS_DATABASE__DATABASE: ${ARMORY_CHARACTERS_DB:-acore_characters}
+
+            # --- world database -------------------------------------------------
+            ACORE_ARMORY_WORLD_DATABASE__HOST: ${ARMORY_DB_HOST:-192.168.1.60}
+            ACORE_ARMORY_WORLD_DATABASE__PORT: ${ARMORY_DB_PORT:-3306}
+            ACORE_ARMORY_WORLD_DATABASE__USER: ${ARMORY_DB_USER:?set ARMORY_DB_USER}
+            ACORE_ARMORY_WORLD_DATABASE__PASSWORD: ${ARMORY_DB_PASS:?set ARMORY_DB_PASS}
+            ACORE_ARMORY_WORLD_DATABASE__DATABASE: ${ARMORY_WORLD_DB:-acore_world}
+
+            ACORE_ARMORY_DB_QUERY_TIMEOUT: ${ARMORY_DB_TIMEOUT:-10000}
+
+        volumes:
+            # The 3D model payload, extracted from the release archive. These
+            # four directories are exactly the top level of data.tar.gz.
+            - ${ARMORY_DATA_DIR:-/opt/mythica-armory/data}/meta:/data/meta
+            - ${ARMORY_DATA_DIR:-/opt/mythica-armory/data}/bone:/data/bone
+            - ${ARMORY_DATA_DIR:-/opt/mythica-armory/data}/mo3:/data/mo3
+            - ${ARMORY_DATA_DIR:-/opt/mythica-armory/data}/textures:/data/textures
+            - ${ARMORY_LOG_DIR:-/opt/mythica-armory/logs}:/logs
+
+        ports:
+            - "${ARMORY_PORT:-48733}:48733"