fix(deploy): support a non-standard S3 port for the pgBackRest endpoint

The S3 endpoint is a host only; some providers publish a separate, non-443 port. Add an optional PGBACKREST_S3_PORT (default 443) alongside the endpoint host, wired through the prod overlay, write-prod-env.sh and both prod workflows, and clarify in the docs that the endpoint variable takes the host alone.
2026-07-09 01:14:05 +02:00
parent e922f5f3b9
commit a58f2ce0e4
6 changed files with 14 additions and 6 deletions
@@ -21,7 +21,8 @@ POSTGRES_PASSWORD=change-me            # required
 # recovery). Gitea: PROD_PGBACKREST_* — endpoint/bucket/region/archive-mode are variables,
 # the two S3 keys + the cipher passphrase are secrets.
 PGBACKREST_ARCHIVE_MODE=off            # on = archiving active (arm only after the stanza exists)
-PGBACKREST_S3_ENDPOINT=                # e.g. s3.ru-1.storage.selcloud.ru (Selectel S3, path-style addressing)
+PGBACKREST_S3_ENDPOINT=                # S3 HOST ONLY — no https://, no port, no bucket (e.g. s3.ru-1.storage.selcloud.ru); path-style addressing
+PGBACKREST_S3_PORT=                    # optional; default 443 — set only if the provider uses a non-standard S3 port
 PGBACKREST_S3_BUCKET=                  # bucket name; lowercase, no dots/underscores
 PGBACKREST_S3_REGION=                  # e.g. ru-1
 PGBACKREST_S3_KEY=                     # secret: S3 access key id