Document the BlueMap live web map setup on minecraft.mivanchenko.de
Server-local Docker setup (not committed), reverse-proxied by Caddy on the same hostname the game client connects to — different port/protocol (80/443 HTTP vs 25565 raw TCP), no conflict.
This commit is contained in:
+16
@@ -51,6 +51,22 @@ python3 rcon.py "op <name>" "gamemode creative <name>" # multiple commands in
|
|||||||
|
|
||||||
Works for any server command — `list`, `whitelist add <name>`, `tp`, `weather clear`, `/chunky`-era commands if relevant, etc. The script reads the password straight from `server.properties`, nothing to copy/paste. Note it only works while the real server is awake — if lazymc has it asleep, wake it first (connect once, or `python3 rcon.py "list"` will just fail to connect).
|
Works for any server command — `list`, `whitelist add <name>`, `tp`, `weather clear`, `/chunky`-era commands if relevant, etc. The script reads the password straight from `server.properties`, nothing to copy/paste. Note it only works while the real server is awake — if lazymc has it asleep, wake it first (connect once, or `python3 rcon.py "list"` will just fail to connect).
|
||||||
|
|
||||||
|
### Live web map (BlueMap)
|
||||||
|
|
||||||
|
`minecraft.mivanchenko.de` serves a live, browser-viewable map (BlueMap) over HTTPS — same hostname the game client connects to, but a completely different port/protocol (80/443 via Caddy for the map, raw TCP 25565 direct to lazymc for gameplay), so the two don't conflict at all.
|
||||||
|
|
||||||
|
Setup lives at `~/lan-minecraft/bluemap/` on the box, running as its own Docker container (`bluemap-lan`, separate from an older unrelated `bluemap` container the box already had for a different world — reused its config templates, not its data). It mounts the live Forge server's `mcserver/world/` read-only and renders + watches for changes continuously (`-r -u -w` flags), so the map stays current through the party automatically — no manual re-render step needed. Caddy just reverse-proxies `minecraft.mivanchenko.de` to `bluemap-lan:8100`.
|
||||||
|
|
||||||
|
```bash
|
||||||
|
ssh server
|
||||||
|
cd ~/lan-minecraft/bluemap
|
||||||
|
docker compose ps # check it's running
|
||||||
|
docker compose logs -f # watch render/webserver activity
|
||||||
|
docker compose restart # if it ever needs a kick
|
||||||
|
```
|
||||||
|
|
||||||
|
Not committed to the `mc-lan-party` Gitea repo (it's server-local infra, not something that travels with the modpack) — if you ever rebuild this box from scratch, recreate it from this section rather than expecting it from `git clone`.
|
||||||
|
|
||||||
### Resource sizing for the venue box (5–15 players)
|
### Resource sizing for the venue box (5–15 players)
|
||||||
|
|
||||||
Create is the dominant cost here — it's heavier on the server **tick thread (CPU)** than on RAM, because kinetic networks and contraptions get simulated every tick regardless of how many players are nearby. Farmer's Delight/its addons are cheap by comparison. Numbers below assume this modpack (~10 mods) and are *total host box* numbers, not just the JVM heap:
|
Create is the dominant cost here — it's heavier on the server **tick thread (CPU)** than on RAM, because kinetic networks and contraptions get simulated every tick regardless of how many players are nearby. Farmer's Delight/its addons are cheap by comparison. Numbers below assume this modpack (~10 mods) and are *total host box* numbers, not just the JVM heap:
|
||||||
|
|||||||
Reference in New Issue
Block a user