diff --git a/blog/nix-flakes-1-2022-02-21.markdown b/blog/nix-flakes-1-2022-02-21.markdown
index 7b20dc1..e28ec80 100644
--- a/blog/nix-flakes-1-2022-02-21.markdown
+++ b/blog/nix-flakes-1-2022-02-21.markdown
@@ -75,6 +75,9 @@ nix = {
Then rebuild your system and you can continue along with the article.
+EDIT: You can use WSL for this. See
+[here](/blog/nix-flakes-4-wsl-2022-05-01) for more information.
+
If you are not on NixOS, you will need to either edit `~/.config/nix/nix.conf`
or `/etc/nix/nix.conf` and add the following line to it:
diff --git a/blog/nix-flakes-4-wsl-2022-04-23.markdown b/blog/nix-flakes-4-wsl-2022-05-01.markdown
similarity index 85%
rename from blog/nix-flakes-4-wsl-2022-04-23.markdown
rename to blog/nix-flakes-4-wsl-2022-05-01.markdown
index 18fa23d..801e75b 100644
--- a/blog/nix-flakes-4-wsl-2022-04-23.markdown
+++ b/blog/nix-flakes-4-wsl-2022-05-01.markdown
@@ -18,7 +18,10 @@ enough to run NixOS on Windows.
This will give you an environment to run
Nix and Nix Flakes commands with. You can use this to follow along with this
-series without having to install NixOS on a VM or cloud server.
+series without having to install NixOS on a VM or cloud server. This is going to
+retread a bunch of ground from the first article. If you have been following
+along through this entire series, once you get to the point where you convert
+the install to flakes there isn't much more new material here.
## Installation
@@ -182,6 +185,12 @@ And paste in this HTML:
It's so cool *twerks*
```
+This doesn't have to just be artisanal
+handcrafted HTML in bespoke folders either. You can set the root
of
+a nginx virtual host to point to a Nix package as well. This will allow you to
+automatically generate your website somehow and deploy it with the rest of the
+system. Including being able to roll back changes.
+
And then you can see it show up with `curl`:
```console
@@ -237,6 +246,20 @@ And finally activate the new configuration with flakes:
sudo nixos-rebuild switch
```
+Why don't you have the --flake
+flag here? Based on what I read in the documentation, I thought you had to have
+it there.
+
+nixos-rebuild
will
+auomatically detect flakes in /etc/nixos
. The only major thing it
+cares about is the hostname matching. If you want to customize the hostname of
+the WSL VM, change the nixos
in
+nixosConfigurations.nixos
above and set
+networking.hostName
to the value you want to use. To use flakes
+explicitly, pass --flake /etc/nixos#hostname
to your
+nixos-rebuild
call.
+
+
After it thinks for a bit, you should notice that nothing happened. This is
good, we have just converted the system over to using Nix flakes instead of the
classic `nix-channel` rebuild method.