Palisade v1.2.0

Multi-user access, adoption of containers you already run, and player analytics — plus a test harness that immediately found two latent bugs.

New

Roles: admin / operator / viewer — give friends their own logins. Viewers get read-only dashboards; operators can start/stop servers, use the console, take backups, manage mods and schedules; admins can do everything, including settings, users, and deletes. Enforced server-side on every endpoint (reads open to all roles, mutations require operator, sensitive routes require admin). Manage accounts in Settings → Users.

Adopt existing containers — already running an itzg Minecraft or lloesche Valheim from Community Applications? Palisade can now find it, create a proper managed server, and copy its world data across. The original container is stopped and left in place so nothing is lost. Server list → "Adopt existing".

Player analytics — per-player total playtime and a server-wide activity-by-hour heatmap (shown in your timezone) on the Players tab. Measured from the live player-list poll, so it appears on games that expose one.

Fixed

• Palworld and Satisfactory were silently writing unused ARK GameUserSettings.ini/Game.ini files into their instance directories — dead files neither image ever reads. Found by a new lifecycle test harness that drives the real server-start path against a simulated Docker daemon; the same harness now guards all 22 games against that class of bug.
• Off-box replication no longer hangs after the first archive (a tar exit-listener race), and the manual "Sync now" runs in the background so it survives large snapshot sets.

Internal

writeInis extracted from the 1,600-line servers service into its own ServerConfigWriter — adding a game's config handling no longer means touching the lifecycle service.

Upgrade notes

Existing single-admin installs keep full admin rights. Tokens issued before v1.1 are already invalid; if you haven't logged in since, you'll be asked to.