name: messenger-lab4 x-app-build: &app-build context: . args: APP_VERSION: ${APP_VERSION:-dev} x-s3-api-secrets: &s3-api-secrets S3_ENDPOINT: ${S3_ENDPOINT:-http://s3:8333} 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 services: migrate: build: *app-build 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 restart: "no" deploy: resources: limits: {cpus: "0.50", memory: 128M} # S3-совместимое хранилище SeaweedFS (master + volume + filer + S3 в одном процессе): байты вложений. # Только во внутренней сети data, порты не публикуются. Ключи и их права — в секрете s3_config # (генерирует scripts/init_secrets.py): admin-ключ для bootstrap и ключ API с правами только на свой bucket. # Анонимного доступа нет: identity "anonymous" в конфиге не объявлена. s3: image: chrislusf/seaweedfs:3.80 entrypoint: ["/usr/bin/weed"] command: ["server", "-dir=/data", "-ip=127.0.0.1", "-ip.bind=0.0.0.0", "-master.volumeSizeLimitMB=1024", "-volume.max=0", "-s3", "-s3.port=8333", "-s3.config=/run/secrets/s3_config"] secrets: [s3_config] volumes: ["s3data:/data"] networks: [data] healthcheck: # S3-порт отвечает по HTTP (анонимный запрос получает 403 — это и есть «жив и закрыт») test: ["CMD-SHELL", "wget -q -S -O /dev/null http://127.0.0.1:8333/ 2>&1 | grep -q 'HTTP/'"] interval: 5s timeout: 3s retries: 24 start_period: 15s start_interval: 1s restart: unless-stopped stop_grace_period: 30s deploy: resources: limits: {cpus: "1.00", memory: 512M} # Одноразовый идемпотентный bootstrap (s3_init.py, образ приложения): приватный bucket + проверки. s3-init: build: *app-build command: ["python", "s3_init.py"] environment: S3_ENDPOINT: ${S3_ENDPOINT:-http://s3:8333} S3_REGION: ${S3_REGION:-us-east-1} S3_BUCKET: ${S3_BUCKET:-messenger-attachments} S3_ADMIN_ACCESS_KEY_ID_FILE: /run/secrets/s3_root_user S3_ADMIN_SECRET_ACCESS_KEY_FILE: /run/secrets/s3_root_password S3_ACCESS_KEY_ID_FILE: /run/secrets/s3_access_key_id S3_SECRET_ACCESS_KEY_FILE: /run/secrets/s3_secret_access_key secrets: [s3_root_user, s3_root_password, s3_access_key_id, s3_secret_access_key] networks: [data] depends_on: s3: {condition: service_healthy} healthcheck: disable: true restart: "no" deploy: resources: limits: {cpus: "0.25", memory: 128M} api: build: *app-build env_file: .env environment: SESSION_TTL_SECONDS: ${SESSION_TTL_SECONDS:-3600} <<: *s3-api-secrets secrets: [database_url, cache_url, s3_access_key_id, s3_secret_access_key] networks: [edge, data] depends_on: migrate: {condition: service_completed_successfully} s3-init: {condition: service_completed_successfully} redis: {condition: service_healthy} healthcheck: test: ["CMD", "python", "-c", "import urllib.request; urllib.request.urlopen('http://127.0.0.1:8080/health/ready', timeout=2)"] interval: 5s timeout: 3s retries: 3 start_period: 30s start_interval: 1s restart: unless-stopped stop_grace_period: 15s deploy: replicas: ${API_REPLICAS:-2} resources: limits: {cpus: "1.00", memory: 512M} # Очистка брошенных загрузок и сверка БД <-> S3 (janitor.py). Тот же образ и тот же ограниченный S3-ключ. janitor: build: *app-build command: ["python", "janitor.py"] env_file: .env environment: CACHE_URL_FILE: "" # janitor не ходит в Redis <<: *s3-api-secrets secrets: [database_url, s3_access_key_id, s3_secret_access_key] networks: [data] depends_on: migrate: {condition: service_completed_successfully} s3-init: {condition: service_completed_successfully} healthcheck: disable: true restart: unless-stopped stop_grace_period: 10s deploy: resources: limits: {cpus: "0.25", memory: 192M} lb: image: haproxy:3.2.25-alpine ports: - "127.0.0.1:8080:8080" - "127.0.0.1:8404:8404" volumes: - ./infra/haproxy.cfg:/usr/local/etc/haproxy/haproxy.cfg:ro networks: [edge] depends_on: api: {condition: service_healthy} healthcheck: test: ["CMD", "wget", "-q", "-T", "2", "-O", "/dev/null", "http://127.0.0.1:8404/lb-health"] interval: 5s timeout: 3s retries: 3 start_period: 10s start_interval: 1s restart: unless-stopped stop_grace_period: 15s deploy: resources: limits: {cpus: "0.50", memory: 128M} postgres: image: postgres:17.11-alpine environment: POSTGRES_USER: messenger POSTGRES_DB: messenger POSTGRES_PASSWORD_FILE: /run/secrets/postgres_password command: ["postgres", "-c", "fsync=on", "-c", "synchronous_commit=on"] secrets: [postgres_password] volumes: ["pgdata:/var/lib/postgresql/data"] networks: [data] healthcheck: test: ["CMD-SHELL", "pg_isready -h 127.0.0.1 -U messenger -d messenger"] interval: 5s timeout: 3s retries: 12 start_period: 10s restart: unless-stopped stop_grace_period: 30s deploy: resources: limits: {cpus: "1.00", memory: 512M} redis: image: redis:7.4.11-alpine command: ["redis-server", "/usr/local/etc/redis/redis.conf"] volumes: - ./infra/redis.conf:/usr/local/etc/redis/redis.conf:ro - redisdata:/data secrets: [redis_auth] networks: [data] healthcheck: test: ["CMD-SHELL", "REDISCLI_AUTH=\"$$(sed -n 's/^requirepass //p' /run/secrets/redis_auth)\" redis-cli ping | grep -q PONG"] interval: 5s timeout: 3s retries: 12 restart: unless-stopped deploy: resources: limits: {cpus: "0.50", memory: 128M} networks: edge: {} data: internal: true volumes: pgdata: {} redisdata: {} s3data: {} secrets: postgres_password: {file: ./secrets/postgres_password} database_url: {file: ./secrets/database_url} cache_url: {file: ./secrets/cache_url} redis_auth: {file: ./secrets/redis_auth} s3_root_user: {file: ./secrets/s3_root_user} s3_root_password: {file: ./secrets/s3_root_password} s3_access_key_id: {file: ./secrets/s3_access_key_id} s3_secret_access_key: {file: ./secrets/s3_secret_access_key} s3_config: {file: ./secrets/s3_config.json}