Use current DB owner during restore

Changes

• Constrain Python version to 3.12.3. s3cmd version 2.4.0 with Python 3.12.4 on Alpine 3.20 fails with an AttributeError.
• Find and use the current database owner when dropping the database during a restore operation. PostgreSQL requires the user executing a DROP DATABASE statement to be the database owner. PostgreSQL databases are initially owned by the user postgres before the ownership is set to the DB user. Restoring data to a brand new database requires a different user than restoring to an existing database.

Add option to backup to BackBlaze

Added

• Add option to backup to BackBlaze

Changed

• Switched from docker-compose to docker compose

Add option to backup to BackBlaze

Added

• Add option to backup to BackBlaze

Changed

• Switched from docker-compose to docker compose

Rollback previous release

Changed

• Revert possible breaking change with last release

Postgres 14 & Build with GitHub Actions

What's Changed

• Switch to GitHub Actions, upgrade postgres to 14 by @devon-sil in #8

Full Changelog: 3.1.1...3.2.0

Release 3.1.1

Fixes

• Changed Docker image base to python:3-alpine.
• Replaced the installation of s3cmd via "pip install" to the version in the Alpine repository.

Use $DB_USER when dropping the database

Merge pull request #6 from silinternational/develop

Develop

Automated build with Codeship

User-visible change: Use $DB_ROOTUSER to drop the database.

2.1.1

Updated to work with AWS RDS

2.1.0

Fixed DB restore error, upgraded to Alpine 3.15 with PostgreSQL 12 client, updated example usage description.