Components

Single-component mode: place component fields directly at the top level (see Quick Start minimal example).

Multi-component mode: use the components map where each key is a component name (see Quick Start multi-component example).

Each component supports: runtime, image, build, provides, requires, supports, env, commands, outputs, health, depends_on, storage, restart, schedule, singleton, platform, host.

graph TD
    subgraph "HedgeDoc Launchfile"
        FE["frontend
:3001 exposed"] -->|"depends_on: healthy"| BE["backend
:3000 internal"]
        BE -->|"requires"| PG[("PostgreSQL")]
        FE -.->|"$components.backend.url"| BE
    end

Real-world examples: Chatwoot and Dify use multi-component Launchfiles with workers and frontends. Browse all apps →