Go to file
Ari Gato 09f11204fb
CI / x86_64-linux (push) Successful in 1m0s Details
CI / aarch64-linux (push) Successful in 1m24s Details
chore: flake lock updates
2024-05-17 11:10:35 +02:00
.forgejo/workflows ci: typo 2024-03-26 08:38:11 +01:00
.github/workflows ci: typo 2024-03-26 08:38:11 +01:00
modules m/common: old nix no longer needed 2024-05-16 19:34:15 +02:00
nixos n/amanojaku: missed rename 2024-05-16 21:13:14 +02:00
overlays pkgs/glitch-soc: upgrade + new attempt at packaging 2024-05-14 19:09:05 +02:00
pkgs pkgs/gltich-soc: made tl-replacer ever so slightly less horrible 2024-05-15 20:01:39 +02:00
secrets pkgs/glitch-soc: upgrade + new attempt at packaging 2024-05-14 19:09:05 +02:00
.ci.sdImages.sh crimes 2023-10-23 15:39:48 +02:00
.ci.sh crimes 2023-10-23 15:39:48 +02:00
.gitignore scaffolding 2023-09-17 21:36:58 +02:00
README.md readme update 2023-12-01 22:36:58 +01:00
ci-secrets.nix chore: fmt 2024-03-20 11:19:16 +01:00
flake.lock chore: flake lock updates 2024-05-17 11:10:35 +02:00
flake.nix chore: fmt, renames 2024-05-07 00:19:20 +02:00
meta.nix meta: avoid repetition with targetHost 2024-02-18 13:43:54 +01:00
secrets.nix pkgs/glitch-soc: upgrade + new attempt at packaging 2024-05-14 19:09:05 +02:00

README.md

My personal NixOS infrastructure configurations

This repository contains configurations for Most™ of my NixOS machines.

All of the host configurations are deployable using deploy-rs, colmena, and plain old nixos-rebuild. See deploy.nodes and colmena crimes in flake outputs for details how. Initial host deploment, sadly, needs to happen manually (for now at least). Secrets are managed using agenix, instead of any deployment-tool-native secret manager.

General usage

Adding new module

$ echo -e "{ config, lib, pkgs, inputs, ... }:\n\n{\n}" > modules/new-module.nix

Adding new host

$ mkdir nixos/newhost
$ echo -e "{ config, lib, pkgs, inputs, ... }:\n\n{\n}" > nixos/newhost/default.nix
$ echo '{"publicKey": "…", "targetHost": "…", "system": "aarch64-linux"}' | jq -rM > nixos/newhost/meta.json

Exploring generated configurations

Colmena has a nice feature here called colmena repl. Go out there and explore nodes and its attributes.

Before you commit

To keep things clean, uniform, and working at least on some basic level, remember to:

$ nix flake check --no-build
$ nix fmt

Small bit of warning: nix fmt, with formatters as configured (deadnix specifically) will remove unused variables and such. Might be annoying when things are work-in-progress.

Deploying new configurations

There are multiple options here. You can use nixos-rebuild either locally:

$ sudo nixos-rebuild switch --flake .#microlith

remotely:

$ nixos-rebuild switch --target-host root@zorigami --build-host root@zorigami --flake .#zorigami

remotely using deploy-rs:

$ deploy .#scylla

or using colmena:

$ colmena apply --on khas

All of these should generally work, though I prefer to use deploy-rs on my router (because of magic rollback) when deploying bigger changes, and colmena in most cases, because it's faster. And if the changes you're about to deploy had a chance to be built by "CI", most stuff shouldn't need to be built locally.

Warnings about colmena and deploy being unknown flake outputs are known, and will stay here at least until schemas get implemented for these.

General notes

Feel free to use this as a basis for your own configuration flakes, but while I keep things here working for me, the general state might not reflect best practices. Use caution, and if you feel like you don't really understand something (and there are some code crimes commited here), don't feel obliged to use it just because it's already here.