Ο Mailvane στο δικό σου VPC, χωρίς trade-offs.

# docker-compose.yml — deploy Mailvane on-prem
# Two services. Bring your own secrets via .env (never commit it).

version: '3.9'

# Web container: the Mailvane app + scheduler.
# Reads DATABASE_URL to reach Postgres, signs sessions with NEXTAUTH_SECRET,
# sends outbound email through the Polsia email proxy (egress only — no
# inbound webhook, no control plane). Exposes port 3000 on your VPN/VPC.
services:
  web:
    image: ghcr.io/mailvane/app:<tag>
    restart: unless-stopped
    ports:
      - '3000:3000'
    environment:
      DATABASE_URL: ${DATABASE_URL}
      NEXTAUTH_SECRET: ${NEXTAUTH_SECRET}
      POLSIA_API_BASE_URL: ${POLSIA_API_BASE_URL}
      OAUTH_GOOGLE_CLIENT_ID: ${OAUTH_GOOGLE_CLIENT_ID}
      OAUTH_GOOGLE_CLIENT_SECRET: ${OAUTH_GOOGLE_CLIENT_SECRET}
      OAUTH_MICROSOFT_CLIENT_ID: ${OAUTH_MICROSOFT_CLIENT_ID}
      OAUTH_MICROSOFT_CLIENT_SECRET: ${OAUTH_MICROSOFT_CLIENT_SECRET}
    depends_on:
      - postgres

# Postgres: stores accounts, threads, and the audit log inside your VPC.
# Named volume persists data across container restarts; back up with your
# existing snapshot cadence.
  postgres:
    image: postgres:16-alpine
    restart: unless-stopped
    environment:
      POSTGRES_USER: mailvane
      POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
      POSTGRES_DB: mailvane
    volumes:
      - pgdata:/var/lib/postgresql/data

volumes:
  pgdata: null