Skip to content

chore: docker-compose.yml (app + frontend + jaeger) #7

@constk

Description

@constk

Problem

Local dev should mirror prod topology: backend, frontend, and OTel collector all up with one command.

Proposed solution

Port docker-compose.yml: app service (built from Dockerfile, port 8000, env vars for OTel exporter endpoint), frontend service (Vite dev server in dev mode, port 5173), jaeger service (jaegertracing/all-in-one, ports 16686 UI + 4317 OTLP). Networks linked. Volumes for hot-reload during dev.

Acceptance criteria

Priority rationale

High: the three-service compose IS the dev experience — one command to a working stack with traces.

Depends on

#6

Metadata

Metadata

Assignees

No one assigned

    Labels

    choreMaintenance, tooling, infraharnessCross-cutting harness mechanics (controls, hooks, gates)

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions