NixOS Explained: Declarative Linux Configuration for Reproducible Servers

Most Linux distributions accumulate configuration through years of manual commands, edited files, and installed packages — a history nobody fully remembers. NixOS declarative configuration takes a radically different approach, defining your entire system in a single set of files that can rebuild an identical machine from scratch, every time, with no drift or guesswork.

What Makes NixOS Different?

NixOS is a Linux distribution built around the Nix package manager, where the entire system configuration — installed packages, running services, user accounts, network settings — is described in configuration files rather than assembled through a sequence of manual commands. Rebuilding the system from that configuration always produces the same result, whether it’s the first time or the hundredth.

The Core Idea: Configuration as a Single Source of Truth

Instead of running apt install nginx and then manually editing config files scattered across /etc, NixOS asks you to describe your desired system state in a file, typically /etc/nixos/configuration.nix. Rebuilding the system reads this file and makes reality match the description — install what’s declared, remove what’s no longer declared, and configure services exactly as specified.

nix

services.nginx = {
  enable = true;
  virtualHosts."example.com" = {
    root = "/var/www/example";
  };
};

Why This Matters for Servers

• Reproducibility – rebuild the exact same server configuration on new hardware or after a failure, without hunting through your memory or scattered notes for what you originally set up
• Atomic rollbacks – every system rebuild creates a new “generation,” and you can boot into any previous generation instantly if a change causes problems
• No configuration drift – since packages and services come entirely from the configuration file, there’s no risk of undocumented manual changes silently accumulating over time
• Version-controlled infrastructure – your entire server configuration can live in a Git repository, tracked and reviewed like application code

Installing Packages the Nix Way

Rather than a traditional package manager modifying a shared system state, Nix installs each package into its own isolated location in the Nix store, referenced by a unique hash based on its exact dependencies. This means multiple versions of the same package can coexist without conflict, and removing a package cleanly removes exactly what was added with no leftover files.

Rebuilding Your System

After editing your configuration file, apply the changes:

sudo nixos-rebuild switch

This builds the new configuration, activates it immediately, and creates a new bootable generation — all while the previous generation remains available as a rollback option in your bootloader menu.

Rolling Back a Bad Change

If a rebuild introduces a problem, simply reboot and select the previous generation from the boot menu, or roll back without rebooting:

sudo nixos-rebuild switch --rollback

The Learning Curve

NixOS’s biggest barrier is the Nix language itself — a functional programming language used to write configuration files, which feels unfamiliar to admins used to imperative shell scripts or standard YAML configuration. Expect a genuine learning investment before NixOS configuration feels natural, though many users find the payoff in reproducibility and rollback safety well worth the initial friction.

Is NixOS Right for Your Home Server?

NixOS suits homelab users who value reproducibility highly — those who want to rebuild a server identically after hardware failure, or who enjoy managing infrastructure as version-controlled code. For users who prefer simpler, more traditional package management and don’t mind a bit of configuration drift over time, a more conventional distribution remains the lower-friction choice.

Final Thoughts

NixOS declarative configuration represents one of the most fundamentally different approaches to system administration in the Linux world, trading a steeper initial learning curve for genuinely reproducible, version-controlled infrastructure. For homelab users willing to invest the time learning the Nix language, it offers a level of configuration confidence that traditional distributions simply can’t match.