comprofix.com/public/index.xml

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Comprofix</title>
    <link>http://localhost:1313/</link>
    <description>Recent content on Comprofix</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 21 Sep 2024 00:00:00 +0000</lastBuildDate>
    <atom:link href="http://localhost:1313/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Continuous Integration &amp; Continuous Deployment</title>
      <link>http://localhost:1313/post/2024-09-21-websitedeployment/</link>
      <pubDate>Sat, 21 Sep 2024 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/post/2024-09-21-websitedeployment/</guid>
      <description>&lt;p&gt;Since the reset of the website, I have been working on getting it to auto build and deploy using &lt;a href=&#34;https://docs.gitea.com/usage/actions/overview&#34;&gt;Gitea Actions&lt;/a&gt;. Which is similar and compatible to &lt;a href=&#34;https://github.com/features/actions&#34;&gt;GitHub Actions&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Before implementing the action it was a manual process which required using docker commands to login, build and push the image to the container registry.&lt;/p&gt;&#xA;&lt;h3 id=&#34;why-use-cicd&#34; id=why-use-cicd&gt;&#xA;  &#xA;    &lt;span class=&#34;me-2&#34;&gt;Why use CI/CD?&lt;/span&gt;&#xA;    &lt;a href=&#34;#why-use-cicd&#34; class=&#34;anchor text-muted&#34;&gt;&lt;i class=&#34;fas fa-hashtag&#34;&gt;&lt;/i&gt;&lt;/a&gt;&#xA;  &#xA;&lt;/h3&gt;&lt;p&gt;It takes the manual process steps away and does them for you, helping you to avoid missing any steps and avoiding errors. This also makes the interaction seamless and automated.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Reset and Restart</title>
      <link>http://localhost:1313/post/2024-09-05-resetrestart/</link>
      <pubDate>Thu, 05 Sep 2024 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/post/2024-09-05-resetrestart/</guid>
      <description>&lt;p&gt;It&amp;rsquo;s time to reset the website and start building my blog again. I have had this domain for a number of years and it has always been used for my E-Mail.&lt;/p&gt;&#xA;&lt;p&gt;But the website has been more of a play ground for experimenting and testing.&lt;/p&gt;&#xA;&lt;p&gt;I am now hoping to get into the habit of writing more blog posts as I document my journey as I experiment with my HomeLab.&lt;/p&gt;</description>
    </item>
    <item>
      <title>About</title>
      <link>http://localhost:1313/about/</link>
      <pubDate>Thu, 20 Apr 2023 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/about/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://github.com/cotes2020/jekyll-theme-chirpy&#34;&gt;Chirpy&lt;/a&gt; is a blog theme originally based on &lt;a href=&#34;https://jekyllrb.com/&#34;&gt;Jekyll&lt;/a&gt;. Due to Jekyll&amp;rsquo;s design limitations, it does not natively support internationalization (i18n) and requires third-party plugins for i18n functionality. To enable i18n support for Chirpy without the hassle of relying on third-party plugins, the &lt;a href=&#34;https://github.com/geekifan/hugo-theme-chirpy&#34;&gt;hugo-theme-chirpy&lt;/a&gt; project migrated the Chirpy theme to &lt;a href=&#34;https://gohugo.io/&#34;&gt;Hugo&lt;/a&gt; with minimal adaptations. All features of Chirpy are available in hugo-theme-chirpy (though some functionalities may operate differently within the Hugo framework).&lt;/p&gt;&#xA;&lt;p&gt;Follow the posts in the demo site to quickly set up a free personal blog!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Archives</title>
      <link>http://localhost:1313/archives/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/archives/</guid>
      <description></description>
    </item>
  </channel>
</rss>