Okay, the long awaited, most anticipated, overly masturbated part two is ready for public consumption:

https://blog.xvrqt.com/nix-wireguard-key-gen.html

We're finally,
almost, ready to configure Wireguard ​

Also, I won't have to write any more shell scripts in Nix which I do not enjoy at all.

If you give it a read please let me know! I find it encouraging, and the feedback helps me grow as a writer.

#nix #wireguard #linux #kernel #flakes #nixox #age #agenix
nix wireguard key gen

In the first post we talked about how at a minimum a Wireguard interface needs the Wireguard privat...

xvrqt
Any tips and tricks for using #git for #nix #nixos #flakes : when the "mother flake" flake lives on a public repo & is set up to provide multiple #configurations for different machines built using:
nixos-rebuild switch --flake .#<machine_name>
I dug myself into a hole by copying the files from the mother flake repo to set up a new machine and the flake on my new machine has diverged & cannot be merged back into the mother flake repo because I did not *clone* it down so has no common git history
1/6
I’ve been thinking through disaster recovery with #NixOS #flakes, impermanence, and #ZFS.
A flake defines a system declaratively, but assumes storage (e.g. ZFS pools) and persisted data (e.g. /persist) already exist. Flakes don’t create storage—they only configure it. Right?
https://blog.xvrqt.com/nix-wireguard.html

Writing a new series on using Nix to configure Wireguard. It's probably overly ambitious as I have had the completed flake done for personal use for weeks now, but writing the blog means redoing it step by step in excruciating detail.

I had to keep cutting scope for each post and now, after typing all day, I finally have... the basic option setup for it. How is writing so hard? Why would a loving god cause such agony?

Feedback welcome, as I think part of my problem is I don't understand who my audience is so I never know what I can leave out and what I should explain further.

#nix #nixos #linux #wireguard #kernel #flakes #foss
nix wireguard

Wireguard1 is a Linux Kernel Module which allows you to easily configure encrypted network interfac...

xvrqt

Wer nannte es eigentlich zmk-nix und nicht corne-flakes?

#zmk #nix #corne #nix_flakes #flakes

nach einer Woche mit meinem #nix monorepo, #flakes und #homemanager bin ich echt zufrieden. ich glaube, ich habe nix jetzt verstanden :D Laptop, Workstation auf der Arbeit, heim-Server und Computer zu Hause sind #nixifiziert :D und es fühlt sich wirklich gut an. jeden Tag passieren immer noch WOW-Momente... Aufgabe für den heiligen #Sonntag: hyprland für das Notebook fertig machen :D wäre doch gelacht, wenn ich das nicht heute hinkriege :D #nixos #Lernkurve #SonntageSindZumLernenDa #Linux
Is #nonguix the Nix #flakes of the Guix community?
How to Install NixOS From Scratch | Flakes + Home Manager Full Guide

So, as someone very new to Nix, could someone check whether my understanding makes some sense:

  • flakes let you reproducibly compose nix
  • this also means that results can be cached, with all inputs of a flake being copied to the store so they can be cheaply reused
  • this includes the folder the flake is in, but there may often be build outputs or similar files that are unnecessary & expensive to copy
  • therefore these can be excluded from the copy; this isn't done by a configuration specific to the flake but by checking the git staging area
  • this is both confusing, and privileges git over other vcs; in particular, using jujutsu with a collocated git repo is very unpleasant
  • but given that the folder contents aren't locked in flake.lock and already are present on the filesystem anyways… what even is the point of copying it too to the store in the first place?

#nix #flakes

I’ve used #nixos since 2017-2018, and I still don’t really understand #flakes. I have 5-10 nixos hosts/vms/lxc using nix-channel. What am I missing out on?

Roast me please