docker-compose.yml Generator

Generate a compose.yaml for local development with MySQL, PostgreSQL, Redis, Mailpit, Meilisearch, MinIO, RabbitMQ or Adminer, with healthchecks and volumes.

Free · No sign-up · Your inputs stay in your browser

Output

compose.yaml

1,063 characters

services:
  app:
    build: .
    ports: ["127.0.0.1:3000:3000"]
    env_file: .env
    depends_on:
      postgres:
        condition: service_healthy
      redis:
        condition: service_healthy
    develop:
      watch:
        - action: sync
          path: ./src
          target: /app/src

  postgres:
    image: postgres:17
    restart: unless-stopped
    environment:
      POSTGRES_DB: app
      POSTGRES_USER: app
      POSTGRES_PASSWORD: secret
    ports: ["127.0.0.1:5432:5432"]
    volumes: [postgres-data:/var/lib/postgresql/data]
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U app -d app"]
      interval: 5s
      retries: 10

  redis:
    image: redis:7.4-alpine
    restart: unless-stopped
    command: ["redis-server", "--appendonly", "yes"]
    ports: ["127.0.0.1:6379:6379"]
    volumes: [redis-data:/data]
    healthcheck:
      test: ["CMD", "redis-cli", "ping"]
      interval: 5s

  mailpit:
    image: axllent/mailpit:latest
    ports: ["127.0.0.1:8025:8025", "127.0.0.1:1025:1025"]

volumes:
  postgres-data:
  redis-data:

Every port is published on 127.0.0.1 only: Docker writes its own iptables rules, so a plain 3306:3306 is reachable from the internet on a server even with ufw denying it. depends_on with condition: service_healthy waits for the healthcheck, not just for the container to start. Pin the latest tags before sharing the file.

Runs in this browser. Nothing you paste is sent to a server.

About this tool

Method, assumptions, practical next steps, and limits.

Publish on localhost

Docker inserts its own iptables rules for published ports, ahead of ufw's, so 3306:3306 on a server is reachable from the internet even with the firewall denying it. Binding to 127.0.0.1:3306:3306 keeps a database private. The packet filtering documentation explains the interaction.

Healthchecks and start order

depends_on alone only waits for a container to start, and a database accepts connections seconds later. With a healthcheck and condition: service_healthy, the app waits until the database answers, which removes the retry loop most entrypoint scripts carry.

Frequently asked questions

Is the version key needed in a Compose file?

No. The Compose Specification has no version key; Docker Compose v2 ignores it and prints a warning, so leave it out.

Where does Compose store the database data?

In the named volumes declared at the bottom. docker compose down keeps them; docker compose down -v deletes them.

Is what I paste sent anywhere?

No. The tool runs entirely in your browser with JavaScript. Nothing you type or paste is sent to our server or stored.

docker-compose.yml Generator

Generate a docker-compose.yml for local development

compose.yaml

Publish on localhost

Healthchecks and start order

Frequently asked questions

Similar tools

File Transfer Time Calculator

IPv6 Subnet Calculator

.env File Diff