top-level configurations for all my NixOS machines
colin
fd48880a0a
it's annoying to rebuild on desko/lappy, and have that fail when servo is offline/unreachable. and it's really silly to have servo use its own cache *over the network*. long-term would be better to do properly distributed builds instead of the cache. |
||
|---|---|---|
| helpers | ||
| machines | ||
| modules | ||
| nixpatches | ||
| pkgs | ||
| secrets | ||
| .gitignore | ||
| .sops.yaml | ||
| flake.lock | ||
| flake.nix | ||
| readme.md | ||
| TODO.md | ||
to deploy:
nixos-rebuild --flake "./#servo" {build,switch}
more options (like building packages defined in this repo):
nix flake show
secrets
i use sops for secrets.
see modules/universal/secrets.nix for some tips.
building images
to build a distributable image (GPT-formatted image with rootfs and /boot partition):
nix build ./#imgs.lappy
this can then be dd'd onto a disk and directly booted from a EFI system.
there's some post-processing to do before running a rebuild on the deployed system (deploying ssh keys, optionally changing fs UUIDs, etc).
refer to flake.nix for more details.