Skip to content
vic

dtomvan/puntbestanden.json
{
"createdAt": "2024-10-30T14:03:53Z",
"defaultBranch": "main",
"description": null,
"fullName": "dtomvan/puntbestanden",
"homepage": "",
"language": "Nix",
"name": "puntbestanden",
"pushedAt": "2025-11-23T16:14:07Z",
"stargazersCount": 10,
"topics": [
"dotfiles",
"nixos",
"nixos-config"
],
"updatedAt": "2025-11-23T16:14:11Z",
"url": "https://github.com/dtomvan/puntbestanden"
}

Literally means “dotfiles” in Dutch: “punt” = “dot”, “bestanden” = “files”

What’s in here:

  • 9 NixOS configs (well, this is a generated number to it’s technically correct but don’t over-estimate me)
  • a dendritic home-manager config (TODO: list aspects here)

A single command:

$ nix develop -c sudo disko-install -m format --flake .#<HOSTNAME> --disk main /dev/nvme0n1
  • An unhinged Emacs config
  • A lot less lines of neovim lua config compared to my previous attempt
  • A clone of 9001’s hub ISO, except not alpine-based :sweat_smile:

This repository uses the dendritic pattern for monolithic, interconnected NixOS/HomeManager/Nixvim configs. Hence it also uses flake.parts. This might throw you off if you are new to nix and/or nix flakes. You’ve been warned!

It is meant to make configurations more modular, flexible, and shareable though, so I encourage you to learn from it if you do so desire. If you understand flake.parts, all you need to know is that (almost) every nix file in this tree is a flake.parts module.

Learn more about it (in order of, well, “deepness” or complexity):

  • boomer, a reasonably sluggish Ryzen 5 2600 desktop PC
  • kaput, a thick bastard of a laptop with a broken screen
  • feather, the ultra-light Thinkpad X1 Carbon G8

This repository includes an “autounattend” installer ISO, which:

  • Installs a nested, pre-defined NixOS configuration
  • Without any user interaction required apart from booting it
  • Also automatically partitions through disko
  • Does not require internet

To create the iso, run nix build .#autounattend-iso.

To run an install demo in QEMU, run nix run .#install-demo.

If you do not have access to the secrets in this repo you’ll need to comment out the networking-wifi-passwords import in order to build it.

Beware: the eval time (and disk usage) is very inefficient, because it seems like nix wants to copy around some source directory through the store a couple of times. it is a cool party trick though.

NEW: you can do this in YOUR repo too, with your own target config!

{
inputs.flake-parts.url = "github:hercules-ci/flake-parts";
inputs.import-tree.url = "github:vic/import-tree";
inputs.nixpkgs.url = "github:nixos/nixpkgs/nixos-unstable";
inputs.dtomvan = {
url = "github:dtomvan/puntbestanden";
flake = false;
};
inputs.disko = {
url = "github:nix-community/disko/latest";
inputs.nixpkgs.follows = "nixpkgs";
};
outputs = inputs @ {
flake-parts,
import-tree,
nixpkgs,
dtomvan,
...
}:
flake-parts.lib.mkFlake { inherit inputs; } {
imports = [
flake-parts.flakeModules.modules
(import-tree "${dtomvan}/modules/community/autounattend")
];
autounattend = {
# needed so the installer partitions the same way you mount your
# filesystems later
diskoFile = ./disko.nix;
# this path will be copied to /etc/nixos after installation.
configRoot = ./.;
};
flake.nixosConfigurations.autounattend = nixpkgs.lib.nixosSystem {
modules = [
./configuration.nix
./disko.nix
disko.nixosModules.disko
];
};
};
}

For myself: How to bootstrap localsend-rs inside of the flake

Section titled “For myself: How to bootstrap localsend-rs inside of the flake”
  • Have one of the private keys corresponding to a pubkey listed in .sops.yaml in ~/.config/sops/age/keys.txt.
  • nix run nixpkgs#sops -- decrypt secrets/localsend-rs.secret
  • Copy the access token
  • nix flake lock --extra-access-tokens "$accesstoken"
  • nh os switch

Afterwards, through the nixos module, the secret will get loaded into nix.conf and you can nix flake update for example without any manual setup