You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 21, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+9-8Lines changed: 9 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ services:
12
12
POSTGRES_PASSWORD: password
13
13
14
14
backup:
15
-
image: eeshugerman/postgres-backup-s3:13
15
+
image: eeshugerman/postgres-backup-s3:15
16
16
environment:
17
17
SCHEDULE: '@weekly'# optional
18
18
BACKUP_KEEP_DAYS: 7# optional
@@ -28,11 +28,12 @@ services:
28
28
POSTGRES_PASSWORD: password
29
29
```
30
30
31
-
- Images are tagged by the major PostgreSQL version they support: `10`, `11`, `12`, `13`, or `14`.
31
+
- Images are tagged by the major PostgreSQL version supported: `11`, `12`, `13`, `14`, or `15`.
32
32
- The `SCHEDULE` variable determines backup frequency. See go-cron schedules documentation [here](http://godoc.org/github.com/robfig/cron#hdr-Predefined_schedules). Omit to run the backup immediately and then exit.
33
33
- If `PASSPHRASE` is provided, the backup will be encrypted using GPG.
34
-
- Run `docker exec <container name> sh backup.sh` to trigger a backup ad-hoc
35
-
- Use `BACKUP_KEEP_DAYS` to set time for how long you want to keep backup.
34
+
- Run `docker exec <container name> sh backup.sh` to trigger a backup ad-hoc.
35
+
- If `BACKUP_KEEP_DAYS` is set, backups older than this many days will be deleted from S3.
36
+
- Set `S3_ENDPOINT` if you're using a non-AWS S3-compatible storage provider.
36
37
37
38
## Restore
38
39
> **WARNING:** DATA LOSS! All database objects will be dropped and re-created.
@@ -64,10 +65,10 @@ This project is a fork and re-structuring of @schickling's [postgres-backup-s3](
64
65
65
66
## Fork goals
66
67
These changes would have been difficult or impossible merge into @schickling's repo or similarly-structured forks.
0 commit comments