.gitea/workflows/build_push.yml

@@ -1,61 +1,42 @@
 name: Build and Push Image
-on:
+on: [ push ]
-    push:
-        branches:
-            - master
 
 jobs:
-    build:
+  build:
-        name: Build and push image
+    name: Build and push image
-        runs-on: ubuntu-latest
+    runs-on: ubuntu-latest
-        container: catthehacker/ubuntu:act-latest
+    container: catthehacker/ubuntu:act-latest
-        if: gitea.ref == 'refs/heads/master'
+    if: gitea.ref == 'refs/heads/master'
 
-        steps:
+    steps:
-            - name: Checkout
+    - name: Checkout
-              uses: actions/checkout@v4
+      uses: actions/checkout@v4
 
-            - name: Create Kubeconfig
+    - name: Create Kubeconfig
-              run: |
+      run: |
-                  mkdir $HOME/.kube
+        mkdir $HOME/.kube
-                  echo "${{ secrets.KUBEC_CONFIG_BUILDX }}" > $HOME/.kube/config
+        echo "${{ secrets.KUBEC_CONFIG_BUILDX }}" > $HOME/.kube/config        
 
-            - name: Set up Docker Buildx
+    - name: Set up Docker Buildx
-              uses: docker/setup-buildx-action@v3
+      uses: docker/setup-buildx-action@v3
-              with:
+      with:
-                  driver: kubernetes
+        driver: kubernetes
-                  driver-opts: |
+        driver-opts: |
-                      namespace=gitea-runner
+          namespace=gitea-runner
-                      qemu.install=true
+          qemu.install=true          
 
-            - name: Login to Docker Registry
+    - name: Login to Docker Registry
-              uses: docker/login-action@v3
+      uses: docker/login-action@v3
-              with:
+      with:
-                  registry: git.aridgwayweb.com
+        registry: git.aridgwayweb.com
-                  username: armistace
+        username: armistace
-                  password: ${{ secrets.REG_PASSWORD }}
+        password: ${{ secrets.REG_PASSWORD }}
 
-            - name: Build and push
+    - name: Build and push
-              uses: docker/build-push-action@v5
+      uses: docker/build-push-action@v5
-              with:
+      with:
-                  context: .
+        context: .
-                  push: true
+        push: true
-                  platforms: linux/amd64,linux/arm64
+        platforms: linux/amd64,linux/arm64
-                  tags: |
+        tags: |
-                      git.aridgwayweb.com/armistace/blog:latest
+          git.aridgwayweb.com/armistace/blog:latest    
-
-            - name: Deploy
-              run: |
-                  echo "Installing Kubectl"
-                  apt-get update
-                  apt-get install -y apt-transport-https ca-certificates curl gnupg
-                  curl -fsSL https://pkgs.k8s.io/core:/stable:/v1.33/deb/Release.key | gpg --dearmor -o /etc/apt/keyrings/kubernetes-apt-keyring.gpg
-                  chmod 644 /etc/apt/keyrings/kubernetes-apt-keyring.gpg
-                  echo 'deb [signed-by=/etc/apt/keyrings/kubernetes-apt-keyring.gpg] https://pkgs.k8s.io/core:/stable:/v1.33/deb/ /' | tee /etc/apt/sources.list.d/kubernetes.list
-                  chmod 644 /etc/apt/sources.list.d/kubernetes.list
-                  apt-get update
-                  apt-get install kubectl
-                  kubectl delete namespace blog
-                  kubectl create namespace blog
-                  kubectl create secret docker-registry regcred --docker-server=${{ vars.DOCKER_SERVER }} --docker-username=${{ vars.DOCKER_USERNAME }} --docker-password='${{ secrets.DOCKER_PASSWORD }}' --docker-email=${{ vars.DOCKER_EMAIL }} --namespace=blog
-                  kubectl apply -f kube/blog_pod.yaml && kubectl apply -f kube/blog_deployment.yaml && kubectl apply -f kube/blog_service.yaml

kube/blog_deployment.yaml

@@ -1,24 +0,0 @@
-apiVersion: apps/v1
-kind: Deployment
-metadata:
-  name: blog-deployment
-  labels:
-    app: blog
-  namespace: blog
-spec:
-  replicas: 3
-  selector:
-    matchLabels:
-      app: blog
-  template:
-    metadata:
-      labels:
-        app: blog
-    spec:
-      containers:
-      - name: blog
-        image: git.aridgwayweb.com/armistace/blog:latest
-        ports:
-        - containerPort: 8000
-      imagePullSecrets:
-        - name: regcred

kube/blog_pod.yaml

@@ -1,13 +0,0 @@
-apiVersion: v1
-kind: Pod
-metadata:
-    name: blog
-    namespace: blog
-spec:
-    containers:
-        - name: blog
-          image: git.aridgwayweb.com/armistace/blog:latest
-          ports:
-              - containerPort: 8000
-    imagePullSecrets:
-        - name: regcred

kube/blog_service.yaml

@@ -1,13 +0,0 @@
-apiVersion: v1
-kind: Service
-metadata:
-  name: blog-service
-  namespace: blog
-spec:
-  type: NodePort
-  selector:
-    app: blog 
-  ports:
-    - port: 80
-      targetPort: 8000
-      nodePort: 30009

src/content/when_to_use_ai.md

@@ -1,10 +1,4 @@
-Title: When to use AI
+# When to use AI
-Date: 2025-06-05 20:00
-Modified: 2025-06-06 08:00
-Category: AI, Data
-Tags: ai, python
-Slug: when-to-use-ai
-Authors: Andrew Ridgway
 
 ## The Great AI Debate: When to Trust the Machine vs. When to Stick to Your Brain
 
@@ -49,3 +43,52 @@ AI is good at *finding connections* and *handling ambiguity*, but it’s *not go
 
 > *“I was given a list of work types that could be grouped into 1 of 2 categories exclusively.”*
 > *“The problem was… the ‘work types’ and work requests were at best tangentially related.”*
+
+So I had to manually read each work type and map it to a work request. It was a *shudder-inducing* task.
+
+## The Final Thought
+
+So, in summary:
+
+*   **AI is not the best choice** when you need precision, accuracy, or a human touch.
+*   **AI is the best choice** when you need to handle ambiguity, find connections, or automate repetitive tasks.
+
+And that’s why I’m a journalist, a developer, and a DevOps expert. I know when to trust the machine and when to rely on my brain.
+
+> *“When in doubt, just do it.”*
+
+## Editable Structure for Easy Customization
+
+### 📝 Title When to use AI
+
+### 🧠 Introduction
+
+*   Briefly explain the question and the tone.
+
+### 🧩 Sections
+
+1.  **When AI is Not the Best Choice**
+    *   Subpoints:
+        *   Fuzzy logic dilemmas
+        *   Manual mapping tasks
+        *   Precision vs. AI’s “fuzzy” logic
+2.  **When AI is the Best Choice**
+    *   Subpoints:
+        *   Math and logic tasks
+        *   Automation of repetitive tasks
+        *   Suggesting numbers or constants
+3.  **The Human vs. AI Divide**
+    *   Highlight the importance of human judgment in critical tasks
+4.  **Final Thought**
+    *   Encourage readers to think critically about when to use AI
+
+### 📝 Conclusion
+
+*   Wrap up the key points and reinforce the message.
+
+## Tips for Editing
+
+*   Replace the example about the spreadsheet with your own scenario.
+*   Add a personal anecdote or a relatable example.
+*   Use humor to keep the tone light and engaging.
+*   Add a call to action: “Next time you’re stuck, ask yourself: ‘Is this a task for AI or a task for me?’”