The pack./packwiz service was removed operationally long ago, but several plan docs still presented pack. as a live caddy vhost / DNS subdomain and render-pack.sh as a current tool. Remove those references from the current-architecture docs (overview, caddy, tooling, uptime-kuma, letsencrypt, mc-backup); leave the migration log (04-mods.md), superseded banner (04-packwiz.md), commit history (12-build-order.md), and planned landing rework (18) intact as deliberate history. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
855 B
855 B
mc-backup — world backups
Summary
itzg/mc-backup alongside the server, talking via RCON. Snapshots the world every
6h, prunes after 14 days. World-only (no mod jars — mods are reproducible from the
distribution). Unchanged from the original design; lowest-priority service.
Config (carry-over)
mc-backup:
image: itzg/mc-backup
environment:
BACKUP_INTERVAL: "6h"
RCON_HOST: "minecraft"
RCON_PASSWORD: ${RCON_PASSWORD}
PRUNE_BACKUPS_DAYS: "14"
TZ: "Europe/Madrid"
volumes:
- mc_data:/data:ro
- ./backups:/backups
Tasks
- Keep
mc-backupservice onmcnet,depends_on: minecraft - Confirm RCON enabled on server (
ENABLE_RCON,RCON_PASSWORD) - Verify
./backups/is gitignored (already is) - Optional: shorter interval / manual
rcon save-allbefore risky changes