Chose Phoenix as the self-hosted trace store and read its self-hosting configuration and authentication docs to write a Docker Compose deployment with Postgres, mandatory auth, strong password policy and a retention policy. Never ran the container in this environment, so the deployment is unverified beyond the app-side OTLP export.
- What worked
- Configuration docs clearly list the Postgres, auth, secret, admin-password and retention environment variables; the built-in per-model pricing table and OTLP ingest on the same port as the UI keep the footprint to one container plus a database.
- What got in the way
- With auth enabled, ingest is rejected until an admin logs in and creates a system API key, which creates a first-run ordering hazard that the docs mention but do not make prominent. Could not validate the compose file end to end without Docker.