docker-compose.production.yml

# This is a transitional production configuration.
# Traffic or NGINX may or may not be used in the final production configuration
# but the Django container will not expose its port to the host (there will be more than one container).

services:
  django: &django
    build:
      context: .
      # This is the most important setting to test the production configuration of Django.
      dockerfile: ./compose/production/django/Dockerfile
    image: insectai/ami_backend
    env_file:
      - ./.envs/.production/.django
      - ./.envs/.production/.postgres
    volumes:
      - ./config:/app/config
    ports:
      - "5001:5000"
    extra_hosts: # hostname aliases to the IPs of persistant services running outside docker network
      - "db:${DATABASE_IP}"
      - "rabbitmq:${RABBITMQ_IP}"
      - "redis:${REDIS_IP}"
      - "nats:${NATS_IP}"
    command: /start
    scale: 1  # Can't scale until the load balancer is within the compose config
    restart: always

  # Only the antenna (default) queue runs here, alongside beat. The jobs and
  # ml_results queues are served by dedicated worker hosts (see
  # docker-compose.worker.yml) so heavy, bursty ML work doesn't compete with
  # Django/beat for CPU and memory on this box.
  celeryworker:
    <<: *django
    scale: 1
    ports: []
    command: /start-celeryworker
    environment:
      CELERY_QUEUES: "antenna"
    restart: always

  celerybeat:
    <<: *django
    ports: []
    command: /start-celerybeat
    restart: always

  flower:
    <<: *django
    ports:
      - "5550:5555"
    command: /start-flower
    restart: always
    volumes:
      - ./data/flower/:/data/

  awscli:
    build:
      context: .
      dockerfile: ./compose/production/aws/Dockerfile
    env_file:
      - ./.envs/.production/.django
    volumes:
      - ./backups/production/postgres:/backups:z