Update Playkeeper: when a new release is available, Update available appears in the sidebar (under More on a phone); it shows what changed and installs it when you click Update. Before anything from the download runs, Playkeeper checks that the release's manifest is signed with the Playkeeper release key built into your installed version, and that the download matches the manifest. Only the dashboard and agent restart; the Minecraft servers keep running. If the new version is not healthy within two minutes, the previous version, its services, settings and databases are put back automatically. Playkeeper looks for a new release a minute after it starts and then twice a day, downloads nothing until you click, and never goes back to an older version. Machines connected to your dashboard update from Settings › Machines.
Upgrade to 0.4.2: install it from the dashboard. A free name moves from .playkeeper.io to .playkeeper.me by itself (A name for your VPS). From a release before 0.4.0, a server on a Minecraft version before 26 also moves to the Java that version was made for, so its next start downloads that runtime once and takes longer.
Upgrade from 0.1.0: 0.1.0 cannot update itself. Run the same one-line install command on the VPS: it sees the installed version, shows what it keeps and replaces, and upgrades in place. Worlds, backups, settings and the admin account are kept, and later updates come from the dashboard. Running the command again later is safe: it does nothing if the version is the same and refuses an older one.
Uninstall: sudo playkeeper uninstall lists what it removes and asks first: Playkeeper, its services, users, containers and firewall rules, and the Docker packages it installed with the Docker folders that install created (and on the RHEL family Docker's repository, its signing key and what Docker added to firewalld), unless other containers still use Docker or you pass --keep-docker. Any of those packages that other software needs stays, like the container-selinux Podman shares. On a connected machine it leaves the dashboard first. It keeps your worlds and backups in /var/lib/playkeeper (reinstalling picks them up); --purge deletes them too and asks you to type a confirmation.
Recover or move a world: see docs/RECOVERY.md. Backups listed in the dashboard live on the same server unless you turn on copies somewhere else; download copies of the ones you care about.
Other commands: sudo playkeeper status, sudo playkeeper setup-code (a new setup code before an admin exists), sudo playkeeper reset-password <user>, sudo playkeeper reset-2fa <user> (turns off two-factor sign-in for a lost phone), sudo playkeeper join and sudo playkeeper leave (connect a machine to another dashboard, or disconnect it), and sudo playkeeper mcp (the AI tools over SSH).