<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Forgejo on ThinkPractice: Smart Solutions to Practical Problems</title>
    <link>https://thinkpractice.nl/tags/forgejo/</link>
    <description>Recent content in Forgejo on ThinkPractice: Smart Solutions to Practical Problems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 24 Aug 2026 13:55:37 +0200</lastBuildDate>
    <atom:link href="https://thinkpractice.nl/tags/forgejo/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Automating the Deployment of This Blog</title>
      <link>https://thinkpractice.nl/post/automating-this-blog/</link>
      <pubDate>Mon, 24 Aug 2026 13:55:37 +0200</pubDate>
      <guid>https://thinkpractice.nl/post/automating-this-blog/</guid>
      <description>&lt;p&gt;Today, I spent some time automating the deployment of this blog. This site is&#xA;generated using a static site generator called &lt;a href=&#34;https://gohugo.io/&#34;&gt;Hugo&lt;/a&gt;. While&#xA;I love Hugo, deployment is a bit different from other blogs than, for instance,&#xA;WordPress. In WordPress, you write and can directly publish the site. Using Hugo,&#xA;however, you write your posts and then the site is generated, much like a compiler&#xA;that generates machine code from the website you&amp;rsquo;ve written. Until now, this was a&#xA;very manual process. I had to write the blog post, test it locally, and copy the&#xA;post manually to my hosting provider. It wasn&amp;rsquo;t that much work to be honest, but&#xA;still it was a small hurdle when writing a post. It also prevented me from&#xA;automating some things, for instance, automatically creating a post when a new&#xA;version of an app was released. That changed today. I spent some time setting up&#xA;a Forgejo runner Docker container on my home server that automatically builds the site when&#xA;committed to the Git repository. When I deploy from the &lt;code&gt;develop&lt;/code&gt; branch, the site&#xA;is deployed locally to that server, so I can directly observe how the new post&#xA;would look in production. When it&amp;rsquo;s then merged into the &lt;code&gt;main&lt;/code&gt; branch, the site is deployed&#xA;here on &lt;code&gt;thinkpractice.nl&lt;/code&gt;. Hopefully, automating this process will make it easier&#xA;for me to write and post. In any case, keep posted &lt;em&gt;pun intended&lt;/em&gt;, because some&#xA;nice updates are coming soon!&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
