Docker Compose Templates

Here is a collection of production-ready docker-compose.yml templates for common application stacks.

Node.js + PostgreSQL

services:
  api:
    build: .
    ports:
      - "3000:3000"
    environment:
      - DATABASE_URL=postgres://user:pass@db:5432/dbname
    depends_on:
      - db

  db:
    image: postgres:15-alpine
    environment:
      POSTGRES_USER: user
      POSTGRES_PASSWORD: pass
      POSTGRES_DB: dbname
    volumes:
      - db-data:/var/lib/postgresql/data

volumes:
  db-data:

Python (Flask/Django) + Redis

services:
  web:
    build: .
    ports:
      - "8000:8000"
    environment:
      - REDIS_URL=redis://redis:6379/0
    depends_on:
      - redis

  redis:
    image: redis:7-alpine
    volumes:
      - redis-data:/data

volumes:
  redis-data:

WordPress + MySQL

services:
  wordpress:
    image: wordpress:latest
    ports:
      - "8080:80"
    environment:
      WORDPRESS_DB_HOST: db
      WORDPRESS_DB_USER: wp_user
      WORDPRESS_DB_PASSWORD: wp_password
      WORDPRESS_DB_NAME: wp_db
    volumes:
      - wp-content:/var/www/html

  db:
    image: mysql:5.7
    environment:
      MYSQL_DATABASE: wp_db
      MYSQL_USER: wp_user
      MYSQL_PASSWORD: wp_password
      MYSQL_ROOT_PASSWORD: root_password
    volumes:
      - db-data:/var/lib/mysql

volumes:
  wp-content:
  db-data:

Nginx Reverse Proxy

services:
  proxy:
    image: nginx:alpine
    ports:
      - "80:80"
    volumes:
      - ./nginx.conf:/etc/nginx/conf.d/default.conf:ro
      - ./html:/usr/share/nginx/html:ro

Best Practices for Templates

1. Use Alpine Images: They are smaller and faster (postgres:15-alpine).
2. Named Volumes: Always use named volumes for databases to ensure data persistence.
3. Environment Variables: Don't hardcode secrets in production. Use .env files.
4. Restart Policies: Add restart: unless-stopped for production services.

---

One-Click Deploy

Hostim.dev has a built-in template library. Select a template and deploy in seconds.

Browse Templates on Hostim.dev