Ctrl K
ComunidadGuías…

compose.yaml

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

Archivo original ↗Preguntar a KiBot
# Top-level stack (ADR-0006): the data plane plus enabled modules, assembled from
# fragments. `docker compose up -d` (or `task up`) brings up everything — the local AI
# runtime included, with no `.env`, no profile and no flags. That is the install the README
# and docs/user/installation.md publish, and nothing added here may quietly ask more of it:
# anything optional is layered *over* this file as an overlay the operator opts into.
#
#   services/core-app/compose.docker-socket.yaml    the raw Docker socket (#708)
#   services/core-app/compose.external-mounts.yaml  extra Files roots from the host (#731)
#   infra/ollama/compose.hosted-only.yaml           no local AI runtime at all (#962)
#
# (`--profile observability` is the one profile the stack uses, and it *adds* services.)
#
# Each module contributes its own services/<name>/compose.yaml fragment; add a
# module by including its fragment here (the installer does this dynamically
# later). Shared infra lives in infra/compose/docker-compose.yml.
name: epicurus

include:
  - infra/compose/docker-compose.yml
  - infra/edge/compose.yaml
  - infra/observability/compose.yaml
  - infra/ollama/compose.yaml
  - infra/searxng/compose.yaml
  - services/echo/compose.yaml
  - services/core-app/compose.yaml
  - services/storage/compose.yaml
  - services/knowledge/compose.yaml
  - services/websearch/compose.yaml
  - services/calendar/compose.yaml
  - services/mail/compose.yaml
  - services/tasks/compose.yaml
  - services/web/compose.yaml
  - services/notes/compose.yaml
  - services/messaging/compose.yaml