Repository containing our nix infrastructure configuration. It simply provides nixosConfigurations for each host and can be easily deployed using tools like infra-rebuild, bij or even nixos-rebuild.

infrastructure nix nixos

Find a file

christian 579b63fe89 Update authorizedKeysRepo rev in common/users.nix to add echtnurich secondary device key		2024-06-08 21:39:24 +02:00
config	Update authorizedKeysRepo rev in common/users.nix	2024-06-08 21:39:24 +02:00
modules/services/audio	Make MPD be put into pause mode instead of start. playback after startup	2024-05-23 22:25:32 +02:00
.gitignore	Initial commit. Add configuration for NixOS Proxmox image	2023-09-11 23:20:34 +02:00
.sops.yaml	Switch the public-web-static hosts secret mngmt from colmena to sops-nix	2024-05-26 03:49:43 +02:00
deployment_configuration.json	Add deployment_configuration to make deployment using infra-rebuild work	2024-06-08 19:57:40 +02:00
flake.lock	Introduce sops and sops-nix for secret management	2024-05-25 16:47:34 +02:00
flake.nix	Configure basic yate host	2024-06-08 20:18:59 +02:00
README.md	Add deployment_configuration to make deployment using infra-rebuild work	2024-06-08 19:57:40 +02:00

README.md

nix-infra

nix infrastructure configuration for CCCHH.

For deployment we're using infra-rebuild.
To easily get a shell with infra-rebuild going, use the following command:

nix shell git+https://git.hamburg.ccc.de/CCCHH/infra-rebuild#infra-rebuild

After that you can simply run the following to deploy e.g. the git and matrix hosts:

infra-rebuild switch git matrix

By default infra-rebuild tries to use the FQDN from the nixosConfiguration of the host for deployment. However to override individual parts of the deployment target, a deployment_configuration.json can be used. This is exactly what we're doing to set the default deployment user to colmena-deploy and have custom target hostnames for Chaosknoten hosts, since they don't have an FQDN defined in their nixosConfiguration.