tygo-van-den-hurk / nixos

This repository contains the the configuration files for my NixOS instance. NixOS is a linux distrobution that allows reproducibility. The point of the repository is such that I can store my configuration safely in the cloud, have version control, and sync any updates to all machines using this configuration as it supports mulitple machines.

This repository contains the the configuration files for the NixOS.

NixOS

What is NixOS?

NixOS is a Declarative linux distribution that allows reproducibility, and focuses of reliability.

1. Reproducible

Nix builds packages in isolation from each other. This ensures that they are reproducible and don’t have undeclared dependencies, so if a package works on one machine, it will also work on another. Declarative

2. Declarative

Nix makes it trivial to share development and build environments for your projects, regardless of what programming languages and tools you’re using. Reliable

3. Reliable

Nix ensures that installing or upgrading one package cannot break other packages. It allows you to roll back to previous versions, and ensures that no package is in an inconsistent state during an upgrade.

Structure of this Repository

This repository has 3 main directories:

• Systems: the systems that I've configured. Load modules from modules/ . You can learn more about that module here.
• Modules: is used to store a set of modules a system can load. You can learn more about that module here.
• Users: this is were the home-manager data will be stored. You can read more about that module here.

Here is an overview of the structure:

NixOS/
├── systems/
├── modules/
├── user/
├── flake.nix
└── flake.lock

There is also the flake.nix, and flake.lock of course here at the root. The flow is as follows:

• The flake takes the argument from the CLI and loads the system from ./systems/ somewhere.
• That system loads the module loader at /modules/default.nix, which you can read more about here.
• The module loader loads the modules specified in the machines settings.

You can learn more about the structure of the systems directory, modules directory, or user directory by clicking these links.

Todo List

This is a todo-list of things we still need to do to get this system as I'd like. After all these are done, it will become a feature list! Go to To Do list

Learn NixOS

These resources helped me with building my own configuration file:

Name	Link
NixOS Setup Guide - Configuration / Home-Manager / Flakes	YouTube
How to Start Adding Modularity to Your NixOS Config	YouTube

nixos's Issues

Settings are not merged deeply

Let's say you have:

# /systems/common-settings.nix
arguments @ { config, pkgs, lib, ... } : {
    user = {
        # some settings
    };  

    modules = { 
        kmonad              = true;         
        gaming              = false;
        # more settings below
    };  

    system = {          
        # some settings
    };
}

and

# `/systems/category/common-settings.nix`, or `/systems/category/machine/settings.nix`
arguments @ { config, pkgs, lib, ... } : let

    common-settings ( import ../common-settings.nix arguments );

in ( common-settings // { # add updates below:
    modules = {
        gaming = true;
    };  
})

then instead of:

 {
    user = {
        # some settings
    };  

    modules = { 
        kmonad              = true;         
        gaming              = true;
        # more settings below
    };  

    system = {          
        # some settings
    };
}

You'll get:

 {
    user = {
        # some settings
    };  

    modules = {         
        gaming = false;
    };  

    system = {          
        # some settings
    };
}

Note here that the other module settings are completely gone. Modules is completely overwritten and now, only has one module gaming.

What is happening here is that module gets assigned the new set, but it does not get it's attributes overwritten as it is supposed to.

Chosing GNOME as your GUI in the settings instead of KDE, or i3wm will result in no GUI

When you switch the setting: modules.gui to anything other then "kde", "KDE", "i3", or "i3wm", for example "GNOME" then this will result in no GUI being shown at all. After running the switch command:

sudo nixos-rebuild switch --flake .# --impure

You'll find yourself here:

Instead of here:

The same issue I found for switching to GNOME.

Chosing Hyprland as your GUI in the settings instead of KDE, or i3wm will result in no GUI

When you switch the setting: modules.gui to anything other then "kde", "KDE", "i3", or "i3wm", for example "Hyprland" then this will result in no GUI being shown at all. After running the switch command:

sudo nixos-rebuild switch --flake .# --impure

You'll find yourself here:

Instead of here:

The same issue I found for switching to GNOME.

xremap does not have application specific remaps on i3wm

Issue

xremap does not know what application is in focus. As you can see from the logs:

may 08 11:33:33 tygos-thinkpad xremap[59750]: warning: Failed to connect to X11: X11 setup failed: 'Authorization required, but no authorization protocol specified

Quick fix

run

xhost +SI:localuser:root

as listed here.

[ FEATURE REQUEST ] : home-manager support

Home-Manager is a module that allows you to create dotfiles with the Nix language.