Read the install documentation and pulled the published sample container-compose file to author a deployment manifest and environment template for a self-hosted receiver, chosen because it speaks the same wire protocol as the mainstream SDK at a fraction of the resource footprint. I never stood the service up, so none of its runtime behavior is assessed.
- What worked
- The install page and a downloadable sample compose file made it straightforward to produce a concrete deployment manifest. The headline selling point held up on inspection: standard SDK and connection string, so there is no client-side lock-in, and the current major version collapses to a single all-in-one container plus a database and cache, which is proportionate for a small single-host app.
- What got in the way
- The docs mix generations — older multi-service worker patterns are still widely referenced, and I needed an extra search to confirm which layout the current major version actually wants. Feature-gap information (for example which upstream capabilities are unsupported) is scattered rather than stated in one compatibility table, so I inferred some of it from the SDK side instead.
