Nix noob trying to build his system
Find a file
2024-02-23 21:17:05 -06:00
patches Updated system 2024-02-18 09:23:57 -06:00
profiles Fixes system rebuilding 2024-01-26 14:45:23 -06:00
system Updated system and (hopefully) fix btrfs slowness 2024-02-03 11:01:38 -06:00
themes Added background test script and updated uwunicorn-yt bg 2024-02-23 21:17:05 -06:00
user Less transparency on windows 2024-02-22 20:01:33 -06:00
desktop.png Added primary rice screenshot for main readme 2023-11-04 14:17:17 -05:00
flake.lock Updated system 2024-02-23 20:19:41 -06:00
flake.nix Updated system 2024-02-18 09:23:57 -06:00
install.org Extra detail on adding unstable channel in install notes 2023-10-28 20:44:08 -05:00
LICENSE Add LICENSE 2023-04-22 20:48:09 +00:00
README.org I guess no scope read-only api access on one public repo is insecure... 2024-01-27 08:54:12 -06:00

NixOS Config

Main Repo Link (GitLab)

Mirror Repo Link (GitHub)

Mirror Repo Link (Codeberg)

What is this repository?

These are my dotfiles (configuration files) for my NixOS setup(s).

Here is my main setup: /byteio/nixos-config/media/commit/2bca53cbd2402f867dd62795e0448a3694c41379/desktop.png

My 55+ Themes

Stylix (and base16.nix, of course) is amazing, allowing you to theme your entire system with base16-themes.

Using this I have 55+ themes (I add more sometimes) I can switch between on-the-fly. Visit the themes directory for more info and screenshots!

Install

I wrote some reinstall notes for myself here (install.org).

Modules

Separate Nix files can be imported as modules using an import block:

imports = [ ./import1.nix
            ./import2.nix
            ...
          ];

This conveniently allows configurations to be (*cough cough) modular (ba dum, tssss).

I have my modules separated into two groups:

More detailed information on these specific modules are in the system directory and user directory respectively.

Patches

In some cases, since I use nixpgs-unstable, I must patch nixpkgs. This can be done inside of a flake via:

    nixpkgs-patched = (import nixpkgs { inherit system; }).applyPatches {
      name = "nixpkgs-patched";
      src = nixpkgs;
      patches = [ ./example-patch.nix ];
    };

    # configure pkgs
    pkgs = import nixpkgs-patched { inherit system; };

    # configure lib
    lib = nixpkgs.lib;

Patches can either be local or remote, so you can even import unmerged pull requests by using fetchpatch and the raw patch url, i.e: https://github.com/NixOS/nixpkgs/pull/example.patch.

I currently curate patches local to this repo in the patches directory.

Profiles

I separate my configurations into profiles (essentially system templates), i.e:

  • Personal - What I would run on a personal laptop/desktop
  • Work - What I would run on a work laptop/desktop (if they let me bring my own OS :P)
  • Homelab - What I would run on a server or homelab
  • WSL - What I would run underneath Windows Subystem for Linux

My profile can be conveniently selected in my flake.nix by setting the profile variable.

More detailed information on these profiles is in the profiles directory.

Star History

Didn't think this would get that many stars on GitHub, yet here we are: https://api.star-history.com/svg?repos=librephoenix/nixos-config&type=Date.png