paulmataruso/zulip
1
0
Fork 0
mirror of https://github.com/zulip/zulip.git synced 2025-11-02 04:53:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

puppet: Rename postgres_appdb to postgresql.

Browse Source 
There is only one PostgreSQL database; the "appdb" is irrelevant.
Also use "postgresql," as it is the name of the software, whereas
"postgres" the name of the binary and colloquial name.  This is minor
cleanup, but enabled by the other renames in the previous commit.
This commit is contained in:
Alex Vandiver
2020-10-19 19:10:17 -07:00
committed by Tim Abbott
parent 91cb0988e1
commit 188af57296
20 changed files with 107 additions and 108 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/production/export-and-import.md
View File

@@ -162,7 +162,7 @@ data includes:
* The Postgres database. You can back it up like any Postgres
database. We have some example tooling for doing that incrementally
into S3 using [wal-g](https://github.com/wal-g/wal-g) in
`puppet/zulip/manifests/postgres_backups.pp`.
`puppet/zulip/manifests/postgresql_backups.pp`.
In short, this requires:
- Zulip 1.4 or newer release.
- An Amazon S3 bucket for storing the backups.
@@ -174,7 +174,7 @@ In short, this requires:
s3_backups_bucket = # name of S3 backup
```
- A cron job to run `/usr/local/bin/pg_backup_and_purge.py`. There's puppet
config for this in `puppet/zulip/manifests/postgres_backups.pp`.
config for this in `puppet/zulip/manifests/postgresql_backups.pp`.
- Verification that backups are running via
`/usr/lib/nagios/plugins/zulip_postgres_backups/check_postgres_backup`.