# Стенд lab5: API -> S3 staging + PostgreSQL outbox -> Valkey Streams -> worker. # Перед первым запуском: python scripts/init_secrets.py # Запуск: docker compose up -d --build --wait (подробно — REPORT.md, раздел «Запуск из чистого clone»). name: mtusi-lab5 x-app: &app build: context: . args: APP_VERSION: ${APP_VERSION:-lab5} image: mtusi-messenger:lab5 # Имя остановленного контейнера встроенный DNS Docker пересылает внешнему серверу и ждёт ответа # около 4 с (замерено в lab2). Ограничиваем ожидание DNS одной секундой. dns_opt: - timeout:1 - attempts:1 x-api-environment: &api-environment APP_HOST: 0.0.0.0 APP_PORT: "8080" APP_ENV: ${APP_ENV:-lab} APP_LOG_LEVEL: ${APP_LOG_LEVEL:-INFO} APP_SHUTDOWN_TIMEOUT: ${APP_SHUTDOWN_TIMEOUT:-8} APP_DRAIN_DELAY: ${APP_DRAIN_DELAY:-3} SESSION_TTL_SECONDS: ${SESSION_TTL_SECONDS:-3600} IDEMPOTENCY_TTL_SECONDS: ${IDEMPOTENCY_TTL_SECONDS:-86400} DB_POOL_SIZE: ${DB_POOL_SIZE:-10} # Пароли передаются файлами секретов, а не переменными окружения. DATABASE_URL_FILE: /run/secrets/database_url CACHE_URL_FILE: /run/secrets/cache_url S3_ENDPOINT: http://s3:8333 S3_REGION: us-east-1 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} x-job-environment: &job-environment DATABASE_URL_FILE: /run/secrets/database_url BROKER_URL_FILE: /run/secrets/broker_url S3_ENDPOINT: http://s3:8333 S3_REGION: us-east-1 S3_BUCKET: messenger-attachments S3_ACCESS_KEY_ID_FILE: /run/secrets/s3_worker_access_key_id S3_SECRET_ACCESS_KEY_FILE: /run/secrets/s3_worker_secret_access_key WORKER_CONCURRENCY: ${WORKER_CONCURRENCY:-1} JOB_MAX_ATTEMPTS: ${JOB_MAX_ATTEMPTS:-5} JOB_TIMEOUT_SECONDS: ${JOB_TIMEOUT_SECONDS:-10} JOB_LEASE_SECONDS: ${JOB_LEASE_SECONDS:-45} IMAGE_MEMORY_MIB: ${IMAGE_MEMORY_MIB:-768} MAX_UPLOAD_BYTES: ${MAX_UPLOAD_BYTES:-10485760} MAX_IMAGE_PIXELS: ${MAX_IMAGE_PIXELS:-40000000} JOB_RETRY_BASE_SECONDS: ${JOB_RETRY_BASE_SECONDS:-1} JOB_RETRY_MAX_SECONDS: ${JOB_RETRY_MAX_SECONDS:-30} STAGING_RETENTION_SECONDS: ${STAGING_RETENTION_SECONDS:-86400} services: # Единственная публичная точка входа. Проверяет /health/ready каждой реплики каждую секунду. lb: image: haproxy:3.4.5-trixie@sha256:76928c0d6b39bdd5f1c15d519cf48c47a6aa18c1dc552f7af1c146d2aa003c14 volumes: - ./infra/haproxy/haproxy.cfg:/usr/local/etc/haproxy/haproxy.cfg:ro ports: - "127.0.0.1:${APP_PUBLISHED_PORT:-8080}:8080" # Страница состояния HAProxy (UP/DOWN реплик), только для этой машины. - "127.0.0.1:${LB_STATS_PORT:-8404}:8404" depends_on: api: condition: service_healthy deploy: resources: limits: {cpus: "0.50", memory: 128M} restart: unless-stopped # Реплики API: без container_name и без опубликованных портов, доступ только через lb. api: <<: *app environment: *api-environment secrets: [database_url, cache_url, s3_access_key_id, s3_secret_access_key] tmpfs: - /tmp:size=32M,mode=1777 deploy: replicas: ${API_REPLICAS:-2} resources: limits: {cpus: "0.50", memory: 512M} depends_on: postgres: condition: service_healthy valkey: condition: service_healthy migrate: condition: service_completed_successfully bucket: condition: service_completed_successfully stop_grace_period: 10s restart: unless-stopped # Одноразовый сервис: применяет миграции один раз до старта реплик и завершается. migrate: <<: *app command: ["python", "-m", "messenger.migrate"] environment: DATABASE_URL_FILE: /run/secrets/database_url secrets: [database_url] depends_on: postgres: condition: service_healthy deploy: resources: limits: {cpus: "0.50", memory: 128M} restart: "no" # S3 gateway, filer, master и volume в одном учебном контейнере; все данные в volume. # Ни S3, ни административные HTTP-порты на хост не публикуются. s3: image: chrislusf/seaweedfs:3.85@sha256:49312939c00c01e5ee6afbd7d728b18027821d3764c35a797a72acd4fdf3296a command: ["server", "-ip=s3", "-dir=/data", "-volume.max=20", "-master.volumeSizeLimitMB=100", "-filer", "-filer.port=8888", "-s3", "-s3.port=8333", "-s3.config=/run/secrets/s3_config"] secrets: [s3_config] volumes: - s3data:/data - ./infra/seaweedfs/filer.toml:/etc/seaweedfs/filer.toml:ro deploy: resources: limits: {cpus: "1.00", memory: 512M} restart: unless-stopped bucket: <<: *app command: ["python", "-m", "messenger.bucket"] environment: S3_ENDPOINT: http://s3:8333 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] depends_on: [s3] restart: "no" # Только явный запуск оператором, без административного ключа у API. cleanup: <<: *app profiles: [tools] entrypoint: ["python", "-m", "messenger.cleanup_objects"] environment: DATABASE_URL_FILE: /run/secrets/database_url S3_ENDPOINT: http://s3:8333 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 STAGING_RETENTION_SECONDS: ${STAGING_RETENTION_SECONDS:-86400} secrets: [database_url, s3_admin_access_key_id, s3_admin_secret_access_key] depends_on: postgres: {condition: service_healthy} bucket: {condition: service_completed_successfully} restart: "no" broker: image: valkey/valkey:9.0.6-trixie@sha256:63346cb24a61221e76bdf41acce99b3968a9fa83d8122144deab45394b27b4f2 command: ["valkey-server", "/usr/local/etc/valkey/valkey.conf"] secrets: [broker_auth] volumes: - brokerdata:/data - ./infra/broker/valkey.conf:/usr/local/etc/valkey/valkey.conf:ro healthcheck: test: ["CMD-SHELL", "valkey-cli --no-auth-warning -a \"$$(sed -n 's/^requirepass //p' /run/secrets/broker_auth)\" ping | grep -q PONG"] interval: 5s timeout: 3s retries: 10 start_period: 5s deploy: resources: limits: {cpus: "0.50", memory: 256M} restart: unless-stopped dispatcher: <<: *app command: ["python", "-m", "messenger.dispatcher"] environment: *job-environment secrets: [database_url, broker_url, s3_worker_access_key_id, s3_worker_secret_access_key] # Readiness API здесь не подходит: dispatcher сам переживает отказ брокера. healthcheck: {disable: true} depends_on: migrate: {condition: service_completed_successfully} broker: {condition: service_healthy} bucket: {condition: service_completed_successfully} deploy: resources: limits: {cpus: "0.50", memory: 256M} stop_grace_period: 8s restart: unless-stopped worker: <<: *app command: ["python", "-m", "messenger.worker"] environment: *job-environment secrets: [database_url, broker_url, s3_worker_access_key_id, s3_worker_secret_access_key] tmpfs: - /tmp:size=128M,mode=1777 healthcheck: {disable: true} depends_on: migrate: {condition: service_completed_successfully} broker: {condition: service_healthy} bucket: {condition: service_completed_successfully} deploy: resources: limits: {cpus: "1.00", memory: 1G} stop_grace_period: 30s restart: unless-stopped jobs: <<: *app profiles: [tools] entrypoint: ["python", "-m", "messenger.jobs_cli"] environment: *job-environment secrets: [database_url, broker_url, s3_worker_access_key_id, s3_worker_secret_access_key] healthcheck: {disable: true} depends_on: migrate: {condition: service_completed_successfully} restart: "no" postgres: image: postgres:18.6-trixie@sha256:74935e72241653ca55e0414067e6d8763aceb8a810eb51b452253ec3dcfc4336 environment: POSTGRES_DB: messenger POSTGRES_USER: messenger POSTGRES_PASSWORD_FILE: /run/secrets/postgres_password secrets: [postgres_password] volumes: # С PostgreSQL 18 образ хранит данные в /var/lib/postgresql/18/docker: volume монтируется на уровень выше. - pgdata:/var/lib/postgresql healthcheck: test: ["CMD", "pg_isready", "--username=messenger", "--dbname=messenger"] interval: 5s timeout: 3s retries: 10 start_period: 10s deploy: resources: limits: {cpus: "1.00", memory: 512M} restart: unless-stopped valkey: image: valkey/valkey:9.0.6-trixie@sha256:63346cb24a61221e76bdf41acce99b3968a9fa83d8122144deab45394b27b4f2 command: ["valkey-server", "/usr/local/etc/valkey/valkey.conf"] secrets: [valkey_auth] volumes: - valkeydata:/data - ./infra/valkey/valkey.conf:/usr/local/etc/valkey/valkey.conf:ro healthcheck: # Пароль берётся из того же файла секрета, что подключает valkey.conf. test: ["CMD-SHELL", "valkey-cli --no-auth-warning -a \"$$(sed -n 's/^requirepass //p' /run/secrets/valkey_auth)\" ping | grep -q PONG"] interval: 5s timeout: 3s retries: 10 start_period: 5s deploy: resources: limits: {cpus: "0.50", memory: 256M} restart: unless-stopped volumes: pgdata: valkeydata: s3data: brokerdata: # Файлы создаёт scripts/init_secrets.py; каталог secrets/ в .gitignore. # Каждому сервису выдаются только нужные ему секреты; lb не получает ни одного. secrets: postgres_password: file: ./secrets/postgres_password database_url: file: ./secrets/database_url valkey_auth: file: ./secrets/valkey_auth cache_url: file: ./secrets/cache_url broker_auth: file: ./secrets/broker_auth broker_url: file: ./secrets/broker_url s3_config: file: ./secrets/s3_config s3_access_key_id: file: ./secrets/s3_access_key_id s3_secret_access_key: file: ./secrets/s3_secret_access_key s3_admin_access_key_id: file: ./secrets/s3_admin_access_key_id s3_admin_secret_access_key: file: ./secrets/s3_admin_secret_access_key s3_worker_access_key_id: file: ./secrets/s3_worker_access_key_id s3_worker_secret_access_key: file: ./secrets/s3_worker_secret_access_key