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

Portainer stack and deployment doc for Nox #1

Merged
yrtria merged 2 commits from mythica-deploy into master 2026-09-02 13:11:14 -06:00
Conversation 0 Commits 2 Files changed 2 +4
1 changed files with 4 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files
Showing only changes of commit 788afd6e8e - Show all commits

4
docs/mythica-deploy.md
View file

@ -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.