From 788afd6e8eed56e4647326c780c536fd1d7363cb Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 2 Sep 2026 17:31:50 +0000 Subject: [PATCH] docs: chown the data directory before downloading into it The procedure created /opt/mythica-armory with sudo but then ran the curl downloads as the normal user, so every one failed with "Permission denied / Failure writing output to destination". Adds the chown and notes that user ownership is fine, since the container reads the bind mount as root. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01NW2ooBP2KPqQVzdZZDMvZd --- docs/mythica-deploy.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/mythica-deploy.md b/docs/mythica-deploy.md index 8668941..299abc0 100644 --- a/docs/mythica-deploy.md +++ b/docs/mythica-deploy.md @@ -40,6 +40,7 @@ Once. Redeploying the stack does not disturb it. ```bash sudo mkdir -p /opt/mythica-armory/data /opt/mythica-armory/logs +sudo chown -R "$USER:$USER" /opt/mythica-armory # else the downloads below fail cd /opt/mythica-armory/data BASE=https://gitlab.hallsworth.ca/yrtria/azerothcore-armory/releases/download/v1.0.0 @@ -56,6 +57,9 @@ rm -f data.tar.gz data.tar.gz.part-* Afterwards `/opt/mythica-armory/data` holds four directories — `meta`, `bone`, `mo3`, `textures` — totalling roughly 2.5 GB unpacked. +Ownership by your own user is fine — the container reads these as root either +way, and it keeps the download and extract steps out of `sudo`. + The DBC `.csv` files are **not** part of this. They are committed to the repo and travel in the image, so they stay in step with the code.