yrtria/azerothcore-armory
1
0
Fork 0
Code Issues Pull requests Projects Releases 1 Packages Activity Actions

docs: chown the data directory before downloading into it
Some checks failed
Build / build (push) Has been cancelled
Details
Lint / eslint (push) Has been cancelled
Details
Build / build (pull_request) Has been cancelled
Details
Lint / eslint (pull_request) Has been cancelled
Details

Browse source 
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 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NW2ooBP2KPqQVzdZZDMvZd
This commit is contained in:
Claude 2026-09-02 17:31:50 +00:00
parent 52a3af6642
commit 788afd6e8e
No known key found for this signature in database
1 changed files with 4 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/mythica-deploy.md
View file

@ -40,6 +40,7 @@ Once. Redeploying the stack does not disturb it.
```bash ```bash
sudo mkdir -p /opt/mythica-armory/data /opt/mythica-armory/logs 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 cd /opt/mythica-armory/data
BASE=https://gitlab.hallsworth.ca/yrtria/azerothcore-armory/releases/download/v1.0.0 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`, Afterwards `/opt/mythica-armory/data` holds four directories — `meta`, `bone`,
`mo3`, `textures` — totalling roughly 2.5 GB unpacked. `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 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. travel in the image, so they stay in step with the code.