NixOS is a declarative and reproducible Linux distribution, meaning ALL the software on your computer is defined in a series of configuration files you can take with you and install anywhere. Without being able to configure everything through Nix, I wouldn't have bothered setting all this up.
- It also does a lot more, but I could be a lot better at explaining things I don't fully comprehend yet.
Much of the NixOS documentation is lackluster or impossible to find, the Nix language is difficult to get a half-decent grasp of (my puny Java-dev mind is still getting used to it), and the primary advice to learn is reading through the code defining each package you want to use--which if you're starting off, you probably won't understand. Despite this, if you love tinkering and hate computers doing what you don't tell them to, I highly recommend looking into NixOS.
This repo serves as a record of how my config has evolved over time and everything I'm actively learning to set up. Since this also serves as production for most of my computers now, I'll try to keep the main branch not broken, but no guarantees there. I've tried to leave comments and citations here and there to document my learning process and hopefully help out anyone who for some unknown reason decides to dive into my config specifically. Have fun in there.
Wallpapers are from Given and Hoshiai no Sora.
See the wiki.
Note
If you're using one of the setups with a GUI, you need to manually set the wallpaper with swww img.
To make development easier, this flake provides a dev shell you can enter using direnv or by running nix develop.
You can then run jstestvm <system> to quickly compile and run a virtual machine of any system in the flake.
- bucatini, the gaming PC.
- farfalle, the laptop.
- lasagna, the bedroom TV.
- tortelli, the server.
flake.nixis the main file in the repository, where the dependencies (inputs) and components (modules) of each system get defined.systemsis where the main config files for each of my systems live. As of writing, each system has a main file for its software, which imports a secondary, auto-generated file for its hardware.modulesis where the general configuration modules can be found. This defines the options enabled by default for all systems along with other options systems can pick and choose based on their needs.desktopholds anything you'd expect a GUI/desktop environment to have. Here, you can find the setup for Hyprland (the main thing you see), all fonts installed on the system, and the keyboard (specifically, the Japanese one).hardwarehas hardware-specific defaults, such as for my PC's AMD GPU and my laptop's fingerprint reader.programscontains most general-purpose applications you may want on a system. These are organized by use case.serverdefines various web services for my homelab.utilsis effectively miscellaneous services you may want on the system, such as automatic updates and backups.
usersdefines the accounts to create at the system level.hmmodulesare where per-user configuration modules are found, managed by Home Manager. Anything that can't be defined for the whole system lives here.hmusersare where the personal preferences for each account are set. These depend onhmmodules.scriptshosts shell scripts the system depends on. These are exported byflake.nixas packages.secretscontains declarative data which some systems depend on but needs to stay private. These are protected by sops-nix.
These inspired the direction I wanted to take my setup in when I was first getting started. This is by no means a comprehensive list, as most references are cited near the code I used from them. These may not also reflect how the repository turned out, as again, I used these a year ago.
