I upgraded the #postgres instance that the pod uses to use WAL-G 2.0.0, which looks to be a fairly substantial upgrade. For me it initially meant upgrading the encryption key used for backups from 20 bytes to 25 bytes (which pretty much necessitated starting a new stream of backups); everything else seems to be about the same.

WAL-G allows point-in-time-recovery (PITR) of Postgres databases to be stored on S3-compatible storage (including the FOSS Minio S3 server). It's continuous, leveraging Postgres' built-in write-ahead log (WAL) to provide the source data for the backups. WAL-G then compresses and (optionally) encrypts the data before sending it to your S3 storage.

If you're running a #Diaspora pod, you owe it to yourself and to your users to maintain reliable offsite backups. Once WAL-G is configured you can pretty much forget about it, except for occasional testing to make sure the backups are recoverable.