Dotfiles

Nix & Flakes

The entire system and user environment are declaratively managed with Nix, a powerful package manager and build system that provides reproducibility, reliability, and flexibility.

Why Nix?

  • Declarative Configuration All configurations, from system services to user applications, are defined in code, enabling effortless system rebuilding and rapid rollback of changes.

  • Reproducibility & Portability The environment can be replicated identically on any Nix-enabled machine, ensuring consistent and streamlined setups.

  • Powerful Package Management Nix isolates dependencies, allowing multiple versions of the same application or library without conflicts, thereby eliminating "dependency hell."

Flake-Based Setup

This setup utilizes Nix flakes, a modern approach to managing Nix projects, offering:

  • Immutable, version-controlled configurations
  • Easy integration with GitHub and other sources
  • Simplified sharing and updating of modules

The flake.nix file unifies the system configuration, Home Manager modules, dotfiles synchronization, and custom scripts.

Home Manager Integration

Managing user-specific configurations (shell, editor, terminal, etc.) declaratively with Home Manager allows for consistent management of:

  • Shell configurations like Fish and Zsh
  • Neovim setup and plugins
  • Terminal and prompt settings
  • Handy scripts and aliases

What I Love About Nix

  • Atomic upgrades and rollbacks prevent issues after updates.
  • Effortless multi-machine synchronization with Git and flakes.
  • Precise control over software versions and dependencies.
  • Seamless integration with systemd, Wayland, and Wayland-native tools.

TL;DR

Nix serves as the foundational element of this environment, enabling a reproducible, flexible, and fully declarative setup that can adapt to evolving requirements.