1 Commits

  • feat(backup): add gramsrv-backup tool, restore scripts and migration guide
    Operators had no supported way to move a deployment or to recover one. This
    adds cmd/gramsrv-backup, which captures the PostgreSQL databases, the media and
    key tree, Redis and the configuration into a single verifiable bundle, and
    restores it on another host.
    
    backup / restore / verify, with MANIFEST.json recording the source commit, the
    schema version and exact row counts, and SHA256SUMS in sha256sum(1) format.
    Components are captured independently (server, grammystore) since each has its
    own database and usually its own container; pg_dump and redis-cli can come from
    the host or from docker exec.
    
    Portability is the point of the dump format:
    
      - plain SQL rather than the custom format, so any psql can replay it and the
        client need not match the server
      - --clean --if-exists so a bundle can be replayed over a populated database
      - --no-owner --no-privileges, and no --create, so the target role and database
        name are not baked into the artifact
      - restored with ON_ERROR_STOP=1 and --single-transaction, so a failure cannot
        leave a half-applied schema
      - \restrict, \unrestrict and SET transaction_timeout are stripped on the way
        in; they are PostgreSQL 17 specific and break older clients and servers
      - the target major version is checked before the restore starts
    
    Freezing (--freeze-units, --freeze-containers) is optional because pg_dump is
    already MVCC-consistent; it exists so the media tree is byte consistent, and
    everything stopped is restarted from a defer even when the capture fails.
    
    Verification re-hashes every artifact, decompresses it, walks tar members, and
    cross-checks file_blobs against the media tree, reporting missing and corrupt
    objects. check-media.sh runs the live form of that check.
    
    Also included: shell and PowerShell wrappers, a migration runbook in
    docs/backup-restore.md, and internal/doclint, which fails the build when tracked
    markdown leaks a key, a token or a credential so documentation stays safe to
    publish.