Ctrl K
ComunidadGuías…

docker-compose.profiles.yml

Rama master · réplica de lectura del repositorio original.

Archivo original ↗Preguntar a KiBot
# Docker Compose profile overlay — historical backwards-compatibility layer.
#
# This file exists only to retroactively gate services that were added to
# docker-compose.dev.yml before per-service `profiles:` was adopted there.
# It shadows those service definitions with a `profiles:` constraint so that
# `hogli dev:start` and CI can start only what's needed without breaking
# users who run `docker compose -f docker-compose.dev.yml up` directly
# (they get all services, same as before).
#
# DO NOT add new services here. New profile-gated services should define
# `profiles:` directly in docker-compose.dev.yml (see capture, plugins,
# ingestion-* for examples of the current pattern).
#
# Usage (legacy, for services still listed below):
#   docker compose -f docker-compose.dev.yml -f docker-compose.profiles.yml \
#     --profile temporal up
#
# Services not listed here have no profile constraint and always start.

services:
    # Temporal capability - workflow orchestration
    temporal:
        profiles: [temporal]
    temporal-ui:
        profiles: [temporal]
    temporal-admin-tools:
        profiles: [temporal]
    elasticsearch:
        profiles: [temporal]

    # Observability capability - tracing and logging
    otel-collector:
        profiles: [observability]
    jaeger:
        profiles: [observability]

    # Dev tools - debugging and monitoring UIs
    kafka_ui:
        profiles: [dev_tools]
    flower:
        profiles: [dev_tools]
    maildev:
        profiles: [dev_tools]
    # Also carries its own profile: a workflow's webhook step needs somewhere to point, and
    # that shouldn't cost you Kafka UI, Flower and maildev as well.
    webhook-tester:
        profiles: [dev_tools, webhook_tester]

    # Session-recording storage (replay).
    seaweedfs:
        profiles: [replay]

    # Cloud provider emulators
    objectstorage-azure:
        profiles: [azure]

    # Coordination - etcd for PersonHog and Kafka partition assignment.
    # Also in the ingestion profile: the personhog services there depend on
    # it as service_healthy, so an ingestion-profile run must bring it up.
    etcd:
        profiles: [etcd, ingestion]

    # DuckDB query server
    duckgres:
        profiles: [duckgres]

# Core services NOT listed = always start:
# - proxy, db, redis7, clickhouse, zookeeper, kafka, objectstorage, feature-flags