Hey, you. You're finally awake. You were trying to configure your OS declaratively, right? Walked right into that NixOS ambush, same as us, and those dotfiles over there.

(screenshots coming soon)

1. Acquire or build a NixOS 24.05+ image:

   # Yoink nixos-unstable from upstream
   $ wget -O nixos.iso https://channels.nixos.org/nixos-unstable/latest-nixos-minimal-x86_64-linux.iso

2. Write it to a USB drive:

   # Replace /dev/sdX with the correct partition!
   $ cp nixos.iso /dev/sdX

3. Restart and boot into the installer.

4. Do your partitions and mount your root to /mnt (for example).

5. Clone these dotfiles somewhere:

   $ git clone --recursive https://github.com/hlissner/dotfiles

6. Create a host config in hosts/ (see existing ones for examples).

7. Run the installer:

   # The options are optional, but these are their default values, if you omit them.
   $ dotfiles/install.zsh \ 
         --root /mnt \
         --flake /mnt/etc/dotfiles \
         --user "$USER" \
         --host "$HOST" \
         --dest /mnt/home/$USER/.config/dotfiles

8. Then reboot and you're good to go!

And I say, bin/hey, what's going on?.

SYNOPSIS:
  hey [-?|-??|-???|-!] [-h|--help] COMMAND [ARGS...]

OPTIONS:
  -!           -- Do a dry run. WARNING: It's up to called scripts to obey!
  -?,-??,-???  -- Enable debug (verbose) mode.
  -h,--help    -- Display the documentation embedded in a target script's
                  header.

COMMANDS:
  - build|b    -- Build nix images or recompile bin/hey
  - exec       -- Dispatch to $DOTFILES_HOME/{,hosts/$HOST,config/$WM}/bin/shim.d $PATH
  - get|set    -- Alias for hey vars {get,set} ...
  - gc         -- Run garbage collection on the user's/system's profile
  - help|h     -- Display documentation for the command
  - hook       -- Trigger scripts associated with an event
  - host       -- Dispatch to $DOTFILES_HOME/hosts/$HOST/bin
  - info       -- Display information about current system (JSON)
  - path       -- Display path to area of my dotfiles
  - profile    -- Manage or analyze a system or user nix profile
  - pull       -- Update flake inputs
  - reload     -- Run reload hooks
  - repl       -- Open a Janet, Nix, or nix-develop REPL
  - swap       -- Swap nix-store symlinks with copies (and back)
  - sync|s     -- Rebuild this flake (using nixos-rebuild)
  - test       -- Run Hey and/or Nix test suites
  - which      -- Print out the script's path (with arguments) w/o executing it
  - wm         -- Dispatch to $DOTFILES_HOME/config/$WM/bin
  - vars       -- Get or set session or persistent state in userspace.
  - @*         -- Dispatch to $DOTFILES_HOME/config/${1#@}/bin
  - .*         -- Tries to be smart. Looks for any executable under host, wm,
                  then $DOTFILES_HOME/bin.

• Why NixOS?

  Because managing a fleet of servers, a hundred strong, is the tenth circle of hell without a declarative, generational, and immutable single-source-of-truth configuration framework like NixOS.

  Sure beats the nightmare of brittle capistrano/chef/puppet/ansible/shell scripts I left behind.

• Should I use NixOS?

  Short answer: no.

  Long answer: no really. Don't.

  Long long answer: I'm not kidding. Don't.

  Unsigned long long answer: Alright alright. Here's why not:

  • Its learning curve is steep.
  • You will trial and error your way to enlightenment, if you survive the frustration long enough.
  • NixOS is unlike other Linux distros. Your issues will be unique and difficult to google. A decent grasp of Linux and your chosen services is a must, if only to distinguish Nix(OS) issues from Linux (or upstream) issues -- as well as to debug them or report them to the correct authority (and coherently).
  • If words like "declarative", "generational", and "immutable" don't put your sexuality in jeopardy, you're considering NixOS for the wrong reasons.
  • The overhead of managing a NixOS config will rarely pay for itself with 3 systems or fewer (perhaps another distro with nix on top would suit you better?).
  • Official documentation for Nix(OS) is vast, but shallow. Unofficial resources and example configs are sparse and tend toward too simple or too complex (and most are outdated). Case in point: this repo.
  • The Nix language is obtuse and its toolchain is not intuitive. Your experience will be infinitely worse if functional languages are alien to you, however, learning Nix is a must to do even a fraction of what makes NixOS worth the trouble.
  • If you need somebody else to tell you whether or not you need NixOS, you don't need NixOS.

  If you're not discouraged by this, then you didn't need my advice in the first place. Stop procrastinating and try NixOS!

• How do you manage secrets?

  With agenix.

• Why did you write bin/hey?

  I envy Guix's CLI and want similar for NixOS, whose toolchain is spread across many commands, none of which are as intuitive: nix, nix-collect-garbage, nixos-rebuild, nix-env, nix-shell, etc.

  I don't claim hey is the answer, but who doesn't like their own brew?

• How 2 flakes?

  Would it be the NixOS experience if I gave you all the answers in one, convenient place?

  No. Suffer my pain:

  • A three-part tweag article that everyone's read.
  • An overengineered config to scare off beginners.
  • A minimalistic config for scared beginners.
  • A nixos wiki page that spells out the format of flake.nix.
  • Official documentation that nobody reads.
  • Some great videos on general nixOS tooling and hackery.
  • A couple flake configs that I may have shamelessly rummaged through.
  • Some notes about using Nix
  • What helped me figure out generators (for npm, yarn, python and haskell)
  • Learn from someone else's descent into madness; this journals his experience digging into the NixOS ecosystem
  • What y'all will need when Nix drives you to drink.

  And if all else fails, ask for help on the NixOS Discourse.