Forgot to build the pages.

public/posts/index.xml

@@ -1,12 +1,21 @@
 <?xml version="1.0" encoding="utf-8" standalone="yes"?>
 <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
   <channel>
-    <title>Posts on Norm-Hosted 💾</title>
+    <title>Posts on Norm-working Packets 💾</title>
     <link>/posts.html</link>
-    <description>Recent content in Posts on Norm-Hosted 💾</description>
+    <description>Recent content in Posts on Norm-working Packets 💾</description>
     <generator>Hugo -- gohugo.io</generator>
     <language>en-us</language>
-    <lastBuildDate>Fri, 22 Sep 2023 15:07:10 -0400</lastBuildDate><atom:link href="/posts/index.xml" rel="self" type="application/rss+xml" />
+    <lastBuildDate>Mon, 25 Sep 2023 12:51:55 -0400</lastBuildDate><atom:link href="/posts/index.xml" rel="self" type="application/rss+xml" />
+    <item>
+      <title>Creating a BirdNetPi Dashboard in HomeAssistant - Part 1</title>
+      <link>/posts/birdnet_homeassistant.html</link>
+      <pubDate>Mon, 25 Sep 2023 12:51:55 -0400</pubDate>
+      
+      <guid>/posts/birdnet_homeassistant.html</guid>
+      <description>Learn how to take BirdNET-Pi Detections to create and display entities in HomeAssistant.</description>
+    </item>
+    
     <item>
       <title>Pushing a Single Local Git Repo to Multiple Remote Repos</title>
       <link>/posts/multiple_git_remotes.html</link>

public/posts/multiple_git_remotes.html

@@ -5,7 +5,7 @@
 <meta http-equiv="X-UA-Compatible" content="IE=edge">
 <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
 <meta name="robots" content="index, follow">
-<title>Pushing a Single Local Git Repo to Multiple Remote Repos | Norm-Hosted 💾</title>
+<title>Pushing a Single Local Git Repo to Multiple Remote Repos | Norm-working Packets 💾</title>
 <meta name="keywords" content="git, backups, commandline">
 <meta name="description" content="Learn one way to push your git changes to multiple remote repositories.">
 <meta name="author" content="Me">
@@ -43,12 +43,12 @@ if (!doNotTrack) {
 <meta property="og:description" content="Learn one way to push your git changes to multiple remote repositories." />
 <meta property="og:type" content="article" />
 <meta property="og:url" content="/posts/multiple_git_remotes.html" />
-<meta property="og:image" content="/%3Cimage%20path/url%3E" /><meta property="article:section" content="posts" />
+<meta property="og:image" content="/multiple-git-cover-img.png" /><meta property="article:section" content="posts" />
 <meta property="article:published_time" content="2023-09-22T15:07:10-04:00" />
-<meta property="article:modified_time" content="2023-09-22T15:07:10-04:00" /><meta property="og:site_name" content="Norm-Hosted" />
+<meta property="article:modified_time" content="2023-09-22T15:07:10-04:00" /><meta property="og:site_name" content="Norm-working Packets" />
 
 <meta name="twitter:card" content="summary_large_image" />
-<meta name="twitter:image" content="/%3Cimage%20path/url%3E" />
+<meta name="twitter:image" content="/multiple-git-cover-img.png" />
 <meta name="twitter:title" content="Pushing a Single Local Git Repo to Multiple Remote Repos"/>
 <meta name="twitter:description" content="Learn one way to push your git changes to multiple remote repositories."/>
 
@@ -80,7 +80,7 @@ if (!doNotTrack) {
   "articleBody": "Why push to multiple repos? Do want to use both Github \u0026 and a Self-hosted Git Repo? Here’s how I’ve been doing it!\nI really enjoy self-hosting services that I use everyday. One of those includes a git-style version control software. In my case, I’ve been running Gitea for a few years now and have been really satisfied with everything (except for that one time that an update broke all my templates).\nAt the same time, there’s the entire social element that comes with Github along with having your public repositories available in a place that other developers are already spending time on. Instead of adding, committing, commenting, and pushing on two different repos, here’s how I run all those commands just once and push it to both repos.\nNote: An import git note to remember is that you can only push to multiple remote repositories. You’ll have to select which repo you want to be the main pull repository. Have this be remote-url-one in the below instructions.\nCommand Line Instructions These instructions come after you initialize the repo in your directory. Make sure you have both of your remote git URLs handy at this point!\ngit remote add {{ remote-name }} {{ remote-url-one }} git remote set-url --add --push {{ remote-name }} {{ remote-url-one }} git remote set-url --add --push {{ remote-name }} {{ remote-url-two }} To confirm that everything worked as expected, run git remote -v to check your remote repos. You should see one repo in there twice, once for (push) and once for (fetch).\nI use the remote name “all” for multiple repos, so here’s what my git remote -v returns:\n\u003e git remote -v all https://git.rsmsn.co/Normanras/rsmsn_blog.git (fetch) all https://git.rsmsn.co/Normanras/rsmsn_blog.git (push) all https://github.com/Normanras/rsmsn_blog.git (push) all https://git.rsmsn.co/Normanras/rsmsn_ddblog.git (push) To now push to your repositories, after adding and committing run git push {{ remote-name }} --all. My command is git push all --all (see why I use all, now?)\nHere’s the man page description on the --all flag:\n--all Push all branches (i.e. refs under refs/heads/); cannot be used Instead of naming each ref to push, specifies that all refs under end, locally updated refs will be force updated on the remote end, Do everything except actually send the updates. same as prefixing all refs with a colon. And that’s it! You should be able to push everything to both of your repos fairly easily now with this new set commands.\n",
   "wordCount" : "403",
   "inLanguage": "en",
-  "image":"/%3Cimage%20path/url%3E","datePublished": "2023-09-22T15:07:10-04:00",
+  "image":"/multiple-git-cover-img.png","datePublished": "2023-09-22T15:07:10-04:00",
   "dateModified": "2023-09-22T15:07:10-04:00",
   "author":{
     "@type": "Person",
@@ -92,7 +92,7 @@ if (!doNotTrack) {
   },
   "publisher": {
     "@type": "Organization",
-    "name": "Norm-Hosted 💾",
+    "name": "Norm-working Packets 💾",
     "logo": {
       "@type": "ImageObject",
       "url": "/favicon.ico"
@@ -113,7 +113,7 @@ if (!doNotTrack) {
 <header class="header">
     <nav class="nav">
         <div class="logo">
-            <a href="../" accesskey="h" title="Norm-Hosted 💾 (Alt + H)">Norm-Hosted 💾</a>
+            <a href="../" accesskey="h" title="Norm-working Packets 💾 (Alt + H)">Norm-working Packets 💾</a>
             <div class="logo-switches">
                 <button id="theme-toggle" accesskey="t" title="(Alt + T)">
                     <svg id="moon" xmlns="http://www.w3.org/2000/svg" width="24" height="18" viewBox="0 0 24 24"
@@ -216,6 +216,11 @@ there twice, once for <code>(push)</code> and once for <code>(fetch)</code>.</p>
       <li><a href="../tags/commandline.html">commandline</a></li>
     </ul>
 <nav class="paginav">
+  <a class="prev" href="../posts/birdnet_homeassistant.html">
+    <span class="title">« Prev</span>
+    <br>
+    <span>Creating a BirdNetPi Dashboard in HomeAssistant - Part 1</span>
+  </a>
   <a class="next" href="../posts/hosting_hugo_troubles.html">
     <span class="title">Next »</span>
     <br>
@@ -228,7 +233,7 @@ there twice, once for <code>(push)</code> and once for <code>(fetch)</code>.</p>
     </main>
     
 <footer class="footer">
-    <span>&copy; 2023 <a href="../">Norm-Hosted 💾</a></span>
+    <span>&copy; 2023 <a href="../">Norm-working Packets 💾</a></span>
     <span>
         Powered by
         <a href="https://gohugo.io/" rel="noopener noreferrer" target="_blank">Hugo</a> &