add a deployment step

.gitea/workflows/deploy.yaml

@@ -2,6 +2,8 @@ name: Deploy Quartz site to Pages
 
 env:
   VERSION_FRAGMENT: minor
+  DEPLOYMENT_NAMESPACE: luxuries
+  DEPLOYMENT_LABEL: garden
 
 on:
   push:
@@ -79,4 +81,15 @@ jobs:
             www.tar.gz
           token: ${{secrets.CI_ACCESS}}
       - run: git push
-        working-directory: content
+        working-directory: content
+  deploy:
+    needs: [ build ]
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions-hub/kubectl@master
+        env:
+          KUBE_HOST: https://kubernetes.default.svc/
+          KUBE_CERTIFICATE: ${{ secrets.KUBE_CERTIFICATE }}
+          KUBE_TOKEN: ${{ secrets.GARDEN_TOKEN }}
+        with:
+          args: delete pods -n ${{env.DEPLOYMENT_NAMESPACE}} -l app=${{ env.DEPLOYMENT_LABEL}}

how the site works.md

@@ -1 +1,9 @@
+---
+title: how the site works
+tags:
+  - nerd-shit
+  - homelab
+---
+
+
 This obsidian vault is stored in a git repository on my gitea instance. It has a workflow which clones the quartz v4 repository, installs the dependencies, patches it, copies the vault contents into the relevant quartz v4 repo folder, runs the quartz build command, and tar's the build output as a release. I then have an nginx deployment in my k3s cluster that downloads the latest release tar ball, inflates it and serves it in an nginx server. It's a lot more straight forward than you would think.

version.txt

@@ -1 +1 @@
-1.15.0
+1.17.0