forked from Synapse-bridgez/synapse-core
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathdocker-compose.yml
More file actions
101 lines (97 loc) · 3.1 KB
/
Copy pathdocker-compose.yml
File metadata and controls
101 lines (97 loc) · 3.1 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
services:
postgres:
image: postgres:14-alpine
container_name: synapse-postgres
environment:
POSTGRES_USER: synapse
POSTGRES_PASSWORD: synapse
POSTGRES_DB: synapse
# wal_level/max_wal_senders/max_replication_slots make pg_basebackup
# streaming possible; archive_mode+archive_command actually populate
# postgres_wal so point-in-time recovery has WAL to replay beyond the
# latest base backup (see scripts/pitr_restore.sh). These are PGC_POSTMASTER
# settings (server start, not `initdb`), so they're passed as `postgres -c`
# flags rather than POSTGRES_INITDB_ARGS — `initdb` doesn't accept `-c`.
command:
- postgres
- -c
- wal_level=replica
- -c
- max_wal_senders=3
- -c
- max_replication_slots=3
- -c
- archive_mode=on
- -c
- archive_command=test ! -f /var/lib/postgresql/wal_archive/%f && cp %p /var/lib/postgresql/wal_archive/%f
ports:
- "5432:5432"
volumes:
- postgres_data:/var/lib/postgresql/data
- postgres_wal:/var/lib/postgresql/wal_archive
healthcheck:
test: ["CMD-SHELL", "pg_isready -U synapse"]
interval: 5s
timeout: 5s
retries: 5
redis:
image: redis:7-alpine
container_name: synapse-redis
ports:
- "6379:6379"
volumes:
- redis_data:/data
healthcheck:
test: ["CMD", "redis-cli", "ping"]
interval: 5s
timeout: 5s
retries: 5
vault:
image: hashicorp/vault:latest
container_name: synapse-vault
ports:
- "8200:8200"
environment:
VAULT_DEV_ROOT_TOKEN_ID: "root"
VAULT_DEV_LISTEN_ADDRESS: "0.0.0.0:8200"
cap_add:
- IPC_LOCK
command: server -dev
app:
build: .
container_name: synapse-app
depends_on:
postgres:
condition: service_healthy
redis:
condition: service_healthy
environment:
SERVER_PORT: 3000
DATABASE_URL: postgres://synapse:synapse@postgres:5432/synapse
DATABASE_URL_TEMPLATE: postgres://synapse:{password}@postgres:5432/synapse
STELLAR_HORIZON_URL: https://horizon-testnet.stellar.org
VAULT_ADDR: http://vault:8200
VAULT_ROLE_ID: ""
VAULT_SECRET_ID: ""
REDIS_URL: redis://redis:6379
# PITR restore (see scripts/pitr_restore.sh / src/services/pitr.rs).
# The script needs its own connection string because it runs as a
# separate process and streams a base backup over the replication
# protocol rather than reusing the app's pool.
PITR_DATABASE_URL: postgres://synapse:synapse@postgres:5432/synapse
WAL_ARCHIVE_DIR: /var/lib/postgresql/wal_archive
PITR_WORKSPACE_DIR: /app/pitr_workspace
ports:
- "3000:3000"
volumes:
- ./migrations:/app/migrations # optional: for live migration updates
# Read-only: the app never writes here, it only reads archived WAL
# segments during a restore.
- postgres_wal:/var/lib/postgresql/wal_archive:ro
- pitr_workspace:/app/pitr_workspace
command: ["/app/synapse-core"]
volumes:
postgres_data:
postgres_wal:
redis_data:
pitr_workspace: