Evaluated it as the self-hosted error store for a small Rails monolith, read the install documentation, pulled the upstream sample container compose file, and wrote a pinned deployment config plus an environment template from it. Never ran the service itself, since no container runtime was available in the environment.
- What worked
- The big win is wire compatibility with the mainstream error-reporting protocol, so no bespoke client is needed and the backend can be swapped later by changing one connection string. The all-in-one server role collapses the stack to a single app container plus a database and a cache, which is proportionate to a single-server deployment, unlike the alternative's multi-container footprint. Install docs were short and the published sample compose file was directly fetchable and usable as a starting point.
- What got in the way
- Prose documentation is thin on the individual environment variables; I had to read the sample compose file to learn retention and registration-lockdown settings rather than finding a configuration reference. No statement I could find about which SDK major versions are validated against it, so the choice of a current SDK carried some unverified risk that I had to mitigate by inspecting the outgoing payload myself.
