Skip to content

jeremylongshore/tons-of-skills-marketplace / plugins/devops/docker-compose-generator/skills/generating-docker-compose-files

generating-docker-compose-files

Verified

Execute use when you need to work with Docker Compose. This skill provides Docker Compose file generation with comprehensive guidance and automation. Trigger with phrases like "generate docker-compose", "create compose file", or "configure multi-container app".

FileKindSize
SKILL.mdskill md4.3 KB
assets/README.mdmarkdown305 B
assets/compose_template.ymlconfig3.3 KB
assets/example_app_architectures.mdmarkdown6.7 KB
references/README.mdmarkdown67 B
scripts/README.mdmarkdown382 B
scripts/deploy.shexecutablescript11.3 KB
scripts/generate_env_file.pyexecutablescript11.1 KB
scripts/validate_compose.shexecutablescript7.2 KB

assets/compose_template.yml

View on GitHub
version: "3.9"

# Define services for your application
services:

  # Example web application service
  web:
    image: nginx:latest # Replace with your web application image
    container_name: web_app
    ports:
      - "80:80" # Expose port 80 for HTTP traffic
      - "443:443" # Expose port 443 for HTTPS traffic (configure SSL certificates)
    volumes:
      - ./html:/usr/share/nginx/html # Mount your web application files
      - ./nginx/conf.d:/etc/nginx/conf.d # Mount Nginx configuration files
    depends_on:
      - app # Ensure the app service is running before starting the web service
    restart: always # Restart the service if it fails
    healthcheck:
      test: ["CMD-SHELL", "curl -f http://localhost || exit 1"] # Check if the web server is responding
      interval: 30s # Check every 30 seconds
      timeout: 10s # Timeout after 10 seconds
      retries: 3 # Retry up to 3 times
    networks:
      - app_network # Connect to the application network
    deploy:
      resources:
        limits:
          cpus: "0.5" # Limit CPU usage to 0.5 cores
          memory: 512M # Limit memory usage to 512MB
    environment:
      - example-value=YOUR_VALUE_HERE # Example environment variable

  # Example application service
  app:
    build:
      context: ./app # Path to the application Dockerfile
    container_name: app_service
    environment:
      - DATABASE_URL=postgres://user:password@db:5432/database # Database connection string
      - SECRET_KEY=YOUR_SECRET_KEY # Secret key for your application
    depends_on:
      - db # Ensure the database service is running before starting the app service
    restart: always # Restart the service if it fails
    healthcheck:
      test: ["CMD-SHELL", "curl -f http://localhost:8000/health || exit 1"] # Check if the application is responding
      interval: 30s # Check every 30 seconds
      timeout: 10s # Timeout after 10 seconds
      retries: 3 # Retry up to 3 times
    networks:
      - app_network # Connect to the application network
    deploy:
      resources:
        limits:
          cpus: "1" # Limit CPU usage to 1 core
          memory: 1G # Limit memory usage to 1GB
    volumes:
      - ./app:/app  # Mount the application code

  # Example database service
  db:
    image: postgres:14 # Use Postgres version 14
    container_name: database
    volumes:
      - db_data:/var/lib/postgresql/data # Persist database data
    environment:
      - POSTGRES_USER=user # Database user
      - POSTGRES_PASSWORD=password # Database password
      - POSTGRES_DB=database # Database name
    restart: always # Restart the service if it fails
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U user -d database"] # Check if the database is ready
      interval: 30s # Check every 30 seconds
      timeout: 10s # Timeout after 10 seconds
      retries: 3 # Retry up to 3 times
    networks:
      - app_network # Connect to the application network
    deploy:
      resources:
        limits:
          cpus: "0.5" # Limit CPU usage to 0.5 cores
          memory: 512M # Limit memory usage to 512MB

# Define networks for communication between services
networks:
  app_network:
    driver: bridge # Use a bridge network for internal communication

# Define volumes for persistent data storage
volumes:
  db_data: # Volume for database data
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 323kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall