fix dockerifle

.gitignore

@@ -5,5 +5,3 @@ __pycache__
 .vscode
 .zed
 pyproject.toml
-.ropeproject
-generated_files/*

Dockerfile

@@ -8,11 +8,7 @@ ENV PYTHONUNBUFFERED 1
 ADD src/ /blog_creator
 
 RUN apt-get update && apt-get install -y rustc cargo python-is-python3 pip python3-venv libmagic-dev git 
-# Need to set up git here or we get funky errors
-RUN git config --global user.name "Blog Creator"
-RUN git config --global user.email "ridgway.infrastructure@gmail.com"
-RUN git config --global push.autoSetupRemote true
-#Get a python venv going as well cause safety
+
 RUN python -m venv /opt/venv
 ENV PATH="/opt/venv/bin:$PATH"
 

generated_files/.gitignore

@@ -1,2 +0,0 @@
-*
-!.gitignore

generated_files/creating_an_ollama_blog_writer.md

@@ -0,0 +1,29 @@
+```markdown
+# Creating an Ollama Blog Writer: A Hilariously Tedious Adventure
+
+Hey tech enthusiasts! 👋 I’m back with another installment of my tech journey, but this time it’s personal. I decided to create a Python script that not only writes blogs for me (please don’t tell my boss), but also uses Ollama for some AI-assisted content creation and connects with Trilium for structured note-taking. Let’s dive into the details!
+
+### Step 1: Get Your Ollama On
+
+First things first, I needed a Python file that could talk to my local Ollama instance. If you haven't heard of Ollama, it's like a tiny llama in your terminal that helps with text generation. It took me a while to figure out how to configure the `.env` file and set up the connection properly. But once I did, I was off to a running start!
+
+### Step 2: Connecting Trilium for Structured Notes
+
+For this part, I used a Python library called `trilium-py` (because why not?). It's like having a brain that can store and retrieve information in an organized way. To make sure my notes are super structured, I had to find the right prompts and ensure they were fed into Ollama correctly. This part was more about figuring out how to structure the data than actually coding—but hey, it’s all part of the fun!
+
+### Step 3: Automating the Blog Creation
+
+Now that I have my notes and AI-generated content sorted, it was time to automate the blog creation process. Here’s where things got a bit Git-y (yes, I made up that word). I wrote a script that would create a new branch in our company's blog repo, push the changes, and voilà—a PR! Just like that, my humble contributions were ready for review by the big boss.
+
+### Step 4: Sending Notifications to Matrix
+
+Finally, as any good DevRel should do, I sent out a notification to our internal Matrix channel. It’s like Slack but with more tech talk and less memes about dogs in hats. The message was short and sweet—just a summary of the blog changes and a request for feedback. Hey, if Elon can tweet at Tesla shareholders, why not send a quick matrix message?
+
+### Wrapping Up
+
+Creating this Ollama Blog Writer wasn’t just about writing better blogs (though that would be nice). It was about embracing the joy of automation and the occasional struggle to get things working right. I learned a lot about Python libraries, local server configurations, and how to communicate effectively with my team via Matrix.
+
+So there you have it—a step-by-step guide on how not to write blogs but definitely how to automate the process. If you’re into tech, automation, or just want to laugh at someone else’s coding mishaps, this blog is for you!
+
+Keep on hacking (and automating), [Your Name]
+```

generated_files/powerbi_and_api_performance.md

@@ -0,0 +1,23 @@
+Title: When Data Visualization Meets Frustration: A Comic Take on PowerBI's API Woes
+
+---
+
+In the ever-evolving world of data and tech, few tools hold as much promise—or frustration—as Microsoft's PowerBI. Its sleek interface, intuitive visuals, and promise to simplify data into digestible insights have made it a favorite among many. But beneath its polished surface lies a storm of challenges that can leave even the most seasoned developers in its dust.
+
+Imagine this: you've spent hours refining your data model, only to find that your team's hierarchy resists your attempt to share sensitive information without breaking hearts. "We're all on different tiers," you mutter, your frustration evident. But here's the kicker—PowerBI won't even let everyone in your company join the party if they're not up to tier 5. And guess what? Most companies operate in reality tier 3 at best. So, step one: API calls to PowerBI. You'd think pulling data would be straightforward, but oh, how it pulls you into a tailspin.
+
+Here's where things get interesting: PowerBI APIs are mostly limited to small tables. It's like trying to fit furniture through a door that's slightly too narrow—it just doesn't work unless you have a magic wand (or in this case, an API upgrade). Imagine needing to fetch data from three different on-premises databases seamlessly; PowerBI might just give you the finger.
+
+Now, if your company happens to be in the Microsoft ecosystem—like the Azure universe—then maybe things are a bit easier. But here's the kicker: it's not being top-to-bottom within that ecosystem that counts as success. If even one part is outside, you're facing performance issues akin to driving through a snowstorm without an umbrella. You get the picture.
+
+So what does this mean for the average user? Unless you've got no choice but to use PowerBI... well, let's just say it might not be your friend in such scenarios. It's like having a GPS that only works if you're willing to drive on a dirt road and expect it to guide you through with zero warnings—sounds great until you end up stranded.
+
+But wait, maybe there's silver lining. Other tools have learned the hard lessons PowerBI has taught us. They allow APIs beyond just small tables and handle ecosystems with ease, making them more versatile for real-world applications. It's like upgrading your car's GPS to one that not only knows all the roads but also can navigate through different weather conditions without complaints.
+
+In conclusion, while PowerBI is undeniably a powerful tool when used correctly—like driving in calm weather on perfectly paved roads—it has its limitations. Its API restrictions and ecosystem integration issues make it less than ideal for many real-world scenarios. So unless you're in a controlled environment where these issues don't arise, maybe it's time to explore other options that can handle the data journey with more grace.
+
+After all, Data Overload isn't just a Star Trek term—it could be your reality if you're not careful with PowerBI. 
+
+---
+
+*So, is PowerBI still your best friend in this complex tech world? Or are there better tools out there waiting to be discovered? Share your thoughts and experiences below!*

generated_files/the_melding_of_data_engineering_and_ai.md

@@ -0,0 +1,35 @@
+# Wrangling Data: A Reality Check
+
+Okay, let’s be honest. Data wrangling isn't glamorous. It’s not a sleek, automated process of magically transforming chaos into insights. It’s a messy, frustrating, and surprisingly human endeavor. Let’s break down the usual suspects – the steps we take to get even a vaguely useful dataset, and why they’re often a monumental task.
+
+**Phase 1: The Hunt**
+
+First, you’re handed a dataset. Let’s call it “Customer_Data_v2”. It’s… somewhere. Maybe a CSV file, maybe a database table, maybe a collection of spreadsheets that haven’t been updated since 2008. Finding it is half the battle. It's like searching for a decent cup of coffee in Melbourne – you know it’s out there, but it’s often hidden behind a wall of bureaucracy.
+
+**Phase 2: Deciphering the Ancient Texts**
+
+Once you *find* it, you start learning what it *means*. This is where things get… interesting. You’re trying to understand what fields represent, what units of measurement are used, and why certain columns have bizarre names (seriously, “Customer_ID_v3”?). It takes x amount of time (depends on the industry, right?). One week for a small bakery, six months for a multinational insurance company. It’s a wild ride.
+
+You’ll spend a lot of time trying to understand the business context. "CRMs" for Customer Relationship Management? Seriously? It’s a constant stream of jargon and acronyms that make your head spin.
+
+**Phase 3: The Schema Struggle**
+
+Then there’s the schema. Oh, the schema. It takes a couple of weeks to learn the schema. It’s like deciphering ancient hieroglyphics, except instead of predicting the rise and fall of empires, you’re trying to understand why a field called “Customer_ID_v3” exists. It’s a puzzle, and a frustrating one at that.
+
+**Phase 4: The Tooling Tango**
+
+You’ll wrestle with the tools. SQL interpreters, data transformation software – they’re all there, but they’re often clunky, outdated, and require a surprising amount of manual effort. It's like finding a decent cup of coffee in Melbourne – you know it’s out there, but it’s often hidden behind a wall of bureaucracy.
+
+**Phase 5: The Reporting Revelation (and Despair)**
+
+Finally, you get to the reporting tool. And cry. Seriously, who actually *likes* this part? It’s a soul-crushing exercise in formatting and filtering, and the output is usually something that nobody actually reads.
+
+**The AI Factor – A Realistic Perspective**
+
+Now, everyone’s talking about AI. And, look, I’m not saying AI is a bad thing. It’s got potential. But let’s be realistic. This will for quite some time be the point where we need people. AI can automate the process of extracting data from a spreadsheet. But it can’t understand *why* that spreadsheet was created in the first place. It can’t understand the context, the assumptions, the biases. It can’t tell you if the data is actually useful.
+
+We can use tools like datahub to capture some of this business knowledge but those tool are only as good as the people who use them. We need to make sure AI is used for those uniform parts – schema discovery, finding the tools, ugh reporting. But where the rubber hits the road… thats where we need people and that we are making sure that there is a person interpreting not only what goes out.. but what goes in.
+
+**The Bottom Line**
+
+It’s a bit like trying to build a great BBQ. You can buy the fanciest gadgets and the most expensive wood, but if you don’t know how to cook, you’re going to end up with a burnt mess. So, let’s not get carried away with the hype. Let’s focus on building a data culture that values human intelligence, critical thinking, and a good dose of common sense. And let’s keep wrangling. Because, let’s be honest, someone’s gotta do it.

src/ai_generators/ollama_md_generator.py

@@ -1,9 +1,8 @@
-import os, re, json, random, time, string
+import os, re, json, random, time
 from ollama import Client
 import chromadb
 from langchain_ollama import ChatOllama
 
-
 class OllamaGenerator:
 
     def __init__(self, title: str, content: str, inner_title: str):
@@ -11,7 +10,7 @@ class OllamaGenerator:
         self.inner_title = inner_title
         self.content = content
         self.response = None
-        self.chroma = chromadb.HttpClient(host="172.18.0.2", port=8000)
+        self.chroma = chromadb.HttpClient(host="172.19.0.2", port=8000)
         ollama_url = f"{os.environ["OLLAMA_PROTOCOL"]}://{os.environ["OLLAMA_HOST"]}:{os.environ["OLLAMA_PORT"]}"
         self.ollama_client = Client(host=ollama_url)
         self.ollama_model = os.environ["EDITOR_MODEL"]
@@ -88,13 +87,11 @@ class OllamaGenerator:
         embeds = self.ollama_client.embed(model=self.embed_model, input=draft_chunks)
         return embeds.get('embeddings', [])
 
-    def id_generator(self, size=6, chars=string.ascii_uppercase + string.digits):
-        return ''.join(random.choice(chars) for _ in range(size))
 
     def load_to_vector_db(self):
         '''Load the generated blog drafts into a vector database'''
-        collection_name = f"blog_{self.title.lower().replace(" ", "_")}_{self.id_generator()}"
-        collection = self.chroma.get_or_create_collection(name=collection_name)#, metadata={"hnsw:space": "cosine"})
+        collection_name = f"blog_{self.title.lower().replace(" ", "_")}"
+        collection = self.chroma.get_or_create_collection(name=collection_name, metadata={"hnsw:space": "cosine"})
         #if any(collection.name == collectionname for collectionname in self.chroma.list_collections()):
         #    self.chroma.delete_collection("blog_creator")
         for model in self.agent_models:
@@ -156,7 +153,7 @@ class OllamaGenerator:
 
     def generate_commit_message(self):
         prompt_system = "You are a blog creator commiting a piece of content to a central git repo"
-        prompt_human = f"Generate a 5 word git commit message describing {self.response}"
+        prompt_human = f"Generate a 10 word git commit message describing {self.response}"
         messages = [("system", prompt_system), ("human", prompt_human),]
         commit_message = self.llm.invoke(messages).text()
         return commit_message

src/main.py

@@ -28,7 +28,7 @@ for note in tril_notes:
     ai_gen.save_to_file(blog_path)
     # Generate commit messages and push to repo
     commit_message = ai_gen.generate_commit_message()
-    git_user = os.environ["GIT_USER"]
+    git_user = os.environp["GIT_USER"]
     git_pass = os.environ["GIT_PASS"]
-    repo_manager = git_repo.GitRepository("blog/", git_user, git_pass)
+    repo_manager = git_repo("blog/", git_user, git_pass)
     repo_manager.create_copy_commit_push(blog_path, os_friendly_title, commit_message)

src/repo_management/repo_manager.py

@@ -1,5 +1,4 @@
 import os, shutil
-from urllib.parse import quote
 from git import Repo
 from git.exc import GitCommandError
 
@@ -11,20 +10,11 @@ class GitRepository:
     def __init__(self, repo_path, username=None, password=None):
         git_protocol = os.environ["GIT_PROTOCOL"]
         git_remote = os.environ["GIT_REMOTE"]
-        #if username is not set we don't need parse to the url
-        if username==None or password == None:
-            remote = f"{git_protocol}://{git_remote}"
-        else:
-            # of course if it is we need to parse and escape it so that it
-            # can generate a url
-            git_user = quote(username)
-            git_password = quote(password)
-            remote = f"{git_protocol}://{git_user}:{git_password}@{git_remote}"
+        remote = f"{git_protocol}://{username}:{password}@{git_remote}"
 
         if os.path.exists(repo_path):
             shutil.rmtree(repo_path)
         self.repo_path = repo_path
-        print("Cloning Repo")
         Repo.clone_from(remote, repo_path)
         self.repo = Repo(repo_path)
         self.username = username
@@ -50,9 +40,8 @@ class GitRepository:
 
     def pull(self, remote_name='origin', ref_name='main'):
         """Pull updates from a remote repository with authentication"""
-        print("Pulling Latest Updates (if any)")
         try:
-            self.repo.remotes[remote_name].pull(ref_name)
+            self.repo.remotes[remote_name].pull(ref_name=ref_name)
             return True
         except GitCommandError as e:
             print(f"Pulling failed: {e}")
@@ -63,21 +52,19 @@ class GitRepository:
         return [branch.name for branch in self.repo.branches]
     
     
-    def create_and_switch_branch(self, branch_name, remote_name='origin', ref_name='main'):
+    def create_branch(self, branch_name, remote_name='origin', ref_name='main'):
         """Create a new branch in the repository with authentication."""
         try:
-            print(f"Creating Branch {branch_name}")
             # Use the same remote and ref as before
-            self.repo.git.branch(branch_name)
-        except GitCommandError:
-            print("Branch already exists switching")
-            # ensure remote commits are pulled into local
-        self.repo.git.checkout(branch_name)
+            self.repo.git.branch(branch_name, commit=True)
+            return True
+        except GitCommandError as e:
+            print(f"Failed to create branch: {e}")
+            return False
         
     def add_and_commit(self, message=None):
         """Add and commit changes to the repository."""
         try:
-            print("Commiting latest draft")
             # Add all changes
             self.repo.git.add(all=True)
             # Commit with the provided message or a default
@@ -85,18 +72,20 @@ class GitRepository:
                 commit_message = "Added and committed new content"
             else:
                 commit_message = message
-            self.repo.git.commit(message=commit_message)
+            self.repo.git.commit(commit_message=commit_message)
             return True
         except GitCommandError as e:
             print(f"Commit failed: {e}")
             return False
         
     def create_copy_commit_push(self, file_path, title, commit_messge):
-        self.create_and_switch_branch(title)
+        self.create_branch(title)
 
-        self.pull(ref_name=title)
         shutil.copy(f"{file_path}", f"{self.repo_path}src/content/")
 
-        self.add_and_commit(f"'{commit_messge}'")
+        self.add_and_commit(commit_messge)
 
-        self.repo.git.push()
+        self.repo.git.push(remote_name='origin', ref_name=title, force=True)
+
+    def remove_repo(self):
+        shutil.rmtree(self.repo_path)