<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>nix on jawr</title><link>https://jawr.github.io/jl-lu/tags/nix/</link><description>Recent content in nix on jawr</description><generator>Hugo -- gohugo.io</generator><language>en-gb</language><copyright>© {year}</copyright><lastBuildDate>Tue, 16 Feb 2021 17:29:58 +0900</lastBuildDate><atom:link href="https://jawr.github.io/jl-lu/tags/nix/index.xml" rel="self" type="application/rss+xml"/><item><title>nixos - wireguard &amp; modules</title><link>https://jawr.github.io/jl-lu/blog/nixos-wireguard-and-modules/</link><pubDate>Tue, 16 Feb 2021 17:29:58 +0900</pubDate><guid>https://jawr.github.io/jl-lu/blog/nixos-wireguard-and-modules/</guid><description>Refactoring In my previous post I attacked the kubernetes configuration using only one module, the rest created relied on functions.
It didn&amp;rsquo;t feel idiomatic and when trying to add wireguard, the cracks started to appear. It felt like I was fighting with the language.
After some wonderful duck debugging with the excellent community on IRC, I decided to refactor what I had in to modules.
Modules The NixOS wiki has an excellent article on modules, but the gist is that a module is a set that has the following syntax:</description></item></channel></rss>