Build local release artifacts and prepare Compose deployment [skip ci]

README.md

@@ -52,10 +52,12 @@ Brand it, publish vanilla versions or modpacks, manage players, and push changes
 ### 1. Run the panel
 
 ```bash
-curl -O https://raw.githubusercontent.com/scopeddlol/SCOPENET-MC/main/docker-compose.yml
-curl -o .env https://raw.githubusercontent.com/scopeddlol/SCOPENET-MC/main/.env.example
-# edit .env → set ADMIN_PASSWORD
-docker compose up -d
+git clone https://github.com/scopeddlol/SCOPENET-MC.git
+cd SCOPENET-MC
+cp .env.example .env
+# edit .env → set ADMIN_PASSWORD and PUBLIC_URL for your domain
+docker compose config --quiet
+docker compose up -d --build
 ```
 
 Open `http://your-server:8080`, sign in as `admin`, then:
@@ -64,7 +66,7 @@ Open `http://your-server:8080`, sign in as `admin`, then:
 2. **Instances** → *New instance* → a version, or a Modrinth / CurseForge / .zip modpack.
 3. **Settings** → how players sign in.
 
-> Put the panel behind HTTPS (Caddy, Traefik, nginx, Cloudflare Tunnel…) before sharing it. See [docs/admin-guide.md](docs/admin-guide.md).
+> Put the panel behind HTTPS (Caddy, Traefik, nginx, Cloudflare Tunnel…) before sharing it. See [docs/deployment.md](docs/deployment.md).
 
 ### 2. Build your branded launcher
 
@@ -99,6 +101,8 @@ docker-compose.yml Panel deployment
 - [Official server setup](docs/server-integration.md) — private authentication, supported versions, activity and UUID protection
 - [Architecture](docs/architecture.md) — how the pieces fit, API reference
 - [Development](docs/development.md) — running everything locally, tests
+- [Deployment](docs/deployment.md) — local Compose build, health check, upgrades and backups
+- [Local 0.4.0 artifacts](release-artifacts/0.4.0/README.md) — Windows installer, server jars and checksums
 
 ## Configuration reference