c6ristian/nix-infra
0
0
Fork 0
forked from CCCHH/nix-infra
Code Pull requests Activity
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.
121 commits 1 branch 0 tags 518 KiB
Nix 97.7%
Python 2.3%
Find a file
echtnurich f6b424fa7a
add yate service for autostart 
introduce /etc/yate, clone/reset on service start

Fix config via git

make yate systemd service

create yate service user

recreate the full config everytime

decolour the log because of blob data

make sure source is available before deleting config

change yate-config repo

fix yate deploy key

fix yate-config not pulling
2024-11-17 21:41:16 +01:00
config add yate service for autostart 2024-11-17 21:41:16 +01: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 add yate service for autostart 2024-11-17 21:41:16 +01: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 add yate service for autostart 2024-11-17 21:41:16 +01: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.