nullbite/nixfiles
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
NullBite 2024-01-11 17:40:55 +01:00
parent 6b7cc6d71b
commit 5ef4b6abea
Signed by: nullbite
GPG Key ID: 6C4D545385D4925A
1 changed files with 12 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
View File

@ -1,6 +1,6 @@
# NullBite's NixOS Config
This is my personal NixOS config. Right now, it's just a basic flake which
imports a (mostly) normal stock NixOS configuration. The plan is to have three
imports a (mostly) normal stock NixOS configuration. <del>The plan is to have three
separate levels of organization:
- **Fragments**: Configure one specific service/app/setting/etc., which has the
@ -21,9 +21,19 @@ separate levels of organization:
however, generally will have some options exclusive to them, and these
should be placed in the host's `configuration.nix` or a host fragment.
At first I am going to migrate configuration into roles, and then as the configuration evolves, I will start to create fragments.
At first I am going to migrate configuration into roles, and then as the configuration evolves, I will start to create fragments.</del>
The above is outdated and I will rewrite it once I settle on a better way to organize this repo.
## `flake.nix` schema
`flake.nix` shall contain a "default" configuration for each host (using the
built-in selection of `nixos-rebuild`), as well as alternative config presets
for the host, if applicable.
## TODO
- Select entire desktop configuration via a single option and make bootable with specialisation
- figure out nixpkgs.lib.options.mkOption and add a string option that picks a desktop to use.
- add Plasma, Hyprland, and maybe GNOME if I'm feeling silly (I'd probably never actually use it)
- make more things configurable as options once I figure out the above, it's probably cleaner than importing modules
- Rewrite README