d676c59cda
- Remove package outputs for MacOS since I don't have any. - Import our custom packages as an overlay for our NixOS configs. - Recursively import our modules which is more correct. |
||
---|---|---|
hosts | ||
lib | ||
modules | ||
pkgs | ||
users | ||
.editorconfig | ||
.gitignore | ||
.gitmodules | ||
flake.lock | ||
flake.nix | ||
Makefile | ||
README.adoc |
This is my NixOS config as a Nix flake.
I finally have some time trying to grok flakes and redo my NixOS config from scratch after leaving NixOs (because I have work and have to quickly set things up without me trying to debug how NixOS works). Here is the result.
Installation
This primarily uses Nix flakes so you can have a preview of what’s available in my config.
nix flake show github:foo-dogsquared/nixos-config
It should export my NixOS configurations of my different hosts (of only one so far excluding VMs and VPSs ;p) among other things.
To install it, run the nixos-install --flake github:foo-dogsquared/nixos-config#ni
.
(Please see the respective appropriate host README for more information.)
Project structure
My NixOS config should look like the following:
nixos-config
├── hosts/
├── lib/
├── modules/
├── pkgs/
├── users/
├── flake.lock
├── flake.nix
└── README.adoc
-
./hosts/
contain machine-specific configuration. This usually configures like the hardware setup, timezone, and users. Host configurations are also exported in the flakes inoutputs.nixosConfigurations
. -
./modules/
contain my custom NixOS modules. For more information, see the related documentation. It is also exported from the flake inoutputs.nixosModules
. -
./pkgs/
contains my custom packages. It is exported in the flakes atoutputs.packages
compiled through various systems. -
./users/
contains my home-manager configurations and modules. It is exported in the flakes atoutputs.homeConfigurations
. For more information, see the related documentation.
TODO
In order of priority:
-
✓ Create custom modules.
-
✓ Create a themes system similar to this NixOS config.
-
✓ Manage secrets with agenix.
-
✓ Automate backups with NixOS config.
-
✓ Create custom packages and export it to flakes. (Maybe consider making it to upstream)
-
✓ Create cluser-wide configs.
-
✓ Create host-wide configs.
-
✓ Create user-specific configs with home-manager.
-
✓ Steal Get some ideas from this overengineered template.
-
✓ Make use of other established utilities such as digga, flake-utils-plus, and home-manager once I’m familiar to create my own Nix programs.
Out of scope:
-
Text editor configurations. They are often updated. I don’t want to rebuild it every time I change it.
-
Migration of my dotfiles. I still use it on other non-NixOS systems.
Frequently asked questions (FAQ)
-
Hello! I’m new to Nix and NixOS, where should I start?
Oh no, you’ve seen the multiple configurations from other systems, didn’t you? I hope you’re ready for some time understanding because the learning curve is steeper than the Troll Wall. I’ve written a blog post regarding my experience with Nix with a bunch of links for getting started. (Un)Fortunately, it is mostly the same experience now that I’ve revisited it.
-
Any requirements for this setup?
You only need Nix 2.4 installed with the experimental features for Nix command and flakes enabled (i.e.,
experimental-features = nix-command flakes
).
Inspirations
I stole got the ideas from the following projects: