Closed otoolep closed 3 months ago
With this build I'm able to then load sqlean into the version of rqlite which is built by musl (and which is used when creating rqlite Docker).
I think musl builds are a great idea and I will try to incorporate them into the overall build pipeline. Thank you!
Thanks.
You can see what I did here -- for Docker I made the download-sqlean-and-build process part of the image-creation itself, and it actually worked pretty well.
This now means that the Sqlean extensions are baked into the rqlite Docker image, and can be enabled simply by setting an Environment Variable. Pretty nice, if you ask me.
Sure, it's a great self-contained approach. And you don't have to rely on Sqlean builds.
This is a PR just to communicate what I have in mind. Feel free to close.
Have you considered also adding musl builds to your releases? I tried these Makefile changes out (I have the musl-gcc compiler installed), and they worked great.
Why do this?
It would mean you would have a release ready for use inside alpine images, which are very popular as small-footprint Docker images. rqlite uses alpine for its Docker images, for example.