Updated readme with tons of information. Made kazuki a hercules agent. Fixed secrets ownerships. Started working on a custom installer iso. Changed helix theme.
2.1 KiB
2.1 KiB
雪定
Project structure
- hosts - per-machine configurations
- modules - options which in principle should be reusable by others
- nixos
- settei - my opinionated nixos options
- flake - flake-parts modules
- nixos
- secrets - agenix secrets
- wrappers - nix packages wrapped with my configs (see: wrapper-manager)
- assets - miscellaneous values reused throughout my config
- effects.nix - hercules-ci configuration
- deploy.nix - deploy-rs configuration
Code guidelines
Not set rules but general guidelines for myself to hopefully keep this config clean, maintainable, and reusable.
- only importing downwards. this means no
imports = [ ../../foo/bar/some-module.nix ];
- ideally only one level of imports.
this means i'll try to only do
imports = [ ./foo ];
orimports = [ ./bar.nix ]
but notimports = [ ./x/y/z.nix ];
- the file should be roughly in order of most interesting to least interesting options.
imports
should be the first attribute (except for_file
)- anything that goes into
modules
should be usable by others. any options specific to me go intohosts/default.nix
orhosts/common
. - there should be no implicit state anywhere in the config. (sounds obvious but this is already broken with legion and the zfs pool but i'll let that one slide) to achieve this i still need to create a proper live iso with my config and my bootstrapping ssh key
TODOs
Sorted rougly by priority
- finish migrating legion
- private nix cache
- set up hercules agent on legion
- hercules-ci checking if configuration is valid
- hercules-ci effects for deploying machines on update (if configuration is valid)
-
Machine not migrated yet or in the process of migrating. See: https://nest.pijul.com/nrabulinski/nix-config ↩︎