commit | ec13fbd7a8bfe2eff569df5ad77d007599bbffc2 | [log] [tgz] |
---|---|---|
author | Skyler Grey <sky@a.starrysky.fyi> | Sat Aug 03 08:11:04 2024 +0000 |
committer | Skyler Grey <minion@clicks.codes> | Thu Aug 08 21:25:44 2024 +0000 |
tree | 0939effdc252adb440e26e6b55b79e178ad70509 | |
parent | d8ae8d9fe17014aab45eeee7bcb17ccc8d9256c3 [diff] |
feat: Make modules evauluate without dependencies Previously, module checks would stop us from evaluating if we didn't include all of our dependencies' modules too. This became cumbersome if someone was importing our flake, especially since as Nix doesn't stop duplicate dependencies from being imported twice... ...by using optionalAttrs anywhere a dependency is needed, we stop Nix being able to check that our options are valid, working around the issue --- It's way too easy to make a mistake here, a first version of this change had a bug where due to something like this... x = lib.mkIf cfg.enable { } // { foo = lib.optionalAttrs ... } ...which evaluates as... x = { _type = "if"; value = ...; foo = lib.optionalAttrs ...; ...; } ...we ended up dropping the impermanence options which mount our storage It's really critical, therefore, to check that you aren't munging attrsets into mkIf statements when you start using a mix of them Change-Id: I7b786af965b3fd1012d956262aea72305b60db27 Reviewed-on: https://git.clicks.codes/c/Infra/NixFiles/+/811 Reviewed-by: Skyler Grey <minion@clicks.codes> Tested-by: Skyler Grey <minion@clicks.codes>
This repository contains system configuration for Clicks's infrastructure.
Config is written using Snowfall lib. It keeps us organized and has some nice features like namespaces.
Devices are named after colors, areas are named as a letter, with the matching phonetic alphabet word. Areas are generally managed by one member of Clicks, who has full access to all of the servers in that area. If you require help for a specific area you can email admin@clicks.codes
and in the subject line include the area you want help for.
System | Description | Address |
---|---|---|
teal | Primary Host | teal.alpha.clicks.domains |
a1d2 | Build Server | d2.a1.clicks.domains |
Deploys are done with deploy-rs, you'll need to be able to ssh into a machine with its hostname (either by a nifty .ssh/config
rule or tailscale
).
Once you've done that, you'll be able to deploy with
$ deploy .#MACHINE_NAME
If you're importing our modules, even if you don't enable most of them, you'll find it easiest and best to import them all. This is because the nixpkgs module system checks if all given options are defined, even if they aren't enabled in your specific configuration.
The module system doesn't do this with traditional if
statements or lib.optionalAttrs
, only lib.mkIf
, so we've made sure to use lib.optionalAttrs
for anything that depends on things not in this list:
nixpkgs
We expect the majority of you will already have all of these imported. We use and test against stateVersion = "24.05"
, and while we expect these modules to generally work with earlier or later stateVersion
s, please be aware that this could cause unexpcted effects
We may also depend on:
lib.nixosSystem
(lib
, pkgs
, etc.) being passed into our moduleslib
being extended such that lib.clicks
is equal to the lib
exported from our flakeWe expect the lib
extension to be a minor change, and providing standard arguments to modules to already be the case.
This means that, provided you don't enable any options, importing the Clicks modules will be safe so long as your flake fulfils all of these factors: we won't break eval and we won't change any of your settings. If you'd like to see how we test that, please check out ./modules.spec.nix
We expect no additions to this list, except a potential future change of adding auxolotl modules to this list when we consider them stable and easily-importable. Additions to this list will always be considered breaking changes.
(n.b. If you're wondering why we didn't use lib.optionalAttrs
everywhere, it's because using it loses us some laziness, making it much easier to make infinite recursions. If we replaced every lib.mkIf
with lib.optionalAttrs
in our own config, for instance, it would no longer evaluate)