mirror/conduit - conduit - xhrpb gitea

Author	SHA1	Message	Date
Charles Hall	15e60818c9	pin nixos-unstable, update flake.lock `nixos-unstable` is the rolling release channel of NixOS. The default is the master branch, which doesn't always have a populated binary cache and so may result in compiling a bunch of stuff unnecessarily.	3 years ago
Charles Hall	55149e3336	use crane instead of naersk I guess naersk still doesn't support git dependencies using workspace inheritance, but crane does.	3 years ago
Charles Hall	a0c449e570	update flake.lock	3 years ago
Charles Hall	c997311bea	Revert "build(nix): fix flake builds" This reverts commit `5d913f7010`. Sorry, I don't understand how any of this works, and it seems pretty opaque/difficult to fine-tune.	3 years ago
Yusuf Bera Ertan	5d913f7010	build(nix): fix flake builds	3 years ago
Charles Hall	9f74555c88	update flake.lock	3 years ago
Charles Hall	fe7d8c4f12	add nix flake Also add `.envrc` for direnv + Nix users. This makes developing locally easier for us NixOS folks. The flake itself will allow NixOS users to pull code directly from Conduit's repository, making it completely trivial to stay up-to-date with every commit. I'd also like to add a NixOS module directly to this repository at some point so that new configuration options will be available in the NixOS module faster. But for now, NixOS users can simply override `serivces.matrix-conduit.package` and get pretty much all the functionality. I've added myself to the `CODEOWNERS` file for the Nix files, since I am willing to maintain this stuff. I use Conduit on NixOS so I'm personally invested in having this work. Lastly, `.gitignore` was updated to exclude symlinks created by `direnv` and `nix build` and other such Nix commands. This doesn't come without maintenance burden, however: * The `sha256` in `flake.nix` will need to be updated whenever Conduit's MSRV is updated, but that should be pretty infrequent. * `nix flake update` should be run every so often to pull in updates to `nixpkgs` and other flake inputs. I think downstream users can also override this themselves with `inputs.<name>.inputs.<name>.follows`. * `nix flake check` should be run in CI to ensure Nix builds keep working. * `nixpkgs-fmt --check $(fd '\.nix')` (or similar) should be run in CI to ensure style uniformity.	3 years ago