Host updates, backups & recovery
Protect the configured data before replacing a release.
Know what a release contains
A downloadable source or update ZIP is not a backup of a running bot’s data or private configuration. The host’s .env, encrypted environment overrides, SQLite data and archives need their own private backup process.
Use the existing installation
Apply a verified update to the current PrynBot directory. Preserve the configured DATA_DIR, bot identity launcher, session/proxy secrets and existing infrastructure. Do not run two gateway processes against the same data directory.
Back up before applying
The update helper checks the target and creates backups before copying application files. New dependencies are prepared separately where required. Stop the correct PrynBot entry in the host manager before updating; leave unrelated bots alone.
Validate after starting
Start through the existing host manager, check the ready/API messages and refresh the dashboard. Test private channel permissions, a real ticket and a welcome in a controlled server. Local automated tests do not prove live provider connectivity.
Plan the rollback
Keep the previous verified release and the private host backup. A code rollback and a data rollback are different actions: restoring older data can discard submissions or tickets created since the snapshot. Preserve the current data before any point-in-time restore.