Skip to main content

​
Before upgrading

  1. Read the release notes and breaking changes.
  2. Back up /app_data and any external database.
  3. Record the current image tag, configuration, and provider versions.
  4. Test the new release with a copy of production data when possible.
  5. Confirm enough disk space exists for the image, migration, and rollback copy.

​
Upgrade

Use an explicit release tag rather than an unpinned image. Keep the same persistent volume and required environment configuration when replacing the container. Allow database migrations to complete before starting concurrent instances.

​
Verify

  • Sign-in and access control
  • Existing presentations and uploads
  • Text, image, and search providers
  • New presentation generation
  • Canvas and AI-assisted editing
  • PPTX and PDF export
  • REST API, webhooks, and MCP integrations

​
Roll back

Stop the new release, restore the matching pre-upgrade data and database backups, and start the previous pinned image. Do not run an older application against data already migrated by a newer release unless the release notes explicitly support it.