extern/zaneyos
1
0
Fork 1
mirror of https://gitlab.com/Zaney/zaneyos.git synced 2025-08-07 13:08:45 +02:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update home

Tyler Kelley
2024-02-02 05:42:46 +00:00
parent 0d527034b6
commit ed213d1b03
1 changed files with 15 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
home.md

@ -2,4 +2,18 @@ This is the actual in depth documentation on what ZaneyOS is, how it works, how
![zaneyos-1400x600](uploads/c1d98476c5503897dca1e5054e8f3cb6/zaneyos-1400x600.jpg)
[What Is NixOS](What-Is-NixOS)
## Why Choose My Configuration?
I have gone through a lot of effort of making my configuration something that is simple to understand while remaining feature complete. My configuration is written as a NixOS Flake so you will need to be using NixOS. I will have a guide to replicating what I use down below.
### What Is A Flake?
For detailed information about flakes in general I will refer you to [here](https://nixos.wiki/wiki/Flakes). Now you can find this great excerpt from a reddit post that explains a lot.
"A flake.nix file is an attribute set with two attributes called inputs and outputs. The inputs attribute describes the other flakes that you would like to use; things like nixpkgs or home-manager. You have to give it the url where the code for that other flake is, and usually people use GitHub. The outputs attribute is a function, which is where we really start getting into the nix programming language. Nix will go and fetch all the inputs, load up their flake.nix files, and it will call your outputs function with all of their outputs as arguments. The outputs of a flake are just whatever its outputs function returns, which can be basically anything the flake wants it to be. Finally, nix records exactly which revision was fetched from GitHub in flake.lock so that the versions of all your inputs are pinned to the same thing until you manually update the lock file."
### What About The ZaneyOS Flake?
My Flake controls where we are getting things from. It also allows me to define variables for things like Git information, CPU, GPU options for enabling different drivers for different configurations. When you run the rebuild switch command with the flake argument and give it the ZaneyOS folder it sources the flake.nix that sources system.nix and home.nix.
The hardware.nix is automatically generated with all the things you need and the system.nix imports it and other nix files containing certain aspects of the config that may or may not change based on CPU or GPU settings.