Feature: Turn this repo into a Nix flake about surrealdb

[rushmorem]

Out of interest, how does the build process work from a dependency point of view? (as you know tikv-client builds fine in Github > Actions CI, but is tricky to build outside of that environment).

From NixOS' homepage:

Nix builds packages in isolation from each other. This ensures that they are reproducible and don't have undeclared dependencies, so if a package works on one machine, it will also work on another.

Does it work with Github Releases, or build from source?

It works with either. It can also work with binaries too. The preferred way of packaging in the Nix community, though, is to package from source.

Either way, definitely interested in investigating this...

You don't need to spend any time on this. I have been using NixOS since 2014. I already have a working flake I packaged using Naersk but I want to first convert it to Crane because it comes with some interesting features I think will be very helpful with our development environments.

[rushmorem]

Presumably statically-build binaries would be more suitable for the Nix packages?

Not really. Nix saves its packages inside /nix/store inside paths like /nix/store/0ignl03zfg6mvs50z4n929b6pyx3rhqj-rustc-1.61.0-x86_64-unknown-linux-gnu/. That's how it's able to have packages of different versions on the same system. The dependencies are dynamically linked by default.

[tobiemh]

Ok this sounds interesting @rushmorem .

Out of interest, how does the build process work from a dependency point of view? (as you know tikv-client builds fine in Github Actions CI, but is tricky to build outside of that environment).

Does it work with Github Releases, or build from source?

Either way, definitely interested in investigating this...

[tobiemh]

Ok awesome @rushmorem . A musl build for Alpine Linux should also be on our roadmap at some point. Presumably statically-build binaries would be more suitable for the Nix packages?

[rushmorem]

Implemented in #100.