Own (ever changing) nixos configurations

CI: QA:

This repository servers my own needs and should not be used verbatim. You can look and get inspired about how I use NixOS. This was made public for the sole purpose of sharing configurations and inspire others.

• The configuration now uses flakes and each folder under machines contains configuration for one server/machine.
• Secrets are encoded with the help of sopsnix.
• Certain not-so-sensitive information is hidden using git-crypt.
• I hide public IPs, domain names, and other information I deem sensitive.

The configuration uses flakes and is modular in order to reuse configuration across machines and have the code as DRY as possible. The "machines" folder contains host configurations with one folder per machine machine. Usually only configuration.nix and hardware.nix is present here. The "modules" folder contains reusable pieces of code, modules meant to be used across machines. The "secrets" folder contains secrets that can be used globally across individual machine configurations. The "profiles" folder contains a bare-bones profile where to start off when adding a new host to machines. The "home" folder contains home-manager configurations.

This repo holds configuration for NixOS machines I manage. The basic actions I need to do to deploy on a local machine follows:

cd path/to/repo/files/nix-config
sudo nixos-rebuild switch --flake .#$(hostname) --print-build-logs

Or the short version (using the actual path and an alias defined in the aliases.nix module):

cd ~/workspace/projects/nix-config
osup

Behind the scenes there are some workflows actions that help building the packages on a NixOS server I control. One action is responsible for building the packages for most of my machines. Another is updating the flake definitions each morning and triggers the build package action. Whenever I run osup on a machine that uses the builder.nix part of the building job is delegated to the remote server that has updated builds of my configuration, thus making the build faster. I also get emails when the automated build fails thus the failure does not propagate to all of the machines.

Key

• 🖥️ : Desktop
• 💻️ : Laptop
• 🎮️ : Games Machine
• 🐄 : Virtual Machine
• ☁️ : Server
• 🧟 : Not in service