<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Reference on Jacob Edwards</title>
    <link>https://jacobedwards.org/tags/reference/</link>
    <description>Recent content in Reference on Jacob Edwards</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <managingEditor>jacob@jacobedwards.org (Jacob Edwards)</managingEditor>
    <webMaster>jacob@jacobedwards.org (Jacob Edwards)</webMaster>
    <lastBuildDate>Sat, 21 Mar 2026 19:00:57 -0500</lastBuildDate>
    <atom:link href="https://jacobedwards.org/tags/reference/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Automatic GitHub Mirroring for Self-Hosted Repositories</title>
      <link>https://jacobedwards.org/posts/github-mirroring/</link>
      <pubDate>Sat, 21 Mar 2026 18:58:00 -0500</pubDate><author>jacob@jacobedwards.org (Jacob Edwards)</author>
      <guid>https://jacobedwards.org/posts/github-mirroring/</guid>
      <description>&lt;p&gt;While there are many benefits to self-hosting git repositories,&#xA;there are a number of reasons to mirror them to GitHub: Redundancy,&#xA;discoverability, integration with other users, etc.  It&amp;rsquo;s actually&#xA;very easy to set up automatic GitHub repository creation and mirroring&#xA;using the &lt;a href=&#34;https://cli.github.com/&#34;&gt;GitHub CLI&lt;/a&gt; and simple git&#xA;hooks. The process is explained below.&lt;/p&gt;&#xA;&lt;h2 id=&#34;generating-a-github-personal-access-token&#34;&gt;Generating a GitHub Personal Access Token&lt;/h2&gt;&#xA;&lt;p&gt;The first step is to go to &amp;ldquo;Developer Settings&amp;rdquo; in settings, then&#xA;generate a fine-grained &lt;a href=&#34;https://github.com/settings/personal-access-tokens&#34;&gt;personal access&#xA;token&lt;/a&gt; with&#xA;read/write access to &amp;ldquo;Administration&amp;rdquo;. This token will be used to&#xA;create and update repositories.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Packaging Software for OpenBSD</title>
      <link>https://jacobedwards.org/posts/openbsd-packaging/</link>
      <pubDate>Sun, 15 Feb 2026 22:09:45 -0600</pubDate><author>jacob@jacobedwards.org (Jacob Edwards)</author>
      <guid>https://jacobedwards.org/posts/openbsd-packaging/</guid>
      <description>&lt;p&gt;I&amp;rsquo;m in the process of creating an Ansible playbook for configuring&#xA;and maintaining all the infrastructure hosted on my server. The&#xA;main benefits of using Ansible for my use-case instead of just&#xA;running commands directly is that it allows for modular, self-documenting&#xA;modules and it&amp;rsquo;s easy to use with version control. There are a lot&#xA;of programs required by the server (&lt;a href=&#34;https://jacobedwards.org/projects/stagit-hook&#34;&gt;stagit-hook&lt;/a&gt;,&#xA;&lt;a href=&#34;https://jacobedwards.org/projects/gitman&#34;&gt;gitman&lt;/a&gt;, &lt;a href=&#34;https://jacobedwards.org/projects/autocert&#34;&gt;autocert&lt;/a&gt;, etc.)&#xA;that aren&amp;rsquo;t officially packaged by OpenBSD, so that leads to two&#xA;choices: Either automate the build and install in Ansible (effectively&#xA;writing package manager in Ansible), or package the projects for&#xA;OpenBSD and install them normally. While either solution would work,&#xA;the latter makes use of existing systems instead of introducing new&#xA;ones and is less error-prone.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
