Switch to local-path-provisioner.

This post is more of a record for me than something readers should discover so I am hiding it from the main homepage list.

.webhook_bridge/pipeline-build-homepage-staging.yaml

@@ -225,7 +225,7 @@ spec:
     - name: git-source
       volumeClaimTemplate:
         spec:
-          storageClassName: "nfs-client"
+          storageClassName: "local-path"
           accessModes:
             - ReadWriteOnce
           resources:

.webhook_bridge/pipeline-build-homepage.yaml

@@ -237,7 +237,7 @@ spec:
     - name: git-source
       volumeClaimTemplate:
         spec:
-          storageClassName: "nfs-client"
+          storageClassName: "local-path"
           accessModes:
             - ReadWriteOnce
           resources:

.webhook_bridge/pipeline-semver.yaml

@@ -177,7 +177,7 @@ spec:
     - name: git-source
       volumeClaimTemplate:
         spec:
-          storageClassName: "nfs-client"
+          storageClassName: "local-path"
           accessModes:
             - ReadWriteOnce
           resources:

pages/about_me/index.org

@@ -0,0 +1,14 @@
+#+OPTIONS: html-postamble:nil
+#+date: <2023-12-23 Sat>
+#+author: Tom Alexander
+#+email:
+#+language: en
+#+select_tags: export
+#+exclude_tags: noexport
+
+Links:
+- My personal repos: [[https://code.fizz.buzz/explore/repos][code.fizz.buzz]]
+- LinkedIn: https://www.linkedin.com/in/tom-alexander-b6a18216/
+- GitHub: https://github.com/tomalexander
+- Resume: https://fizz.buzz/tom_alexander_resume.pdf
+- PGP Key: https://fizz.buzz/pgp.asc

posts/2025/02/16/install-sm64ex-steam-deck/index.org

@@ -249,7 +249,7 @@ This will compile sm64ex and install it. But there's two problems we can immedia
 
 We will be solving these by creating a ~.desktop~ file, introducing nixGL, and writing a wrapper script that makes sm64ex launch from within steam gaming mode properly.
 * Adding nixGL
-If we were running NixOS, graphical programs would work out-of-the-box. Unfortunately on other Linux Distributions, we need to wrap our graphical programs so they know where to find the graphics drivers. To perform this wrapping, we will use [[https://github.com/nix-community/nixGL][nixGL]]. To install nixGL we need to add it as an input in our ~flake.nix~, apply its overlay, and add it as an ~extraSpecialArgs~ to have it automatically passed into each module:
+If we were running NixOS, graphical programs would work out-of-the-box. Unfortunately on other Linux distributions, we need to wrap our graphical programs so they know where to find the graphics drivers. To perform this wrapping, we will use [[https://github.com/nix-community/nixGL][nixGL]]. To install nixGL we need to add it as an input in our ~flake.nix~, apply its overlay, and add it as an ~extraSpecialArgs~ to have it automatically passed into each module:
 
 #+begin_src nix
   {

posts/2025/02/21/why-i-use-nixos/index.org

@@ -0,0 +1,19 @@
+#+OPTIONS: html-postamble:nil
+#+title: Why I use NixOS
+#+date: <2025-02-21 Fri>
+#+author: Tom Alexander
+#+email:
+#+language: en
+#+select_tags: export
+#+exclude_tags: noexport
+#+natter_publish: unlisted
+
+This is just a list of situations in which classic Linux distributions have failed me, whereas NixOS would not.
+
+* Package version conflicts
+
+** gsutil on Arch Linux [2025-02-21 Fri]
+[[./files/20250221_gsutil.png]]
+
+** NodeJS on Arch Linux [2025-02-21 Fri]
+[[./files/20250221_nodejs.png]]