Go to file
Riley Apeldoorn ca5ee9ed20 Fix swaylock on work machine 2023-12-22 12:26:06 +01:00
script Add yeet script 2023-08-23 10:03:13 +02:00
secret Add deemix + config 2023-09-02 23:26:09 +02:00
shared Fix swaylock on work machine 2023-12-22 12:26:06 +01:00
system Enable steam and bluetooth on lime 2023-11-10 18:45:01 +01:00
themes Add color theme 2023-05-21 22:09:59 +00:00
README.md Decommission `odin` 2023-06-06 16:19:47 +02:00
flake.lock Update nixpkgs 2023-09-21 17:38:37 +02:00
flake.nix Fix swaylock on work machine 2023-12-22 12:26:06 +01:00
secrets.nix Add deemix + config 2023-09-02 23:26:09 +02:00
switch.sh Allow unfree packages in switch script 2023-05-25 19:44:28 +02:00

README.md

Infrastructure

Hello this is my new and improved Nix infrastructure.

General layout

There are three main directories:

  • secret, which contains secrets
  • shared, which contains shared config modules
  • system, which contains the configurations for specific machines

I have some machines that don't run NixOS so I have separated the home-manager stuff (home) from the NixOS system-level stuff (core).

For example, strawberry is a NixOS machine, so for this machine, there is both a home.nix for the home config of my user account, and a core.nix containing the system-level configuration of the machine.

Shared configuration

NixOS and home-manager modules are used to organize the config.

A lot of config is shared between machines. This is stored within the shared/ directory, under either shared/core/ for system-level NixOS modules or shared/home/ for home-manager modules.

There's also a shared key used by the nix user of each machine, for which the public key is in shared/data/. This key is used to let other machines serve as remote builders.