stray w

Reviewed-on: #8

.gitea/workflows/build_push.yml

@@ -1,42 +1,61 @@
 name: Build and Push Image
-on: [ push ]
+on:
+    push:
+        branches:
+            - master
 
 jobs:
-  build:
-    name: Build and push image
-    runs-on: ubuntu-latest
-    container: catthehacker/ubuntu:act-latest
-    if: gitea.ref == 'refs/heads/master'
+    build:
+        name: Build and push image
+        runs-on: ubuntu-latest
+        container: catthehacker/ubuntu:act-latest
+        if: gitea.ref == 'refs/heads/master'
 
-    steps:
-    - name: Checkout
-      uses: actions/checkout@v4
+        steps:
+            - name: Checkout
+              uses: actions/checkout@v4
 
-    - name: Create Kubeconfig
-      run: |
-        mkdir $HOME/.kube
-        echo "${{ secrets.KUBEC_CONFIG_BUILDX }}" > $HOME/.kube/config        
+            - name: Create Kubeconfig
+              run: |
+                  mkdir $HOME/.kube
+                  echo "${{ secrets.KUBEC_CONFIG_BUILDX }}" > $HOME/.kube/config
 
-    - name: Set up Docker Buildx
-      uses: docker/setup-buildx-action@v3
-      with:
-        driver: kubernetes
-        driver-opts: |
-          namespace=gitea-runner
-          qemu.install=true          
+            - name: Set up Docker Buildx
+              uses: docker/setup-buildx-action@v3
+              with:
+                  driver: kubernetes
+                  driver-opts: |
+                      namespace=gitea-runner
+                      qemu.install=true
 
-    - name: Login to Docker Registry
-      uses: docker/login-action@v3
-      with:
-        registry: git.aridgwayweb.com
-        username: armistace
-        password: ${{ secrets.REG_PASSWORD }}
+            - name: Login to Docker Registry
+              uses: docker/login-action@v3
+              with:
+                  registry: git.aridgwayweb.com
+                  username: armistace
+                  password: ${{ secrets.REG_PASSWORD }}
 
-    - name: Build and push
-      uses: docker/build-push-action@v5
-      with:
-        context: .
-        push: true
-        platforms: linux/amd64,linux/arm64
-        tags: |
-          git.aridgwayweb.com/armistace/blog:latest    
+            - name: Build and push
+              uses: docker/build-push-action@v5
+              with:
+                  context: .
+                  push: true
+                  platforms: linux/amd64,linux/arm64
+                  tags: |
+                      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

@@ -0,0 +1,24 @@
+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

@@ -0,0 +1,13 @@
+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

@@ -0,0 +1,13 @@
+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/first_ai_blog.md

@@ -12,11 +12,11 @@ As mentioned in the last post I have been experimenting with AI content generati
 
 It's still not in the state I want it to be and isn't connecting to the actual blog repo yet (the idea being that I edit and change as part of a review process). But it is generating stuff that I thought would be worth a share just for fun. The eventual idea is the container will be something I trigger as part of a CI/CD process when the equipment is up and running but the final "production" implementation is still being fleshed out in my head (if you can call a homelab project "production")
 
-The focus to this point has been on prompt engineering and model selection. A big part of this is that it needs to be able to run completely indepdantly of any cloud services so no Chat GPT.
+The focus to this point has been on prompt engineering and model selection. A big part of this is that it needs to be able to run completely independently of any cloud services so no Chat GPT.
 
-The obvious solution is [ollama](https://ollama.com) I'm luck enough to have a modest secondary gaming rig in my living room with an nvidia 2060 in it that can act as a modest AI server so I have set it up there.
+The obvious solution is [ollama](https://ollama.com) I'm lucky enough to have a modest secondary gaming rig in my living room with an nvidia 2060 in it that can act as a modest AI server so I have set it up there.
 
-This server has allowed me to experiment almost at will with models. a few I tried included
+This server has allowed me to experiment, almost at will, with models. a few I tried included
 
 - llama3.2
 - zephyr
@@ -29,6 +29,7 @@ However I have found that mistral-nemo seems to be the strongest contender, at l
 You can see the code and what I have been working on for more details [HERE](https://git.aridgwayweb.com/armistace/blog_creator)
 
 #### The summary prompt used by mistral to generate this post
+
 _The following is what I have in trilium to generate the AI written content_
 
 Get a python file that can communicate with a local ollama instance
@@ -50,7 +51,8 @@ Send a notification to matrix that there is a new PR in and give a summary of th
 _as you can see it pretty light on content so what it generates given this lack of context I feel is pretty good_
 
 # Let the post begin (begin...begin...begin...)
-_What follows is what it generated.. yes it is hilarious but well... it was to good not to share_
+
+_What follows is what it generated.. yes it is hilarious but well... it was too good not to share_
 
 # G'day, mates! Let's make an Ollama Blog Writer!
 
@@ -157,4 +159,102 @@ But its safe to say its still producing some hilarious results that are still so
 
 I'll keep tinkering away in the few moments I get to myself but this has been fun
 
+# _UPDATE UPDATE UPDATE_
+
+Ok so just before posting this I read about a new model supposedly on par with chatgpt o1... enter [Deepseek-r1](https://ollama.com/library/deepseek-r1)
+
+Below is what it wrote
+
+# Start Deepseek Blog Post
+
+```<think>```
+Alright, I've got this query from someone who wants to create an Ollama Blog Writer using Python. Let me break down what they're asking for.
+
+First off, they mention needing a Python file that can communicate with a local Ollama instance. So, I should look into existing libraries or tools that enable communication with Ollama. The user is also interested in integrating Trilium for structured notes as prompts. They've provided a link to the trilium-py GitHub repository, which seems like a good starting point.
+
+Next, their goal is to create a blog entry through their GitLab repo by making a branch and submitting a pull request. They want the PR content approved before proceeding further. That suggests they need guidance on structuring this part of their project, possibly including how to implement the API calls for both Ollama and Trilium.
+
+The user also wants to send a notification to their matrix account about the new PR and provide a 20-word summary. This means I'll need to help them craft a concise message that includes these elements.
+
+Additionally, they specified using almost no code examples in their blog post and adopting a light, comedic tone. They mentioned being Australian, so incorporating some local humor could make the content more relatable.
+
+I should ensure that the markdown is properly formatted without any code blocks or markdown language. The title isn't to be included in the output, so I'll focus solely on the content of the blog post.
+
+Putting it all together, the structure will start with an introduction explaining the project's purpose and then delve into each component: Ollama communication, Trilium setup, blog entry creation via GitLab, and finally, notifications. Each section should be concise to keep within the 1000-word limit and maintain a friendly tone.
+
+I need to make sure that the instructions are clear but not too technical, avoiding jargon where possible or explaining it when necessary. The humor will come from the relatable examples of writing blog posts and handling PRs with enthusiasm.
+```</think>```
+
+# Creating an Ollama Blog Writer  
+
+Alright, fellow tech enthusiasts! Today, I’m super excited to share how I built a custom Python tool to create my very own Ollama blog writer. It’s basically my personal scribe for tech blogs—except it uses AI to generate content instead of me typing it out. Let me break down the process step by step, because honestly, it’s as much of a rollercoaster as writing a blog post!  
+
+## Step 1: Communicating with Ollama  
+
+First things first, I needed to connect my Python script to a running Ollama instance. Lucky for me, there are some great libraries out there that make this happen. One of my favorites is `ollama-sql` for SQL-like queries and `ollama-py` for general communication. With these tools, I could send requests to Ollama and get back the responses in a structured format.  
+
+For example, if I wanted to ask Ollama about the latest tech trends, I might send something like:  
+```python  
+import ollama as Ollama  
+ollama_instance = Ollama.init()  
+response = ollama_instance.query("What are the top AI developments this year?")  
+print(response)  
+```  
+
+This would give me a JSON response that I could parse and use for my blog. Easy peasy!  
+
+## Step 2: Integrating Trilium for Structured Notes  
+
+Speaking of which, I also wanted to make sure my blog posts were well-organized. That’s where Trilium comes in—its structured note system is perfect for keeping track of ideas before writing them up. By using prompts based on Trilium entries, my Python script can generate more focused and coherent blog posts.  
+
+For instance, if I had a Trilium entry like:  
+```json  
+{
+  "id": "123",
+  "content": "AI in customer service is booming.",
+  "type": "thought"
+}
+```
+I could use that as a prompt to generate something like:  
+*"In the rapidly evolving landscape of AI applications, customer service has taken a quantum leap with AI-powered platforms...."*  
+
+Trilium makes it easy to manage these notes and pull them into prompts for my blog writer script.  
+
+## Step 3: Creating Blog Entries in My GitLab Repo  
+
+Now, here’s where things get interesting (and slightly nerve-wracking). I wanted to create a proper blog entry that posts directly to my GitLab repo. So, I forked the [aridgwayweb/blog](https://git.aridgwayweb.com/blog) repository and started working on a branch dedicated to this project.  
+
+In my `create_blog_entry.py` script, I used GitLab’s API to create a new entry. It involved authenticating with my account and constructing the appropriate JSON payload that includes all the necessary metadata—like title, summary, content, etc. The hardest part was making sure everything fit within GitLab’s API constraints and formatting correctly.  
+
+Here’s an excerpt of what I sent:  
+```python  
+import gitlab  
+gl = gitlab.Gitlab('gitlab.com', 'your_api_key')  
+entry = gl.entries.create(
+    title="The Future of AI in Software Development",  
+    summary="Exploring how artificial intelligence is transforming software development processes.",  
+    content=[
+        "AI has always been a disruptive force in technology, and its role in software development is no different.",
+        "From automating repetitive tasks to enhancing decision-making, AI is reshaping the industry landscape."
+    ]
+)  
+```  
+
+And then I notified myself that it was done!  
+
+## Step 4: Sending Notifications via Matrix  
+
+Finally, after everything was up and running, I sent a quick notification to my matrix account about the new pull request. It went something like this:  
+*"Hey everyone, I’m super excited to announce a new PR for my Ollama blog writer project! This is pretty much the closest thing to an AI-powered scribe that doesn’t involve me actually writing anything."*  
+
+Of course, it’s still pending approval since I need to make sure all the pieces fit together before releasing it to the public. But hey, at least I’ve got a solid foundation to build on!  
+
+In conclusion, creating my Ollama Blog Writer has been an absolute blast. It combines my love for tech with Python and AI in ways I never imagined. Now, if only I could find a way to automate writing blog *reviews*…
+
+# End blog post
+
+Now I'm not sure what the ```<think>``` tags are all about but this is a very interesting model and has produced the closest thing to what the prompt Asked for in my opinion
+
+Deepseek-r1 is definitely one to keep an eye on and one I'll be using in the future
+
 Until next time (But will the content come from me?)!

src/content/when_to_use_ai.md

@@ -0,0 +1,54 @@
+# Human Introduction
+Well.. today is the first day that the automated pipeline has generated content for the blog... still a bit of work to do including
+1. establishing a permanent vectordb solution (chromadb? pg_vector?)
+2. Notification to Matrix that something has happened
+3. Updating Trilium so that the note is marked as blog_written=true
+
+BUT it can take a note from trilium, generate drafts with mulitple agents, and then use RAG to have an editor go over those drafts.
+
+I'm particularly proud of the randomness I've applied to temperature, top_p and top_k for the different draft agents. This means that each pass is giving me quite different "creativity" (as much as that can be applied to an algorithm that is essentially munging letters together that have a high probability of being together) It has created some really interesting variation for the editor to work with and getting some really interesting results.
+
+Anyways, without further ado, I present to you the first, pipeline written, AI content for this blog
+
+---
+
+# When to use AI 😄
+*A journalist, software developer, and DevOps expert’s take on when AI is overkill and when it’s just the right tool*
+
+When I was building a spreadsheet called “shudders,” I was trying to figure out how to automate the process of mapping work types to work requests. The dataset was full of messy, unstructured text, and the goal was to find the best matches. At first, I thought, “This is a perfect use case for AI!” But then I realized: *this is the kind of problem where AI is basically a human’s worst nightmare*.
+
+So, let’s break it down.
+
+### 🧠 When AI is *not* the answer
+
+AI is great at pattern recognition, but it’s not great at *understanding context*. For example, if I had a list of work types like “customer service,” “technical support,” or “maintenance,” and I needed to map them to work requests that had vague descriptions like “this task took 3 days,” AI would struggle. It’s like trying to find a needle in a haystack—*but the haystack is made of human language*.
+
+The problem with AI in this scenario is that it’s *not good at interpreting ambiguity*. If the work types are vague, the AI might mislabel them, leading to errors. Plus, when the data is messy, AI can’t keep up. I remember one time I tried to use a chatbot to classify work requests. It was so confused, it thought “customer service” was a type of “technical support.” 😅 The result? A spreadsheet full of “unknown” entries.
+
+### 🧮 When AI *is* the answer
+
+There are some scenarios where AI is *definitely* the way to go. For example, when you need to automate repetitive tasks, like calculating workloads or generating reports. These tasks are math-heavy and don’t require creative thinking. Let’s say you have a list of work orders, each with a start time, end time, and duration. You want to calculate the average time per task. AI can do that with precision. It’s like a calculator, but with a personality.
+
+Another example: if you need to generate a report that summarizes key metrics, AI can handle that. It’s not about creativity, it’s about logic. And that’s where traditional programming shines.
+
+### 🧪 The balance between AI and human oversight
+
+AI is a tool, not a replacement for human judgment. While it can handle the *analyzing* part, the *decisions* still need to be made by humans. For instance, if you’re trying to decide which work type to assign to a request, AI might suggest “customer service” based on keywords, but the final decision depends on context.
+
+So, in the end, AI is a *helper*, not a *replacement*. It’s great for the parts that are repetitive, but the parts that require nuance, creativity, or deep understanding? That’s where humans step in.
+
+### 🧩 Final thoughts
+
+AI is like a superpower—great at certain things, not so great at others. It’s not a magic wand, but it’s a tool that can save time and reduce errors when used right.
+
+So, when is it time to say “AI, nope”? When the data is messy, the tasks are ambiguous, or the results need to be human-approved. And when is it time to say “AI, yes”? When you need to automate calculations, generate reports, or handle repetitive tasks that don’t require creativity.
+
+### 🧩 Summary
+
+| Scenario | AI? | Reason |
+|---|---|---|
+| Ambiguous data | ❌ | AI struggles with context |
+| Repetitive tasks | ✅ | AI handles math and logic |
+| Creative decisions | ❌ | AI lacks the ability to think creatively |
+
+In the end, AI is just another tool. Use it when it works, and don’t let it define your workflow. 😄 *And if you ever feel like AI is overstepping, remember: it’s just trying to be helpful. Sometimes it’s not the best choice. Sometimes it’s the only choice.*