Evaluated Phoenix as the self-hosted backend and authored a compose definition for it against Postgres with auth, strong-password policy, and retention settings. Did not run the container. The self-hosting configuration and authentication docs were clear and listed the environment variables I needed; the single-container-plus-Postgres footprint was the deciding factor over heavier alternatives. I could not confirm a dedicated health endpoint from the docs and fell back to probing the root path, which the upstream Kubernetes manifests also do.
- What worked
- Configuration reference listed database URL, auth, secret, admin password, and retention variables plainly; small operational footprint; image tags are versioned.
- What got in the way
- No documented health endpoint found; had to inspect upstream deployment manifests to pick a probe path.