chore: remove pack (packwiz) service and subdomain
The pack service was already gone from compose/caddy and the landing is off packwiz. Remove the remaining live references: the pack. TLS vhost in the host nginx template, pack from LE_SUBDOMAINS, and stale docs in README and CLAUDE.md. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -23,7 +23,7 @@ with `plan/` or the code, those win.
|
||||
One unified `docker-compose.yml`. The host's own nginx terminates TLS (Let's
|
||||
Encrypt) and reverse-proxies every vhost to caddy (published localhost-only) by
|
||||
Host header. caddy is the internal router; containers reach the stack's own names
|
||||
via caddy's `mcnet` aliases (`auth.`, `pack.`).
|
||||
via caddy's `mcnet` aliases (`auth.`).
|
||||
|
||||
```
|
||||
Internet ── host nginx (TLS, LE certs, HSTS) ──► caddy (127.0.0.1:8880)
|
||||
@@ -119,8 +119,7 @@ mirrored at apex `/launcher/`. Per guest:
|
||||
`https://auth.${BASE_DOMAIN}/authlib-injector` (register/login at
|
||||
`https://auth.${BASE_DOMAIN}`).
|
||||
3. The launcher installs the modpack from the distribution (`distribution.json`).
|
||||
(NOTE: packwiz/`pack.` removed — the landing join step still references a
|
||||
packwiz URL and needs reworking around the launcher/distribution flow.)
|
||||
(packwiz and the `pack.` service/subdomain have been fully removed.)
|
||||
4. Connect to `${BASE_DOMAIN}` (`:25565`).
|
||||
|
||||
## Open / Pending Work
|
||||
|
||||
Reference in New Issue
Block a user