Prebuilt artifacts/binaries

[JensRantil]

Hey, I was about to give Bedrock a spin ~6 months ago and ran into issues building it on MacOSX, then gave up concluding it was too much work. The issues were unclear and long forgotten by now, but just wanted to create this issue as a feature request to have prebuilt binaries/artifacts. I think it would benefit the project by reducing the friction significantly to start using Bedrock, both for developers, but also for rolling out in production.

The fact that every shop must build Bedrock themselves, host their own binaries somewhere etc. I think it a big friction point to convince ops people it's a good database to go with.

[quinthar]

Yep, I totally agree, but this is much easier said than done. It's a good suggestion, eager for your PRs!

[JensRantil]

A good start is probably to focus on creating an official Docker image. It would be isolated and recreatable and avoid issues with dynamic libs etc. Given that Travis CI build is working and there is a script that could be the basis for starting this work.

[AstraLuma]

+1 for containers.

Makes it easier to spin up test environments and clusters.

Makes development environments simpler.

Enables Bedrock on container orchestrators.

[Jaspooky]

+1, a Docker container would be great for starting out with Bedrock