ThreatCull 2.7.0

Backups that bring an install back with the same feed URLs, and an optional full database backup.
After upgrading, export your configuration so your backup has the new fields. If a cron job runs
threatcull run next to serve, remove it: serve runs its own schedule, and run now refuses to
start beside it.

Added

• 💾 Configuration and full backups. The configuration export now carries Feed Token and API
  token hashes (still no passwords or raw tokens). threatcull config import --restore-tokens
  brings them back, so old feed URLs and API tokens keep working on a fresh install. The
  Restore Feed Tokens from the file box on Settings restores Feed Tokens only; API tokens are
  restored from the command line. threatcull backup create copies the whole database while
  ThreatCull runs, and threatcull backup restore replaces it with a checked backup file while
  ThreatCull is stopped, keeping a safety copy. See the README's "Back up and restore". A
  configuration file exported by this version needs this version or newer to import, because older
  versions reject the new fields.

Changed

• 🔒 One ThreatCull per data directory. serve and run now hold a lock on the data directory.
  A second serve, or threatcull run while serve runs (for example from cron), stops with
  "ThreatCull is running on …: stop it first". Commands also refuse to open the database while a
  backup restore is running.

Documentation

• 📝 Safer full backups. The README told you to copy the threatcull-data volume for a full
  backup, which can give a corrupt database while ThreatCull runs. It now uses
  threatcull backup create and shows how to restore on a new host. The Quick start is numbered
  steps, the README says who ThreatCull is for, and an Air-gapped install section covers offline
  hosts.