generate-compose-with-labels

Generate docker-compose.yml with Traefik labels, networks, healthchecks, and docs.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/chris78rey/en_construccion --skill generate-compose-with-labels
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-compose-with-labels
Source: https://github.com/chris78rey/en_construccion/tree/main/.opencode/skills/generate-compose-with-labels
Command: npx skills add https://github.com/chris78rey/en_construccion --skill generate-compose-with-labels

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Este Skill automatiza la creación de un docker-compose.yml de producción con etiquetas de Traefik y configuración para Coolify, eliminando la necesidad de configurar etiquetas manualmente en la UI.

Core Features & Use Cases

  • Genera un docker-compose completo con servicios públicos detrás de Traefik y redes necesarias.
  • Configura en automático routers, TLS/Let’s Encrypt y middlewares para redirección HTTP→HTTPS.
  • Incluye healthchecks, volúmenes nombrados y variables de entorno externalizadas.
  • Soporta escenarios con múltiples servicios (API, frontend, base de datos, caché).

Quick Start

Pide un docker-compose completo especificando: nombre del stack, dominio público, servicios a incluir, puertos internos de cada servicio, imágenes y versiones, y variables sensibles para externalizar. Por ejemplo: Genera docker-compose para stack 'myapp' con API Node en 3000, frontend React en 8080, dominio 'app.da-tica.com', imágenes 'node:18.20.1-alpine3.18' y 'react-scripts:latest', y variables DATABASE_URL y API_KEY.

Frequently Asked Questions about generate-compose-with-labels

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a docker-compose.yml with Traefik labels and TLS automatically?

To generate a docker-compose.yml with Traefik labels automatically, provide the stack name, public domain, services, internal ports, fixed image tags, and externalized variables to get a production-ready file with routers, TLS, and HTTP to HTTPS redirects.

Can I use Coolify with a multi-service docker-compose stack that has a public domain?

Yes, Coolify works with multi-service docker-compose stacks by applying Traefik labels automatically for routing and TLS, while configuring integrated networks, healthchecks, and named volumes for services like APIs, frontends, and databases.

What's the best way to configure healthchecks and named volumes in a production docker-compose file?

The best way to configure healthchecks and named volumes in a production docker-compose file is by auto-generating the configuration with fixed image tags, exposed ports, and externalized environment variables for a multi-service stack.

Does this approach to docker-compose generation support externalizing sensitive variables like API keys?

Yes, this docker-compose generation approach supports externalizing sensitive variables like API keys and database URLs by referencing them in the environment configuration without hardcoding secrets directly into the compose file.

Why do I need to specify fixed image tags when generating a docker-compose configuration?

You need to specify fixed image tags when generating a docker-compose configuration to ensure deployment stability and prevent unexpected breaking changes from rolling tags across your multi-service stack.

When do I need Traefik middlewares for HTTP to HTTPS redirection in docker-compose?

You need Traefik middlewares for HTTP to HTTPS redirection in docker-compose when exposing public services with a domain, ensuring automated TLS via Let's Encrypt and secure routing across your application stack.