Проверять готовность PostgreSQL по TCP и ограничить память Valkey

This commit is contained in:
2026-10-06 15:54:26 +03:00
parent bea31f3f02
commit ba535c6ee6
2 changed files with 7 additions and 3 deletions
+3 -1
View File
@@ -41,7 +41,9 @@ services:
volumes:
- pgdata:/var/lib/postgresql
healthcheck:
test: ["CMD", "pg_isready", "-U", "messenger", "-d", "messenger"]
# Over TCP: during first initialisation the image runs a temporary
# server on the Unix socket only, which must not count as ready.
test: ["CMD", "pg_isready", "-h", "127.0.0.1", "-U", "messenger", "-d", "messenger"]
interval: 5s
timeout: 3s
retries: 10
+4 -2
View File
@@ -9,8 +9,10 @@ dir /data
# The append-only file already persists everything; RDB snapshots are off.
save ""
# Sessions are never evicted to free memory: a full store refuses new logins
# (503) instead of silently logging users out.
# Sessions are never evicted to free memory: once maxmemory is reached the
# store refuses new sessions (login answers 503) instead of silently logging
# users out. A session key takes about a hundred bytes.
maxmemory 256mb
maxmemory-policy noeviction
# requirepass comes from the compose secret, never from the repository.