Misterio77/nix-starter-configs
Gabriel Fontes
Minimal and standard flake templates with heavy comments, designed to be the thing you copy on day one.
Worth borrowing: The whole thing. Start your own config from the minimal template.
Propping up the bar
The Regulars
NixOS configs from real people, each with a short note on what it does well and what’s worth borrowing. Reading other people’s configs is one of the quickest ways to learn.
First pint
tomwrw/megadots
The landlord
An AMD gaming desktop and a Surface Pro tablet from one den config, with every feature written as a reusable aspect.
Worth borrowing: The steam aspect: one file that brings in Steam, two extra Proton builds, a binary cache and a persisted game library.
Misterio77/nix-config
Gabriel Fontes
A widely copied personal config, with a clean separation of hosts, users and shared modules.
Worth borrowing: How it splits system settings from per-user Home Manager settings.
ryan4yin/nix-config
Ryan Yin
From the author of the NixOS & Flakes Book: desktops, servers and macOS, all in one place.
Worth borrowing: Read it next to the book: the chapters map onto real code here.
mitchellh/nixos-config
Mitchell Hashimoto
Runs NixOS in a VM on a Mac as a daily development machine. A neat look at Nix outside a normal PC.
Worth borrowing: The idea that your dev environment can live in a VM you rebuild at will.
fufexan/dotfiles
fufexan
A polished Hyprland desktop, kept entirely in config.
Worth borrowing: Theming and bar setup for a riced Hyprland desktop.
mightyiam/infra
mightyiam
The personal infrastructure of the person who first wrote up the dendritic pattern, and the reference for what one looks like in practice.
Worth borrowing: The shape of it: a near-empty flake.nix, and every feature in a file of its own.
How to read someone's config
- Start at
flake.nix. It lists every machine (“host”) the repo builds. - Pick one host and follow its imports. That’s the whole recipe for that machine.
- Borrow one module at a time. Copy, rebuild, check it works, then take the next.
Pour your own
Got a config you’re proud of? Add it with a pull request: copy any file in content/regulars/, fill in the front matter, and write a few lines on what it does well. I read every submission and can help with the notes.
A good regular is public, has a README, and has at least one thing a beginner could copy on its own.