<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Hashover on Matt Thornton</title>
    <link>https://matt-thornton.net/tags/hashover/</link>
    <description>Recent content in Hashover on Matt Thornton</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Wed, 23 Feb 2022 05:26:35 +0000</lastBuildDate><atom:link href="https://matt-thornton.net/tags/hashover/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Migrating Wordpress comments to HashOver for Hugo</title>
      <link>https://matt-thornton.net/tech/migrating-wordpress-comments-to-hashover-for-hugo/</link>
      <pubDate>Wed, 23 Feb 2022 05:26:35 +0000</pubDate>
      
      <guid>https://matt-thornton.net/tech/migrating-wordpress-comments-to-hashover-for-hugo/</guid>
      
        <description>&lt;p&gt;I&amp;rsquo;ve briefly covered thoughts around &lt;a href=&#34;https://www.matt-thornton.net/general/hugo-migration-part-2/&#34;&gt;adding a comment system&lt;/a&gt; in to this blog since it was migrated to Hugo.&lt;/p&gt;
&lt;p&gt;I won&amp;rsquo;t rehash the decision making process - but fundamentally I wasn&amp;rsquo;t going to go with Disqus and wanted a simpler solution. There are various options out there and tl;dr I ended up choosing &lt;a href=&#34;https://github.com/jacobwb/hashover&#34;&gt;HashOver&lt;/a&gt;, mostly for the following reasons:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;It appeared to be reasonably simple to stand it up completely external to the &amp;lsquo;main&amp;rsquo; site, i.e. in a sub-domain&lt;/li&gt;
&lt;li&gt;It runs on PHP/MySQL which is already available on my host. Other commenting systems needed different stacks which I don&amp;rsquo;t have access to without switching.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Incidentally, HashOver supports other persistence options such as SQLite and even XML which if you wanted to be completely serverless which could be interesting; but as it happens this comment migration process would likely have been a fair whack harder.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>