This website requires JavaScript.
Explore
Cloud
Chat
CI/CD
Help
Sign in
MirrorHub
/
conduit
Watch
1
Star
0
Fork
You've already forked conduit
0
mirror of
https://gitlab.com/famedly/conduit.git
synced
2024-11-16 18:10:51 +01:00
Code
Issues
Releases
Activity
18e684b92e
conduit
/
.envrc
6 lines
45 B
Text
Raw
Normal View
History
Unescape
Escape
add shebang to .envrc All this really does is make syntax highlighting and shellcheck work by default in more editors.
2023-12-24 07:02:24 +01:00
#!/usr/bin/env bash
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.
2022-10-15 22:02:13 +02:00
use flake
add script to build and push to binary cache This is even useful for local development, as you can pre-populate the binary cache before running CI (assuming you have the token). Also, it being in a script makes it easier to test. We've added attic as a flake input even though the flake itself doesn't use it so that we can use `--inputs-from .` in Nix commands to reference a locked version of attic. This helps with reproducibility and caching, and to makes it easy to update attic because it's part of the normal flake lifecycle.
2024-01-25 20:34:46 +01:00
PATH_add bin
Reference in a new issue
Copy permalink