The pgbackrest_entrypoint.sh script hasn't been updated in five years. It's still a great guideline for using the image & the API server and I got a working local setup out of it with minor tweaking, but it could be worth spending a small amount of time updating.
One thing I noted when building a self-hosted setup is that it hardcodes the amazon aws API and us-east-2 . It may be useful to turn those into optional env variable parameters could be a good idea, since the S3 API has been copied by a bunch of other storage media such as minio and ceph , both of which can be excellent targets to store physical backups depending on scale/requirements.
The
pgbackrest_entrypoint.shscript hasn't been updated in five years. It's still a great guideline for using the image & the API server and I got a working local setup out of it with minor tweaking, but it could be worth spending a small amount of time updating.One thing I noted when building a self-hosted setup is that it hardcodes the amazon aws API and us-east-2 . It may be useful to turn those into optional env variable parameters could be a good idea, since the S3 API has been copied by a bunch of other storage media such as minio and ceph , both of which can be excellent targets to store physical backups depending on scale/requirements.