Backup Maintenance

Backup and Maintenance

Data worth backing up

At minimum, include:

plugins/BlueMapWebChat/config.yml
plugins/BlueMapWebChat/history.db
plugins/BlueMapWebChat/direct-messages.db
plugins/BlueMapWebChat/group-messages.db
plugins/BlueMapWebChat/emojis/
plugins/BlueMapWebChat/uploads/
plugins/BlueMapWebChat/audit/

Also include any JSONL files if you selected JSONL storage instead of SQLite.

SQLite backups

The safest backup is taken while the server/plugin is stopped, or with a SQLite-aware backup method. Avoid treating a database file that is actively being written as an ordinary text file.

Retention

BlueMapWebChat can clean old public history, DMs, group messages, uploads, and other retained data according to configuration. Review retention before enabling the plugin on an existing server, especially if you expect long-lived archives.

Reload vs restart

Use /bmchat reload for normal configuration changes.

A full server restart is required when:

• Replacing the BlueMapWebChat JAR
• Changing code-level behavior/endpoints
• Updating a dependency/plugin that itself requires restart

Run /bluemap reload when BlueMap web assets need to be reloaded.

Before upgrading

1. Back up the plugin directory and databases.
2. Record the exact JAR/checksum currently deployed.
3. Upgrade all cross-server DM peers together.
4. Review the generated migration fragment before changing config-version.