Docker Compose for Local Development: The Perfect Developer Environment

Docker Compose defines multi-container applications in a single YAML file. Run docker compose up and your entire stack—Flask app, PostgreSQL, Redis, Celery workers, and even a local mail catcher—starts in seconds with the exact same configuration every time, on any machine.

Complete Development Stack

services:
  api:
    build: .
    ports: ["5001:5001"]
    volumes: ["./backend:/app"]  # Hot reload
    environment:
      DATABASE_URL: postgresql://mirahlabs:secret@db/mirahlabs
      REDIS_URL: redis://redis:6379/0
      FLASK_DEBUG: "1"
    depends_on:
      db:
        condition: service_healthy
      redis:
        condition: service_started

  db:
    image: postgres:16-alpine
    environment:
      POSTGRES_DB: mirahlabs
      POSTGRES_PASSWORD: secret
    volumes: ["pg_data:/var/lib/postgresql/data"]
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U postgres"]
      interval: 5s

  redis:
    image: redis:7-alpine

  worker:
    build: .
    command: celery -A app.celery worker --loglevel=info
    environment:
      DATABASE_URL: postgresql://mirahlabs:secret@db/mirahlabs
    depends_on: [db, redis]

  mailpit:
    image: axllent/mailpit
    ports: ["8025:8025"]  # Web UI for captured emails

volumes:
  pg_data:

Volume Mounting for Hot Reload

Mount your source code as a volume so Flask's debug reloader picks up changes without rebuilding the container. This gives you the same fast iteration speed as running Flask natively while keeping dependencies isolated.

Docker Compose Override Files

Use docker-compose.override.yml for developer-specific settings (like exposing extra ports for debugging) that shouldn't be in the base file. This file is gitignored and applied automatically when present.

Production Multi-Stage Dockerfile Blueprint

Below is a secure, multi-stage production Dockerfile designed to minimize image size and eliminate security vulnerabilities by running as a non-privileged user:

# Stage 1: Build virtual env
FROM python:3.11-slim AS builder
WORKDIR /app
RUN apt-get update && apt-get install -y --no-install-recommends gcc libpq-dev && rm -rf /var/lib/apt/lists/*
RUN python -m venv /opt/venv
ENV PATH="/opt/venv/bin:$PATH"
COPY requirements.txt .
RUN pip install --no-cache-dir -r requirements.txt

# Stage 2: Final lightweight image
FROM python:3.11-slim
WORKDIR /app
RUN apt-get update && apt-get install -y --no-install-recommends libpq-dev && rm -rf /var/lib/apt/lists/*
COPY --from=builder /opt/venv /opt/venv
COPY . .
ENV PATH="/opt/venv/bin:$PATH"
ENV PYTHONUNBUFFERED=1
RUN useradd -u 10001 appuser && chown -R appuser:appuser /app
USER 10001
EXPOSE 8080
CMD ["gunicorn", "--bind", "0.0.0.0:8080", "run:app"]

Cloud Infrastructure Performance Profile

Below is a comparative latency and throughput profile of this infrastructure pattern deployed under a simulated load of 10,000 concurrent requests:

US & UK DevOps Governance & Infrastructure Security

Automating infrastructure and deployment workflows must respect regional privacy laws. Under the UK GDPR and US California Consumer Privacy Act (CCPA), system administrators must ensure that data pipelines respect strict boundaries regarding where user telemetry and system logs are stored (data residency). Implementing secure deployment methods (such as the NIST Secure Software Development Framework - SSDF) ensures that pipeline secrets are securely managed in systems like HashiCorp Vault, and that container configurations undergo automated security scanning before being shipped to production environments.