Appearance
Backups, updates and restore
A complete backup includes the database and the files that give its records meaning. Custom-model metadata without the matching files is not a restorable skin collection.
What to preserve
- MariaDB game/web database, including account security and audit tables.
- Configured
mysql.ini,config.json, localsecrets.pwnand service environments, stored securely. - Mutable game runtime files, engine
bans.jsonand any relevant script data. - Uploaded model pairs and other user-managed assets.
- Runtime logs according to your retention policy.
- The exact source revision, plugin/runtime versions and known-good compiled gamemode.
The source repository excludes production credentials, generated collision data, local previews, most binaries and uploads. Git is a source backup, not a complete operational backup.
Database backup
Use a database administration/backup account and a secure destination. A Unix-shell example is:
sh
mariadb-dump --single-transaction -u backup_user -p omprp > omprp-backup.sqlThe command uses a password prompt rather than exposing a password in command arguments. --single-transaction protects transactional-table consistency, not cross-file consistency or non-transactional tables. For a consistent game/files snapshot, use a planned maintenance window and stop writes.
On Windows, use your MariaDB backup tooling or a shell that supports the intended redirection. Store backups outside the web root and release archive, with access controls and an off-host copy.
Update procedure
- Record the running revision and take a restorable backup.
- Review source, dependency and SQL changes on a private test installation.
- Apply reviewed additive migrations with an administrative DB account.
- Run web
npm ci,npm run db:generate, tests and production build. - Recompile Pawn and deploy matching runtime/plugin files where needed.
- Restart using the designated process owner, then perform smoke tests.
Use web-platform/web/prisma/sql/framework-web.sql for the supplied web additions on an existing MariaDB installation. Do not import fresh-start seeds or use prisma db push against a live framework database.
Restore rehearsal
Restore to a separate private database and directory. Reconnect the game/web to that database, restore model/runtime files and prove login, character state, faction equipment and asset access. Never test restoration by overwriting production first.
Rollback
Keep the old compiled/source revision and its matching schema assumptions. Reverting application code alone does not undo a database migration. Decide before deployment whether rollback needs data restoration or whether a forward correction is safer.
Changing AUTH_SECRET invalidates existing web sessions. Restore or rotate secrets deliberately; do not accidentally reuse a test server’s credentials in production.