539a798009
I revisited NixOS this week and I've rewritten my NixOS config from scratch. I must say I really like Nix flakes. For whatever reason it just clicked and I understood more programming with Nix despite my previous experience which is not good. Could be just the fact I had a break for a long time from completely using Nix (I still used it on non-NixOS distros). Eh... I still took some things from the original inspiration of this configuration so there's that. |
||
---|---|---|
hosts/ni | ||
lib | ||
modules | ||
.editorconfig | ||
.gitignore | ||
flake.lock | ||
flake.nix | ||
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 only export my NixOS configurations of my different hosts (of only one so far excluding VMs and VPSs ;p).
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.