Skip to content

Operations

Running LicenseTrack in production - hardening, backups, upgrades, and day-to-day operations - is covered by the pages in this section. New to LicenseTrack? Start with Getting Started to stand up an instance first; this section is about keeping it healthy in production.

  • Production deployment & hardening

    Podman, production hardening (HTTPS, reverse proxy, CORS), the full configuration reference, Official Extensions runtime constraints, and persistent data.

  • Operations runbook

    Health monitoring, log review, audit review, vulnerability management, upgrade checks, and incident response.

  • Upgrading LicenseTrack

    Docker Compose upgrade procedure, full-volume backup, project-name/volume-name behavior, and recovery if a new empty volume is created.

  • Native Linux upgrades

    Upgrade a systemd installation with its recovery archive and post-upgrade checks.

  • Native Linux removal

    Guarded removal procedure, data-retention choices, service-account cleanup, and external host cleanup for native installations.

  • Backup & restore

    How database backups and restores work, retention, the pre-restore safety snapshot, and what is (and isn't) covered.

Back up before you experiment

Deleting a license is permanent unless you have a database backup. Set up backups early, and remember that uploaded documents are stored separately from the database and need their own backup. See Backup & restore and Upgrading LicenseTrack.