name: mtusi-messenger-lab4 # Настройки и секреты берутся из .env (создаёт scripts/init-env.sh, в Git не попадает). # Секреты доходят до контейнеров только файлами в /run/secrets, в переменных окружения контейнеров их нет. x-app: &app build: context: . args: APP_VERSION: ${APP_VERSION:-dev} image: mtusi-messenger:lab4 x-app-env: &app-env APP_HOST: 0.0.0.0 APP_PORT: "8080" APP_ENV: ${APP_ENV:-lab} LOG_LEVEL: ${LOG_LEVEL:-info} SHUTDOWN_TIMEOUT: ${SHUTDOWN_TIMEOUT:-8} SESSION_TTL_SECONDS: ${SESSION_TTL_SECONDS:-3600} SESSION_STORE: ${SESSION_STORE:-redis} IDEMPOTENCY_TTL_SECONDS: ${IDEMPOTENCY_TTL_SECONDS:-86400} DATABASE_URL_FILE: /run/secrets/database_url CACHE_URL_FILE: /run/secrets/cache_url DB_POOL_MIN_SIZE: ${DB_POOL_MIN_SIZE:-2} DB_POOL_MAX_SIZE: ${DB_POOL_MAX_SIZE:-10} DB_POOL_TIMEOUT: ${DB_POOL_TIMEOUT:-3} DB_CONNECT_TIMEOUT: ${DB_CONNECT_TIMEOUT:-3} DB_STATEMENT_TIMEOUT: ${DB_STATEMENT_TIMEOUT:-5} CACHE_POOL_MAX_SIZE: ${CACHE_POOL_MAX_SIZE:-20} CACHE_TIMEOUT: ${CACHE_TIMEOUT:-2} S3_ENDPOINT: http://s3:9000 S3_REGION: ${S3_REGION:-us-east-1} S3_BUCKET: ${S3_BUCKET:-messenger-attachments} S3_ACCESS_KEY_ID_FILE: /run/secrets/s3_access_key_id S3_SECRET_ACCESS_KEY_FILE: /run/secrets/s3_secret_access_key MAX_UPLOAD_BYTES: ${MAX_UPLOAD_BYTES:-10485760} MAX_IMAGE_PIXELS: ${MAX_IMAGE_PIXELS:-40000000} MAX_PARALLEL_UPLOADS: ${MAX_PARALLEL_UPLOADS:-32} UPLOAD_TIMEOUT_SECONDS: ${UPLOAD_TIMEOUT_SECONDS:-60} S3_PARALLEL_WRITES: ${S3_PARALLEL_WRITES:-4} S3_WRITE_QUEUE_SECONDS: ${S3_WRITE_QUEUE_SECONDS:-10} services: lb: build: infra/haproxy image: mtusi-messenger-lb:lab4 # единственный опубликованный порт стенда ports: - "127.0.0.1:8080:8080" networks: - edge depends_on: api: condition: service_started healthcheck: test: ["CMD", "wget", "-q", "-O", "/dev/null", "http://127.0.0.1:8404/lb-health"] interval: 5s timeout: 3s retries: 5 deploy: resources: limits: cpus: "0.5" memory: 128M restart: unless-stopped api: <<: *app environment: *app-env secrets: - database_url - cache_url - s3_access_key_id - s3_secret_access_key networks: - edge - data - storage depends_on: migrate: condition: service_completed_successfully redis: condition: service_healthy s3-init: condition: service_completed_successfully # SIGTERM -> приём закрыт -> незавершённые запросы до SHUTDOWN_TIMEOUT -> выход раньше SIGKILL stop_grace_period: 10s deploy: replicas: ${API_REPLICAS:-2} resources: limits: cpus: "1.0" memory: 256M restart: unless-stopped # миграции выполняет один контейнер до старта реплик, а не каждая реплика migrate: <<: *app command: ["python", "migrate.py"] environment: DATABASE_URL_FILE: /run/secrets/database_url secrets: - database_url networks: - data depends_on: postgres: condition: service_healthy healthcheck: disable: true deploy: resources: limits: cpus: "0.5" memory: 128M restart: "no" # создаёт bucket; повторный запуск ничего не меняет s3-init: <<: *app command: ["python", "s3_init.py"] environment: S3_ENDPOINT: http://s3:9000 S3_REGION: ${S3_REGION:-us-east-1} S3_BUCKET: ${S3_BUCKET:-messenger-attachments} S3_ADMIN_ACCESS_KEY_ID_FILE: /run/secrets/s3_admin_access_key_id S3_ADMIN_SECRET_ACCESS_KEY_FILE: /run/secrets/s3_admin_secret_access_key secrets: - s3_admin_access_key_id - s3_admin_secret_access_key networks: - storage depends_on: s3: condition: service_healthy healthcheck: disable: true deploy: resources: limits: cpus: "0.5" memory: 128M restart: "no" # убирает следы незавершённых загрузок, ключ S3 у него свой janitor: <<: *app command: ["python", "janitor.py"] environment: DATABASE_URL_FILE: /run/secrets/database_url S3_ENDPOINT: http://s3:9000 S3_REGION: ${S3_REGION:-us-east-1} S3_BUCKET: ${S3_BUCKET:-messenger-attachments} S3_JANITOR_ACCESS_KEY_ID_FILE: /run/secrets/s3_janitor_access_key_id S3_JANITOR_SECRET_ACCESS_KEY_FILE: /run/secrets/s3_janitor_secret_access_key ATTACHMENT_GRACE_SECONDS: ${ATTACHMENT_GRACE_SECONDS:-3600} JANITOR_INTERVAL_SECONDS: ${JANITOR_INTERVAL_SECONDS:-300} LOG_LEVEL: ${LOG_LEVEL:-info} secrets: - database_url - s3_janitor_access_key_id - s3_janitor_secret_access_key networks: - data - storage depends_on: migrate: condition: service_completed_successfully s3-init: condition: service_completed_successfully healthcheck: disable: true stop_grace_period: 5s deploy: resources: limits: cpus: "0.25" memory: 128M restart: unless-stopped # SeaweedFS: S3 на порту 9000; порты не опубликованы, веб-интерфейс мастера доступен только в сети storage s3: build: infra/s3 image: mtusi-messenger-s3:lab4 environment: S3_BUCKET: ${S3_BUCKET:-messenger-attachments} # мягкий предел Go ниже лимита контейнера: сборщик мусора успевает раньше, чем OOM killer GOMEMLIMIT: 768MiB secrets: - s3_admin_access_key_id - s3_admin_secret_access_key - s3_access_key_id - s3_secret_access_key - s3_janitor_access_key_id - s3_janitor_secret_access_key networks: - storage volumes: - s3data:/data healthcheck: # порт S3 открывается раньше, чем мастер узнаёт о томе данных, а до этого запросы к объектам зависают test: ["CMD-SHELL", "wget -q -O- http://127.0.0.1:9333/dir/status | grep -q s3:8080 && wget -q -O /dev/null http://127.0.0.1:9000/healthz"] interval: 3s timeout: 2s retries: 30 start_period: 60s deploy: resources: limits: cpus: "1.0" # при 512 МБ процесс убивался OOM killer при 30 параллельных загрузках по 10 MiB memory: 1024M restart: unless-stopped postgres: image: postgres:17.11-alpine environment: POSTGRES_USER: messenger POSTGRES_DB: messenger POSTGRES_PASSWORD_FILE: /run/secrets/postgres_password secrets: - postgres_password networks: - data volumes: - pgdata:/var/lib/postgresql/data healthcheck: test: ["CMD-SHELL", "pg_isready -U messenger -d messenger"] interval: 5s timeout: 3s retries: 10 deploy: resources: limits: cpus: "1.0" memory: 512M restart: unless-stopped redis: image: redis:7.4.11-alpine # сессии хранятся только здесь, поэтому включён AOF с fsync на каждую запись; # запуск через docker-entrypoint.sh, чтобы процесс работал от пользователя redis, а не от root command: - sh - -c - exec docker-entrypoint.sh redis-server --appendonly yes --appendfsync always --requirepass "$$(cat /run/secrets/redis_password)" secrets: - redis_password networks: - data volumes: - redisdata:/data healthcheck: test: ["CMD-SHELL", "redis-cli --no-auth-warning -a \"$$(cat /run/secrets/redis_password)\" ping | grep -q PONG"] interval: 5s timeout: 3s retries: 10 deploy: resources: limits: cpus: "0.5" memory: 128M restart: unless-stopped networks: # балансировщик и реплики edge: # реплики и хранилища; балансировщик сюда не входит, выхода наружу нет data: internal: true # реплики и S3; база и Redis отдельно от S3 storage: internal: true volumes: pgdata: redisdata: s3data: secrets: postgres_password: environment: POSTGRES_PASSWORD redis_password: environment: REDIS_PASSWORD database_url: environment: DATABASE_URL cache_url: environment: CACHE_URL s3_admin_access_key_id: environment: S3_ADMIN_ACCESS_KEY_ID s3_admin_secret_access_key: environment: S3_ADMIN_SECRET_ACCESS_KEY s3_access_key_id: environment: S3_ACCESS_KEY_ID s3_secret_access_key: environment: S3_SECRET_ACCESS_KEY s3_janitor_access_key_id: environment: S3_JANITOR_ACCESS_KEY_ID s3_janitor_secret_access_key: environment: S3_JANITOR_SECRET_ACCESS_KEY